Checked 1 minutes ago
Increased HTTP 5xx Errors for us-east-1-aws — started 51 hours ago.
A problem is happening now — it started 51 hours ago.
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.
We have only been recording Cloudflare for 3 days, so treat these figures as provisional.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-07-31 02:01 UTC | ongoing | partly down | Increased HTTP 5xx Errors for us-east-1-aws |
Cloudflare publishes over 460 components — one for nearly every datacenter — which makes their status page unusually detailed and unusually easy to misread.
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.
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.
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.