Issues with 1.1.1.1 public resolver in Canada
The 1.1.1.1 public resolver has degraded performance in Canada. This affects the Recursive DNS component. Cloudflare has identified the issue and reports an active hijack of 1.1.1.0/24 on one network. The 1.0.0.1 and IPv6 resolver prefixes work at this time.
State
Identified
Started
Ongoing for
1 h
Worst impact
Degraded
Timeline
2 updatesInvestigating
16 min 27%
Identified
44 min 73%
Updates
Times in UTCAs posted by Cloudflare
We have reached out to the network where we see an active hijack of 1.1.1.0/24. 1.0.0.1 and public resolver IPv6 prefixes are fully operational and reachable at this time.
Cloudflare is aware of, and investigating, an issue which potentially impacts multiple users in Canada that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.
Affected components
1Cloudflare in the last 90 days
Full historyIncidents in 90 days
97
Days with an incident
79
Median duration
1 h 33 min
This incident
35% shorter than the median
Other Cloudflare incidents
All incidentsCloudflare·Cloudflare is seeing an issue with Workers API availability
Cloudflare Workers API availability is degraded. Customers can see more 5xx errors when they deploy Workers or do other API actions. Cloudflare identified the issue, implemented a fix, and now monitors the results.
Cloudflare·Cloudflare is currently having an issue with the r8.im registry used for Replicate model publishing and builds is currently restricted
The r8.im registry that Replicate uses for model publishing and builds is restricted. Cloudflare reports that a fix is in place and engineers monitor the results.
Cloudflare·Elevated error rate for workers startup
Cloudflare Workers startup had an elevated error rate. The problem affected Workers and Developer Services - Workers, mainly for Workers that use large amounts of memory. Cloudflare resolved the incident after 82 minutes.
Cloudflare·Durable Objects increased error rates in North America
Cloudflare Durable Objects had increased error rates in North American colos. Cloudflare reports that the incident is resolved. The incident lasted about 5 hours and 5 minutes.
Cloudflare·Replicate Issue
Cloudflare Replicate customers saw more 500 errors for predictions in the Replicate component. Cloudflare identified the issue and put a fix in place. The incident is resolved and lasted 3 hours and 4 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