Cloudflare: outage reported

The problem is reported by Cloudflare itself. The site still answers our check, so it may affect only some features or regions.

Official status
Partial System Outage

From www.cloudflarestatus.com, read 3 min ago.

Our check, from Germany
Answered in 100 ms

Request to www.cloudflare.com, 4 min ago. 288 of 288 checks in the last 24 hours succeeded, median 109 ms.

Is Cloudflare working for you?

One click, no account. It helps others see whether the problem is widespread.

We are still collecting reports. The numbers appear once 20 people have answered within 24 hours.

Affected parts, according to Cloudflare

Arica, Chile - (ARI)
Major outage
Annaba, Algeria - (AAE)
Major outage
Baku, Azerbaijan - (GYD)
Degraded performance
Bangalore, India - (BLR)
Degraded performance
Canberra, ACT, Australia - (CBR)
Major outage
Cape Town, South Africa - (CPT)
Degraded performance
Belo Horizonte, Brazil - (CNF)
Degraded performance
Beirut, Lebanon - (BEY)
Degraded performance
Bandar Seri Begawan, Brunei - (BWN)
Major outage
Hagatna, Guam - (GUM)
Major outage
Bogotá, Colombia - (BOG)
Degraded performance
Dar Es Salaam, Tanzania - (DAR)
Degraded performance

Open incidents

identifiedMinor impactStarted Aug 27, 18:46 UTC

We are continuing to work on a fix for this issue.

Response time, last 24 hours

measured from our server in Germany
0 ms500 ms1 s20:0000:0004:0008:0012:0016:00
Time to first responseFailed check
One request every 5 minutes from a single location (Falkenstein, Germany). It shows how the answer time changes; it is not the speed you will see on your own connection.

Works for everyone else? Fix it on your side

  1. Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
  2. Test from the command line. Check name resolution and the route, to see where the connection stops.
    nslookup cloudflare.com tracert cloudflare.com
  3. Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
  4. Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
  5. Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
    ipconfig /flushdns
  6. Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
  7. Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.
Guides that mention Cloudflare

Recent incidents

from the official feed, read 27 min ago
ResolvedStarted Oct 16, 12:58 UTCResolved Oct 16, 13:03 UTC

Between 12:58 and 13:03 UTC, Cloudflare experienced an elevated rate of HTTP 5xx errors in Ashburn (IAD). The incident is now resolved, and systems are fully operational.

ResolvedStarted Oct 16, 10:15 UTCResolved Oct 16, 11:24 UTC
ResolvedStarted Oct 16, 09:20 UTCResolved Oct 16, 09:59 UTC
ResolvedStarted Oct 16, 06:48 UTCResolved Oct 16, 07:30 UTC

Cloudflare investigated and resolved issues with network performance in Bangkok, Thailand. There may have been elevated response times and an increase in 5xx errors between 06:48 and 07:30 UTC. This has been resolved and normal operations have resumed.

ResolvedStarted Oct 16, 01:13 UTCResolved Oct 16, 02:11 UTC

Between 01:13 AM and 02:11 AM UTC, network performance at our ICN-A colo in Seoul was impacted. Users downstream of KINX may have experienced increased latency (TTFB) and elevated Network Error Logging (NEL) metrics due to network path congestion. Performance metrics have since returned to normal baselines, and the is…

ResolvedStarted Oct 16, 00:01 UTCResolved Oct 16, 01:06 UTC

Workers Cron Triggers have stabilized

ResolvedStarted Oct 13, 10:14 UTCResolved Oct 16, 00:36 UTC
ResolvedStarted Oct 15, 20:48 UTCResolved Oct 15, 21:38 UTC

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…

4,322 members already hereThey read, write, comment and vote. 0 verified · 31 joined this year