Is Amplitude Down?

No — Amplitude is up

Reachable from all 8 checked regions

Average response time: 1004ms

Last checked 33 minutes ago · checks run every 6 hours

Official status page: https://status.amplitude.com

Amplitude uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

996ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 14 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

14-day clean streak

Jul 19 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr

557ms

DNS 0ms TCP 0ms TLS 186ms TTFB 410ms

fra

1136ms

DNS 0ms TCP 1ms TLS 425ms TTFB 836ms

gru

1310ms

DNS 0ms TCP 5ms TLS 521ms TTFB 933ms

iad

613ms

DNS 0ms TCP 1ms TLS 173ms TTFB 468ms

jnb

2077ms

DNS 0ms TCP 2ms TLS 901ms TTFB 1444ms

lax

416ms

DNS 0ms TCP 0ms TLS 74ms TTFB 303ms

lhr

984ms

DNS 0ms TCP 1ms TLS 383ms TTFB 702ms

nrt

1018ms

DNS 0ms TCP 1ms TLS 295ms TTFB 789ms

ord

482ms

DNS 0ms TCP 1ms TLS 134ms TTFB 346ms

What Amplitude does

Amplitude is a product analytics platform that records user behaviour events from web and mobile apps and turns them into funnels, retention curves and cohorts. Product and growth teams use it to decide what to build next. It also runs feature flags and experiments, which puts part of it in the request path of applications rather than purely in reporting.

What an outage looks like

Charts fail to load, or load with data that stops short of the current hour. Event ingestion can fail separately from reporting, so the dashboard works while recent events never appear. Scheduled data exports and cohort syncs to downstream tools do not arrive. If you use Amplitude Experiment, flag evaluation may fall back to default values in your application.

What to do about it

Check status.amplitude.com, which lists Data Reception and Data Processing separately from Web Reporting and the Web Application, so an ingestion incident and a dashboard incident look different there. Evaluation API, Flag Configurations API and Profile API are listed individually, which matters if flags are in your request path. Confirm your SDK has a sensible default for every flag before assuming the fallback behaved.

Is it down for everyone, or just you?

If this page says Amplitude is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Amplitude outage FAQ

Are events lost during an Amplitude outage?

Usually they are delayed rather than lost. Amplitude SDKs queue events on the client and retry, and Data Reception is a separate component from Data Processing, so events can be accepted while processing lags behind. Mobile clients buffer across app restarts, browsers less reliably. Expect charts to backfill after recovery, and compare event volume for the outage window against a normal day before treating the gap as real.

Does an Amplitude outage affect my application?

Only if you use Amplitude Experiment for feature flags. Plain analytics tracking is fire-and-forget, so an outage costs you data rather than availability. Flag evaluation is different: the Evaluation API and Flag Configurations API are in the request path, and if your SDK cannot reach them it falls back to whatever default you configured. That default is worth checking before an incident rather than during one.

Why is my dashboard loading but showing no recent data?

That pattern points at ingestion rather than reporting. Web Reporting and Data Reception are separate components on the status page, so the interface can be healthy while incoming events are stalled. The give-away is that historical charts look normal and only the most recent hours are flat. Check Data Reception and Data Processing specifically rather than relying on the overall status banner.

Will scheduled exports and cohort syncs catch up?

Cohort Export and Data Export are listed as their own components, so they can fail while the rest of Amplitude works. A missed scheduled export is generally not retried on its own timetable, so downstream tools that expected a file may simply have an older one. After an incident, check whether the destination actually received the run rather than assuming the schedule resumed.

How we measure this

We request Amplitude's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Amplitude publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Amplitude goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required