Maintenance bunny.net status
bunny.net · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
bunny.net's status page shows “Maintenance” in Stream Service and Stream - Transcoding Service; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Maintenance · 4 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS200325: routing data not loaded on this view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Stream Service, Stream - Transcoding Service, API
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 78 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 1 h 8 min |
Evidence
- Official page: Maintenance (“Service Under Maintenance”). evidence confidence: high
- Vendor stage: resolved on “Video Playback and Encoding Failures on Bunny Stream”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside bunny.net's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on bunny.net. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on bunny.net, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with bunny.net. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Video Playback and Encoding Failures on Bunny Stream
major resolved · started · resolved
5 updates
- investigating
Our Engineering team are currently investigating an issue on our Stream platform of playback failures on our embedded players, as well as upload failures to our platform.
- monitoring
We have identified a backend database issue which had caused a timeout across our video servers (to include our player and uploading process). The problem was rectified and we are now monitoring the situation.
- monitoring
We are observing some isolated issues on the back of the fix. We are working to fully restore the process on our platform.
- monitoring
We have confirmed that all services have fully resumed. Our Engineering team are currently monitoring the situation. Playback has now fully resumed without issue. New uploads during the outage have failed and thus would need re-uploading. Existing transcoding videos were not lost, however the status reported on some of these videos may be inaccurate as a result.
- resolved
This issue is now fully resolved. Our Engineering team have identified additional guardrails to prevent this specific issue from happening in future.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.