lagcheck can I play right now?

Is Cloudflare down right now?

Checked 1 minute ago

Yes — Cloudflare is having problems

Network Performance Issues in Los Angeles — started 8 hours ago.

GitHub, Bitbucket, Twilio, Xero and 5 more are all reporting problems at the same time. Amazon Web Services, DigitalOcean, Supabase, MongoDB Atlas and Elastic Cloud are infrastructure a lot of what we watch runs on. We cannot tell from here whether that is the cause — we are reading status pages, not tracing dependencies — but it is worth ruling out before you blame your own line.

The last 48 hours

A problem is happening now — it started 8 hours ago.

Longer record

64.26%Clear of trouble, 31 days
46Problems seen
133h 14mLongest
8 hoursLast problem
Clear of trouble, each day, last 31 days

This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Cloudflare.

Something was impaired on 35.74% of our checks over that window. That is how often Cloudflare was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 133h 14m.

Day by day

The last 30 days of Cloudflare, one row each.

DayClearUpChecksStartedLongest ended
2026-09-16 so far today 19.67% 100% 122 1
2026-09-15 10.8% 100% 287 1 26h 14m
2026-09-14 85.02% 100% 287 1
2026-09-13 100% 100% 287 none
2026-09-12 55.4% 100% 287 none 15h 10m
2026-09-11 74.56% 100% 287 2 1h 45m
2026-09-10 34.49% 100% 287 1 16h 56m
2026-09-09 60.07% 100% 288 1
2026-09-08 83.97% 100% 287 3 2h 0m
2026-09-07 66.55% 100% 287 3 4h 51m
2026-09-06 78.05% 100% 287 1 5h 20m
2026-09-05 97.21% 100% 287 none 3h 35m
2026-09-04 62.02% 100% 287 3 4h 35m
2026-09-03 79.44% 100% 287 3 72h 48m
2026-09-02 62.37% 100% 287 1 133h 14m
2026-09-01 7.32% 98.61% 287 1 108h 4m
2026-08-31 31.01% 100% 287 2 81h 9m
2026-08-30 51.57% 100% 287 1 56h 49m
2026-08-29 62.02% 100% 287 1 34h 5m
2026-08-28 0% 100% 287 none
2026-08-27 61.32% 100% 287 1
2026-08-26 84.67% 100% 287 2 3h 2m
2026-08-25 37.98% 100% 287 none 18h 17m
2026-08-24 66.9% 100% 287 2 4h 36m
2026-08-23 100% 100% 287 none
2026-08-22 98.26% 100% 287 1 28 min
2026-08-21 88.15% 100% 287 3 1h 45m
2026-08-20 77.08% 100% 288 4 3h 37m
2026-08-19 85.37% 100% 287 3 2h 5m
2026-08-18 100% 100% 287 none

Clear is the share of checks that found nothing wrong at all; Up is the share that found Cloudflare actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.

Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.

Outage history

StartedLastedSeverityWhat happened
2026-09-16 02:03 UTC ongoing having problems Network Performance Issues in Los Angeles
2026-09-14 20:22 UTC 26h 14m having problems Cloudflare Queues issues
2026-09-14 20:22 UTC 17h 44m having problems Cloudflare Queues issues
2026-09-11 19:35 UTC 15h 10m having problems Network Performance Issues with Taiwan datacenter (TPE)
2026-09-11 02:20 UTC 1h 45m having problems SSL Certificate Provisioning Delays for Let's Encrypt
2026-09-10 13:58 UTC 8h 27m having problems DNS Update Delays
2026-09-09 14:25 UTC 16h 56m having problems Cloudflare Workers AI increased errors
2026-09-08 19:39 UTC 51 min having problems Intermittent issues accessing the Dashboard on FireFox and Safari
2026-09-08 03:25 UTC 2h 0m having problems Cache Reserve Issue in Paris
2026-09-08 00:35 UTC 1h 11m having problems Cloudflare Account Member Invite Issue
2026-09-07 14:25 UTC 4h 51m having problems Browser Isolation Session Initialization Failures
2026-09-07 13:02 UTC 53 min having problems Performance degradation affecting TURN service
2026-09-07 05:12 UTC 2h 29m having problems Increased Workflow Instance Creation Errors
2026-09-06 16:36 UTC 5h 20m having problems Service Connectivity Issues in Canberra
2026-09-04 21:10 UTC 3h 35m having problems Elevated number of R2 503 errors in Eastern North America region
2026-09-04 19:55 UTC 15 min having problems Zero Trust Dashboard - Posture Check Visibility Issue
2026-09-04 14:51 UTC 2h 10m having problems Cache Purging Errors
2026-09-03 23:35 UTC 4h 35m having problems Workers Builds elevated queue times
2026-08-31 18:47 UTC 72h 48m having problems HTTP/3 issue affecting R2 custom domains
2026-09-03 09:21 UTC 20 min having problems Increased HTTP 5xx Errors in Hong Kong.

What Cloudflare actually publishes

Cloudflare publishes over 460 components — one for nearly every datacenter — which makes their status page unusually detailed and unusually easy to misread.

Matching the symptom to the cause

Several unrelated games or sites failing at once
That pattern points at infrastructure rather than any one vendor. A lot of gaming services sit behind Cloudflare, so one bad region can look like several separate outages.

Where this reading can mislead you

On any ordinary day roughly 40 of Cloudflare's 460+ components are re-routed or in maintenance while the service is completely fine. Taking the worst component would report a partial outage almost permanently. We keep Cloudflare's own banner unless an incident is open or a quarter of components are unhappy — this specific service is why that rule exists.

When the status page says green and you still can't play

Status pages report the vendor's view of their own service, and they lag real outages — often by many minutes, sometimes by hours, because a human usually has to confirm before anything is posted. They also can't see the two things most likely to be wrong at your end.

The first is your own connection under load. A line that idles at 20 ms can jump to 300 ms the moment something starts uploading, which drops you from sessions and looks exactly like a server fault. Your plan speed says nothing about this; it's called bufferbloat and almost nobody measures it.

The second is where everyone else in your group is. A service can be healthy in your region and unwell in theirs, and if one person is hosting, their problem is everyone's problem.

Playing with people elsewhere

Cloudflare being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.

Other services we watch

Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.