Skip to content

Outage tracker

Amplitude: the full evidence record

The last 24 hours in detail, 46 days of measured availability, a 12-month summary, our own incident log, Amplitude's declared record, and how the two compare.

← Back to Amplitude's live status

We started measuring Amplitude on August 22, 2026, which is 46 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see Amplitude go down

Measured by our own probes from ten regions, not Amplitude's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Amplitude's own status page declared. Below it, any public chatter we saw about Amplitude and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Amplitude's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Amplitude in the last 24 hours, which is not evidence that nothing is wrong.
Amplitude's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Amplitude's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Amplitude next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East99.97%6276
US-West100.00%6269
Europe100.00%6197
Asia-Pacific100.00%5957
US-Central100.00%2399
Canada100.00%2398
UK100.00%2397
Southeast Asia100.00%2365
Australia100.00%2361
South America99.96%2387

Monthly summary

Tracking Amplitude since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Amplitude: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Amplitude's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Amplitude in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Amplitude's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Amplitude since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Amplitude's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Guides and Surveys Service DisruptionAll systems operational
Oct 5, 2026, 6:56 PM UTC to Oct 5, 2026, 6:56 PM UTC (0 min)resolved
their latest update (Oct 5, 2026, 6:56 PM UTC): Between 11:40 AM and 11:48 AM PT on October 5, 2026, Amplitude experienced a full outage of the Guides and Surveys service. During this time, users may have been unable to create, publish, or edit Guides and Surveys, or may have seen Guides and Surveys fail to load for end users.…
Amplitude- Platform Loading IssuesAll systems operational
Oct 2, 2026, 6:35 PM UTC to Oct 2, 2026, 6:43 PM UTC (9 min)resolved
their latest update (Oct 2, 2026, 6:43 PM UTC): The issue has been resolved, and the platform is operating normally again. Our Engineering team will continue to monitor the platform closely to ensure everything remains stable. Thank you for your patience and understanding while we worked to resolve this issue.
We are actively investigating an incident in our data exportsMinor incident
Sep 28, 2026, 9:09 PM UTC to Sep 29, 2026, 2:33 AM UTC (5h 24m)resolved
their latest update (Sep 29, 2026, 2:33 AM UTC): This incident has been resolved.
Export Destinations data delivery issueMinor incident
Sep 24, 2026, 7:47 PM UTC to Sep 24, 2026, 9:22 PM UTC (1h 34m)resolved
their latest update (Sep 24, 2026, 9:22 PM UTC): This incident has been resolved. We don't expect any data loss, and no action is required on your end.
Export Destinations data delivery issuePartial outage
Sep 23, 2026, 8:02 AM UTC to Sep 23, 2026, 2:07 PM UTC (6h 5m)resolved
their latest update (Sep 23, 2026, 2:07 PM UTC): This incident has been resolved. All affected export jobs have fully recovered and are running normally. We don't expect any data loss, and no action is required on your end.
Snowflake Data Share export delivery issuePartial outage
Sep 22, 2026, 6:49 PM UTC to Sep 23, 2026, 12:53 AM UTC (6h 4m)resolved
their latest update (Sep 23, 2026, 12:53 AM UTC): The authentication issue affecting Snowflake Data Share delivery has been resolved. Snowflake Data Share exports are operating normally. No data loss is expected, and no customer action is needed.
Realtime Data Pipeline DelayMinor incident
Sep 17, 2026, 8:05 PM UTC to Sep 17, 2026, 9:15 PM UTC (1h 11m)resolved
their latest update (Sep 17, 2026, 9:15 PM UTC): From approximately 11:30 AM PDT (18:30 UTC) to 2:14 PM PDT (21:14 UTC), Amplitude experienced delays affecting the realtime data pipeline. Some data may have been delayed before appearing in Amplitude in real time. The issue has been resolved. There is no data loss, and no custo…
S3 export delivery permissions - ResolvedAll systems operational
Sep 11, 2026, 12:19 AM UTC to Sep 9, 2026, 8:32 PM UTC (0 min)resolved
their latest update (Sep 9, 2026, 8:32 PM UTC): Some S3 export files delivered between September 9 at 20:32 UTC and September 10 at 04:01 UTC were missing the bucket-owner-full-control permission, which prevented affected customers from reading them. The issue is resolved. Exports moving forward and outside this timeframe are …
We are actively investigating an issue with our realtime ingestion pipelines.Minor incident
Sep 10, 2026, 3:07 AM UTC to Sep 10, 2026, 4:01 AM UTC (54 min)resolved
their latest update (Sep 10, 2026, 4:01 AM UTC): This incident has been resolved.
We are actively investigating a processing delay in our realtime pipelineMinor incident
Aug 26, 2026, 3:23 PM UTC to Aug 26, 2026, 6:38 PM UTC (3h 15m)resolved
their latest update (Aug 26, 2026, 6:38 PM UTC): This incident has been resolved.

Showing the 10 most recent of 62 incidents Amplitude has declared in the history we hold.

These entries are Amplitude's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Amplitude's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Amplitude's own status page on August 22, 2026, 44 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Amplitude since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Amplitude decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Amplitude believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.