outages.live
Live
CloudflareIncident ·

Network Performance Issues in St. Louis, USA

ResolvedOfficial update
0

Cloudflare reported network performance issues in St. Louis, USA. The affected components were St. Louis, United States (STL) and North America - St. Louis, United States (STL). Cloudflare reports that the incident is resolved, and it lasted 140 minutes.

State

Resolved

Started

Lasted

2 h 20 min

Worst impact

Degraded

Timeline

2 updates
22:5023:2500:0000:3501:10
DegradedUpdate postedTimes in UTC

Monitoring

2 h 20 min 100%

Updates

Times in UTC

As posted by Cloudflare

Resolved

This incident has been resolved.

Monitoring

Cloudflare has identified issues with network performance in St. Louis (STL), USA. A fix has been implemented and we're monitoring the results.

Affected components

2
St. Louis, United States - (STL)North America - St. Louis, United States - (STL)

Cloudflare in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

84

Days with an incident

76

Median duration

1 h 36 min

This incident

1.5× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

56 days
median 1 h 36 min
90 days agoToday

Other Cloudflare incidents

All incidents

Cloudflare·Prediction issue on OpenAI models via Replicate

Cloudflare reported that predictions on official OpenAI models through Replicate were degraded. Some predictions failed with a 401 tokeninvalidated error. The incident is resolved and lasted 31 minutes.

Resolved

Cloudflare·Account Analytics Filter Issue

Cloudflare Analytics filters did not work on some analytics dashboards. Cloudflare reports that the incident is resolved. The outage lasted 43 minutes.

Resolved

Cloudflare·Changes to Cloudflare Workers are not producing Event Subscription events

Cloudflare Workers changes do not produce Event Subscription events. This affects Workers and Queues. Cloudflare reports that it is investigating. Cloudflare disabled the feature on purpose and is working to restore it.

Degraded

Cloudflare·Network Performance Issues in Eastern North America

Cloudflare network performance was degraded in Eastern North America. The Network component was affected. Cloudflare reported the incident as identified, then monitored it. Cloudflare resolved the incident after about 3 hours and 38 minutes.

Resolved

Cloudflare·Changes made to Workers may be delayed or disrupted

Cloudflare reported that changes to Workers, such as creating, editing and deleting them, were delayed or disrupted. Deployed Workers were not affected. Cloudflare resolved the incident after about 9 hours and 31 minutes.

Resolved

Follow Cloudflare

Your coding agent knows when Cloudflare is down, and tells you when a failure is theirs, not yours. You can also get Cloudflare incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cloudflare" and tell me if Cloudflare has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=cloudflare
Slack
/feed subscribe https://outages.live/feed.xml?providers=cloudflare

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane