Isolated 502s for Magic Containers
Resolved
Major impact
Updates
Resolved
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.
Monitoring
We are monitoring improvements related to the resilience of routing configuration failover on edge servers during temporary control plane connectivity interruptions.
Investigating
Our Engineering team are still investigating the root cause for isolated 502s in the NA region.
Investigating
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
We are continuing to investigate this issue.
Investigating
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.