Changes / Bunny.net / Isolated 502s for Magic Containers

Bunny.net: Major incident: Isolated 502s for Magic Containers

Summary

Major isolated 502s affected North American CDN endpoints using Magic Containers and Databases, starting 2026-04-30 10:12 UTC and resolved 2026-05-26 08:23 UTC (25 days 22 h). Database routing adjustments restored service; Bunny.net later fixed delayed endpoint synchronization between Magic Containers and CDN routing, linked to slow sticky session invalidation that left stale endpoint data in use.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 64%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Isolated 502s for Magic Containers
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-04-30 10:12 UTC
AddedResolved time#5
Before: not present
After: 2026-05-26 08:23 UTC
AddedAffected components#6
Before: not present
After: Bunny Database, Edge Scripting, Magic Containers
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateinvestigating#9
Before: not present
After: 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.
AddedUpdateinvestigating#10
Before: not present
After: Our Engineering team are still investigating the root cause for isolated 502s in the NA region.
AddedUpdatemonitoring#11
Before: not present
After: We are monitoring improvements related to the resilience of routing configuration failover on edge servers during temporary control plane connectivity interruptions.
AddedUpdateresolved#12
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident.

History of this incident

When (UTC)ChangeKind
Major incident: Isolated 502s for Magic Containers (this change)
Major isolated 502s affected North American CDN endpoints using Magic Containers and Databases, starting 2026-04-30 10:12 UTC and resolved 2026-05-26 08:23 UTC (25 days 22 h). Database routing adjustments restored service; Bunny.net later fixed delayed endpoint synchronization between Magic Containers and CDN routing, linked to slow sticky session invalidation that left stale endpoint data in use.
Major incident

All Bunny.net changes → · Bunny.net profile · Markdown · JSON