S3 Storage degradation in Frankfurt
S3 Storage in Frankfurt (DE) gives intermittent errors. Uploads, downloads, and listings on Edge Storage may be affected. bunny.net reports the status as monitoring. A fix is applied and performance has normalized.
State
Monitoring
Started
Ongoing for
20 h 45 min
Worst impact
Degraded
Timeline
2 updatesIdentified
4 h 8 min 20%
Monitoring
16 h 37 min 80%
Updates
Times in UTCAs posted by bunny.net
Our Storage team has identified an underlying degraded process causing intermittent/degraded S3 storage zone performance in DE, and have applied a fix to the application. Performance has now normalized, and we will continue to monitor the situation.
We have identified an issue causing intermittent errors on S3 Storage zones in DE. Uploads, downloads and listings may be affected. Our Engineering team is working on a fix.
Affected components
1bunny.net in the last 90 days
Full historyIncidents in 90 days
21
Days with an incident
41
Median duration
3 h 48 min
This incident
5.5× the median
Other bunny.net incidents
All incidentsbunny.net·Security update regarding one of our infrastructure providers
bunny.net reports a security incident at one of its infrastructure providers. One CDN node in Pakistan was on an affected server, but that node was out of traffic rotation and did not serve requests. bunny.net removed the server and the status is monitoring.
bunny.net·Network unavailability in Los Angeles
Network unavailability in Los Angeles affected bunny.net CDN, Edge Storage, Magic Containers, and Bunny Database. Bunny.net reports that CDN traffic was rerouted to the nearest PoP. The incident is resolved and lasted about 14 hours and 17 minutes.
bunny.net·Shield Zone Update Failures
bunny.net reports that Shield Zone updates failed on the API and Bunny Shield components. A fix is in place and bunny.net monitors the result. The incident is resolved after 44 minutes.
bunny.net·Crypto Payment Failures
Crypto payments fail on the bunny.net API. The partner payment provider stopped its service after a security incident. Bunny.net investigates the issue. Crypto payments and pending payments continue when the partner starts its service again. Other payment methods and all bunny.net services work normally.
bunny.net·Degraded API Response Times
bunny.net reported degraded API response times that affected the Dashboard and API. The incident is resolved and lasted about 61 minutes.
Follow bunny.net
Your coding agent knows when bunny.net is down, and tells you when a failure is theirs, not yours. You can also get bunny.net incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "bunny" and tell me if bunny.net has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=bunny/feed subscribe https://outages.live/feed.xml?providers=bunnyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane