Skip to main content
Amplitude

We are actively investigating bigquery exports taking a long time to complete

Degraded Lasted 1h 14m · started · Amplitude's page

Level
confirmed
Worst impact
Degraded
Components
Data Export
Down Index
31of 100

What to do

  • Check whether you use Amplitude Data Export. 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 1h 14m it lasted.

    Anything that failed between 2026-07-24 14:45 UTC and 2026-07-24 15:59 UTC may need a replay.
  • Subscribe to Amplitude's feed to hear about the next one first. RSS feed

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

Updates from Amplitude 3

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    The jobs waiting on google's end have started recovering and we are seeing jobs making progress within Amplitude too

    provider

  3. 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-31f4f9ce23

Is Amplitude still down?

No, this incident was resolved 2026-07-24 15:59 UTC. For Amplitude's live state, see https://down.guide/amplitude.

How long did it last?

1h 14m, from 2026-07-24 14:45 UTC to 2026-07-24 15:59 UTC, by the times Amplitude posted.

What was affected?

Amplitude named Data Export.

What caused it?

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

Where does this come from?

Amplitude's official status page, https://amplitude.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.