Several Sites Down at Once? Check Regional Outages With Cloudflare Radar
Email, banking and a news site all stop loading at once, and Radar’s map shows an outage in your country. Is that event the reason you’re offline?
- Radar’s redesigned homepage starts with a map of Internet traffic and outages.
- Match your failed connections to an event’s location, network and time, not just its country name.
- Radar, Cloudflare Status and your own service logs answer different questions.
Use the map to look beyond one failed connection
When several sites stop loading, Cloudflare Radar can help establish whether a wider disruption was observed in the region. It provides context for an investigation rather than a test of your individual broadband connection.
Cloudflare’s October 23 changelog highlights a redesigned homepage with traffic and outages on an interactive map. The map leads into country-level information, making geography a practical starting point for a reader who does not already know which chart to open.
The redesign explanation describes a tabbed flow beneath the map for summary statistics and deeper exploration. For an outage investigation, begin with the affected location and the Outage Center; other Internet adoption statistics can wait.
Align the time window, network and affected area
Open the Outage Center and select a period covering the failed connections. It separates observed Internet outages from automatically detected traffic anomalies. An anomaly is a reason to investigate, not a statement that an entire country lost connectivity.
The event fields distinguish location, autonomous system number, type, scope, likely cause and start/end times. An ASN identifies a network. A country label can therefore accompany an incident limited to one provider or a smaller region.
Outage Center timestamps are in UTC. Convert local incident notes before comparing them. For example, 14:00 UTC is 23:00 in South Korea on the same date; other conversions can cross midnight.
Follow the event’s supporting information when available. The Outage Center’s design connects observed events to additional reporting or charts. The detailed scope is more useful than a map marker alone, and a likely cause should remain a likely cause.
Radar and Cloudflare Status cover different systems
| Question | Where to look | What it contributes |
|---|---|---|
| Was a wider regional or network disruption observed? | Radar / Outage Center | Traffic context and observed Internet events |
| Did Cloudflare report a service incident? | Cloudflare Status | Cloudflare service incidents and maintenance |
| Why did this application request fail? | The service’s status page and logs | Evidence about that service and request |
Cloudflare Status reports the company’s own service conditions. A wider Internet outage visible in Radar does not, by itself, establish a Cloudflare service failure. Compare the product, location and incident time before connecting the two.
No matching event does not clear the local connection
Radar draws on Cloudflare’s global network and aggregated, anonymized 1.1.1.1 resolver data, among other sources. Those observations do not test every home router or every application request. An empty event list cannot certify that your connection is healthy.
A useful next step is to record the failure time and timezone, affected services and error messages. Comparing the same device over another connection can help narrow the investigation. Match those observations against Radar’s scope and the relevant service status notices.
If an event fits, follow its details and recovery updates. If none fits, continue investigating DNS, the connection path and the application response. Radar supplies the wider Internet context for that work.