Bunny incident

Isolated 502s for Magic Containers

Major Resolved View vendor source →

Bunny experienced a major incident on April 30, 2026 affecting Magic Containers and Bunny Database, lasting 25d 22h. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2026, 10:12 AM UTC
Resolved
May 26, 2026, 08:23 AM UTC
Duration
25d 22h
Detected by Pingoru
Apr 30, 2026, 10:12 AM UTC

Affected components

Magic ContainersBunny Database

Update timeline

  1. investigating Apr 30, 2026, 10:12 AM UTC

    We are currently looking into isolated 502s within the NA region for CDN endpoints utilizing Magic Containers and Edge Scripting. This is primarily affecting specific regions in North America. Our Engineering team are investigating the issue currently.

  2. investigating Apr 30, 2026, 10:14 AM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 30, 2026, 12:16 PM UTC

    We have made some routing adjustments to mitigate the timeouts on Database and is fully operational again. Our Engineering team is continuing to investigate the Magic Containers issue.

  4. investigating May 01, 2026, 10:48 AM UTC

    Our Engineering team are still investigating the root cause for isolated 502s in the NA region.

  5. monitoring May 06, 2026, 02:29 PM UTC

    We are monitoring improvements related to the resilience of routing configuration failover on edge servers during temporary control plane connectivity interruptions.

  6. resolved May 26, 2026, 08:23 AM UTC

    We identified and resolved an issue that could cause endpoint updates to experience delayed propagation after CDN services had been running for an extended period of time. The issue was related to endpoint synchronization between Magic Containers and the CDN routing component, where slower processing connected to sticky session invalidation could result in stale endpoint data remaining in use longer than expected.