Skip to main content
Cloudflare

Cloudflare Analytics API latency out of AMS

Degraded Lasted 18m · started · Cloudflare's page

Level
confirmed
Worst impact
Degraded
Components
Analytics, Amsterdam, Netherlands - (AMS)
Regions
eu
Down Index
19of 100

What to do

  • Check whether you use Cloudflare Analytics, Amsterdam, Netherlands - (AMS) in eu. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 18m it lasted.

    Anything that failed between 2026-06-04 09:08 UTC and 2026-06-04 09:27 UTC may need a replay.
  • Subscribe to Cloudflare's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Cloudflare 1

  1. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-0039d302f4

Is Cloudflare still down?

No, this incident was resolved 2026-06-04 09:27 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.

How long did it last?

18m, from 2026-06-04 09:08 UTC to 2026-06-04 09:27 UTC, by the times Cloudflare posted.

What was affected?

Cloudflare named Analytics, Amsterdam, Netherlands - (AMS) in eu.

What caused it?

Cloudflare hasn't published a root cause. If it does, it shows here.

Where does this come from?

Cloudflare's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.