Cloudflare Gateway DNS-over-TLS Connectivity Issues over IPv4
Cloudflare Gateway DNS-over-TLS connections over IPv4 do not work. This affects the Gateway and Zero Trust Gateway components. Cloudflare reports that it is investigating the issue.
State
Investigating
Started
2 h ago
2026-11-02 22:12 UTC
Ongoing for
1 h 36 min
Worst impact
Degraded
Timeline
1 updateInvestigating
1 h 36 min 100%
Updates
Times in UTCAs posted by Cloudflare
Cloudflare is investigating an issue affecting Cloudflare Gateway DNS-over-TLS (DoT) connections over IPv4. Affected customers may experience connection timeouts and failed DNS resolution. This issue is limited to DoT over IPv4. DoT over IPv6, DNS-over-HTTPS (DoH), and standard DNS over UDP/TCP are not affected. We are working to identify the cause and restore connectivity. Further updates will be provided as more information becomes available.
Affected components
2Cloudflare in the last 90 days
Full historyIncidents in 90 days
54
Days with an incident
67
Median duration
1 h 17 min
This incident
1.3× the median
Other Cloudflare incidents
All incidentsCloudflare·Partial System Outage
Cloudflare reports a partial system outage at 20 points of presence. The affected locations include Ahmedabad, Arica, Algiers, Annaba, Baku, Bangalore, Canberra, Hagatna, Doha, Djibouti, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, Dhaka, Mombasa, Nairobi, and Fuzhou. Cloudflare reports that the incident is resolved. The outage lasted 282 minutes, from 17:33 to 22:15 UTC on 2 November 2026.
Cloudflare·Worker Deployments Delayed
Cloudflare Workers deployments were delayed. The incident affected Workers and Developer Services - Workers. Cloudflare reports that the incident is resolved. It lasted 49 minutes.
Cloudflare·Partial System Outage
Cloudflare reports a partial outage in 20 locations. The affected locations include Arica, Algiers, Annaba, Baku, Bangalore, Canberra, Hagatna, Djibouti, Erbil, Sydney, Gaborone, Dallas, Curitiba, Luanda, Mombasa, Nairobi, Fuzhou, Istanbul, Guatemala City, and Chengmai. Cloudflare reports that the outage is resolved. It lasted about 43 hours and 33 minutes.
Cloudflare·Cache purge delays in Qingdao Shandong, China
This incident has been resolved.
Cloudflare·Increased Errors for Browser Run
This incident has 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.cc/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.cc/feed.xml?providers=cloudflare/feed subscribe https://outages.cc/feed.xml?providers=cloudflareFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane