Third party transit provider issue causing increased HTTP 5xx errors

This incident has been resolved.

We are continuing to monitor for any further issues.

At this moment we are seeing network stability and reachability return back to normal levels, and we are monitoring the situation. We are updating the status of this incident to Monitoring, and if the situation changes we will update accordingly.

As the major provider that was experiencing issues has implemented a fix in their network, other global network providers have started to re-enable their peering sessions with it. We are continuing to see improved reachability and monitoring the situation.

We are observing significantly improved stability and reachability in the network as the third party provider is implementing a fix for their issue and we have implemented measures to work around the problem

Major transit providers are taking action to work around the network that is experiencing issues and affecting global traffic. We are applying corrective action in our data centers as the situation changes in order to improve reachability

We are continuing to engage with our partners, fixes are being implemented with other transit providers.

We are continuing to work on a fix for this issue.

We have identified an issue with a transit provider which is causing 5xx class HTTP errors, such as HTTP 522, 502, 503. This is affecting all data centers that make use of this transit provider and we are working on implementing mitigations to alleviate this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

Cloudflare is investigating an increased level of HTTP 5xx class errors. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.