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.
State
Resolved
Started
Lasted
44 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
22 min 51%
Monitoring
21 min 49%
Updates
Times in UTCAs posted by bunny.net
This issue has now been resolved.
Our Engineering team has applied a fix to the Shield rule logic and we are currently monitoring the situation. Any updates performed on Shield from 11:48am UTC will need to be reissued on the affected zone (API call or change toggle).
We are currently reviewing an issue where shield zone rule or logic changes are failing to propagate across our network.
Affected components
2bunny.net in the last 90 days
Full historyIncidents in 90 days
19
Days with an incident
33
Median duration
2 h 58 min
This incident
76% shorter than the median
Other bunny.net incidents
All incidentsbunny.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.
bunny.net·Security update regarding one of our infrastructure providers
bunny.net reported a security incident that affected the CDN. bunny.net now states that the incident is resolved. The incident lasted from 28 October 2026 to 9 November 2026.
bunny.net·Performance degradation in DE
This incident has been resolved, we're not observing performance issues anymore.
bunny.net·Storage operations in DE and Stream uploads performance degradation
This issue has now been resolved.
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