ORF (Norfolk) on 2026-11-20
We will be performing scheduled maintenance in ORF (Norfolk) datacenter on 2026-11-20 between 07:00 and 11: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
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Cloudflare
We will be performing scheduled maintenance in ORF (Norfolk) datacenter on 2026-11-20 between 07:00 and 11: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
119
Days with an incident
84
Median duration
1 h 26 min
This incident
Not comparable
Other Cloudflare incidents
All incidentsCloudflare·Degraded connectivity between Europe and Asia Pacific
Cloudflare reports degraded connectivity between Europe and the Asia Pacific region. This affects requests to R2, D1, and Cache Reserve. Cloudflare implemented a fix and monitors the results.
Cloudflare·Increased latency on Analytics API (GraphQL) queries
Cloudflare reports increased latency on Analytics API GraphQL queries. The incident is resolved and lasted about 2 hours and 47 minutes.
Cloudflare·R2 Downloads Stalling in Japan
R2 downloads stalled for users who connect through datacenters in Japan. Cloudflare reports that the incident is resolved. The incident lasted 78 minutes.
Cloudflare·Network disruption across multiple colocations in India
A network disruption degraded some Cloudflare services in Ahmedabad, Hyderabad, Kanpur, Mumbai, Nagpur, New Delhi, and Patna, India. Cloudflare identified the issue and implemented a fix, then monitored the results. The incident is resolved and lasted 42 minutes.
Cloudflare·Network Performance Issues in North America
Between approximately 07:00 UTC and 10:00 UTC Cloudflare investigated issues with network performance in North America. This has since been 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.
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