SEA (Seattle) on 2026-11-20
We will be performing scheduled maintenance in SEA (Seattle) datacenter on 2026-11-20 between 09:00 and 15:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
The latest update from Cloudflare.
State
Resolved
Starts
Lasted
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Cloudflare
We will be performing scheduled maintenance in SEA (Seattle) datacenter on 2026-11-20 between 09:00 and 15:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
123
Days with an incident
85
Median duration
1 h 30 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·R2 and Durable Objects availability issues
R2 and Durable Objects in Eastern North America have intermittent errors and failed requests. Cloudflare reports that a fix is in place and monitoring is in progress.
Cloudflare·Observability ingestion delay and query failures
Cloudflare Workers Observability and Cloudflare Traces had delays in new data ingestion and increased query errors. The incident affected the Workers and Workers Observability components. Cloudflare reports that the incident is resolved, and it lasted about 5 hours and 26 minutes.
Cloudflare·Durable Objects and D1 – Increased Errors
Cloudflare reported increased errors and latency on Durable Objects and D1 for a subset of customers; Workers that do not use these components were not affected. Cloudflare identified the problem and implemented a fix. The incident is resolved and lasted about 32 minutes.
Cloudflare·Cloudflare Access Issue
Cloudflare Access had degraded performance that can cause authentication failures for applications that strictly validate token claims. Cloudflare reports that the incident is resolved and lasted 2 hours and 8 minutes.
Cloudflare·Degraded connectivity between Europe and Asia Pacific
Cloudflare reported degraded connectivity between Europe and Asia Pacific. This affected Cache Reserve, D1, and R2. Cloudflare reported the incident as resolved after 4 hours and 53 minutes.
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.
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.
https://outages.live/feed.xml?providers=cloudflare/feed subscribe https://outages.live/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane