Bunny.net Status · History · Incident #2417

RESOLVED

Isolated 502s for Magic Containers

Major · Started Apr 30, 2026 · 10:12 AM

  • Duration

    25d 22h 11m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Isolated 502s for Magic Containers

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.


  • Started

    Apr 30, 2026 · 10:12 AM

  • Resolved

    May 26, 2026 · 8:23 AM

  • Duration

    25d 22h 11m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Apr 30 · 10:12 AM Bunny.net

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

  • Investigating

    Apr 30 · 10:14 AM Bunny.net

    We are continuing to investigate this issue.

  • Investigating

    Apr 30 · 12:16 PM Bunny.net

    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.

  • Investigating

    May 1 · 10:48 AM Bunny.net

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

  • Monitoring

    May 6 · 2:29 PM Bunny.net

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

  • Resolved

    May 26 · 8:23 AM Bunny.net

    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.

Get alerted before the next Bunny.net outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free
Hey there 👋  Friends from designmodo are here to help!