Major ImpactLast updated: Oct 31, 2025, 6:04 PM UTCFetched just now

Issues with 1.1.1.1 public resolver

Started

Oct 31, 2025, 11:43 AM UTC

Resolved

Oct 31, 2025, 6:04 PM UTC

Timeline

ResolvedOct 31, 2025, 6:04 PM UTC
This incident is now resolved.
UpdatedOct 31, 2025, 5:49 PM UTC
The fixes have been deployed and we are continuing to monitor the situation.
UpdatedOct 31, 2025, 5:33 PM UTC
The fixes have been deployed and we are continuing to monitor the situation.
MonitoringOct 31, 2025, 5:16 PM UTC
The fixes have been deployed and we are continuing to monitor the situation.
UpdatedOct 31, 2025, 5:00 PM UTC
We are deploying fixes and are continuing to monitor the situation.
UpdatedOct 31, 2025, 4:44 PM UTC
We are deploying fixes and are continuing to monitor the situation.
UpdatedOct 31, 2025, 4:28 PM UTC
We are deploying fixes and are continuing to monitor the situation.
UpdatedOct 31, 2025, 4:11 PM UTC
We are deploying fixes and are continuing to monitor the situation.
UpdatedOct 31, 2025, 3:52 PM UTC
We are deploying fixes and are continuing to monitor the situation.
UpdatedOct 31, 2025, 3:40 PM UTC
We are continuing to investigate possible solutions.
UpdatedOct 31, 2025, 3:16 PM UTC
We are continuing to investigate possible solutions.
UpdatedOct 31, 2025, 3:00 PM UTC
We are continuing to investigate possible solutions.
UpdatedOct 31, 2025, 2:46 PM UTC
We are continuing to investigate possible solutions.
IdentifiedOct 31, 2025, 2:28 PM UTC
The issue has been identified and we are investigating possible solutions.
UpdatedOct 31, 2025, 2:07 PM UTC
We are continuing to investigate this issue.
InvestigatingOct 31, 2025, 12:48 PM UTC
We are currently investigating this issue.
MonitoringOct 31, 2025, 11:54 AM UTC
A fix has been implemented and we are monitoring the results.
InvestigatingOct 31, 2025, 11:43 AM UTC
Cloudflare is aware of, and investigating, an issue which potentially impacts multiple users that use 1.1.1.1 public resolver. Further detail will be provided as more information becomes available.