outages.live
Live
bunny.netMaintenance ·

Magic Containers Maintenance (Sweden)

MaintenanceOfficial update

We will be undergoing maintenance within our MC Sweden nodes. Some applications with attached volumes solely pinned to this location may be unavailable temporarily (multi region applications will failover)

The latest update from bunny.net.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by bunny.net

Scheduled

We will be undergoing maintenance within our MC Sweden nodes. Some applications with attached volumes solely pinned to this location may be unavailable temporarily (multi region applications will failover)

Affected components

1
Magic Containers

bunny.net in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

20

Days with an incident

35

Median duration

3 h 19 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 days
median 3 h 19 min
90 days agoToday

Other bunny.net incidents

All incidents

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.

Resolved

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.

Resolved

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.

Degraded

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.

Resolved

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.

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=bunny
Slack
/feed subscribe https://outages.live/feed.xml?providers=bunny

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane