Loading status…
What to do while Bunny.net is down
isuptime cannot fix Bunny.net, and neither can you. These are the things that are actually worth doing until it comes back.
- Read what Bunny.net has actually published. Their incident notes say which components are affected and usually carry an estimate, which is more than any third party can tell you. “Increased encoding processing time”
- Stop retrying in a loop. If your code calls Bunny.net, back off exponentially and cap the retries. A retry storm from every client at once is a large part of why outages take as long to clear as they do, and it will exhaust your own quota before the service returns.
- Get told when it clears, instead of refreshing. The bell in the header sets up a browser notification, or a Discord, Slack or Telegram webhook, for the moment Bunny.net's status changes.
- Move the urgent work elsewhere. Only worth it for something that cannot wait — check the substitute is up first.
Instead of Bunny.net, right now
Status shown for each is read from that provider's own feed, on the same schedule as this page.
