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.
State
Resolved
Started
Lasted
1 h 1 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
43 min 70%
Monitoring
18 min 30%
Updates
Times in UTCAs posted by bunny.net
This incident is now resolved
We have resolved the API degradation issue, and are monitoring the services.
We are currently investigating an issue with degraded API response times on our platform. Dashboard services may have delayed response times, as well as some of our API endpoint responses. Active platform services are not affected by degradation.
Affected components
2bunny.net in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
27
Median duration
2 h 58 min
This incident
66% shorter than the median
Other bunny.net incidents
All incidentsbunny.net·Security update regarding one of our infrastructure providers
bunny.net reports a security incident that affects the CDN component for custom domains. The provider continues to monitor the situation. The reissuance of managed TLS certificates is complete and all affected certificates are revoked.
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.
bunny.net·Network issues in Frankfurt
Root Cause behind this incident was a core network outage on one of our major Frankfurt providers that made a large number of Bunny servers in Frankfurt unreachable between 02:36 and 02:44 UTC. We haven't observed any further issues since 02:44 UTC, nor expect any further issues due to this and will be resolving this incident at this time.
bunny.net·Database Performance Degradation
This incident 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