Skip to content

Outage tracker

Amplitude: the full evidence record

The last 24 hours in detail, 11 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 11 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

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
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-East100.00%1247
US-West100.00%1241
Europe100.00%1184
Asia-Pacific100.00%1056

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
Sep 2025not tracked
Oct 2025not tracked
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

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.

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.
Brief Service DisruptionAll systems operational
Aug 25, 2026, 9:54 PM UTC to Aug 25, 2026, 8:48 PM UTC (0 min)resolved
their latest update (Aug 25, 2026, 8:48 PM UTC): Incident timeline Resolved — Amplitude is accessible once again, and customers should be able to access the platform as expected. Posted Aug 25, 2026 - 14:03 PT Investigating — Since approximately 13:48 PT, some customers may have experienced a brief interruption when using Am…
Login Page Unavailable for New Sign-insAll systems operational
Aug 25, 2026, 2:06 AM UTC to Aug 25, 2026, 3:23 AM UTC (1h 16m)resolved
their latest update (Aug 25, 2026, 3:23 AM UTC): A fix was deployed, and the issue was fully resolved.
AI Controls unexpectedly displayed as “Admin preview”All systems operational
Aug 19, 2026, 5:41 PM UTC to Aug 19, 2026, 5:41 PM UTC (0 min)resolved
their latest update (Aug 19, 2026, 5:41 PM UTC): On 2026-08-19 at 10:41:25 AM PT, some customers who had not explicitly enabled AI through the AI Controls page were placed in “Admin preview,” and non-admin users could not access AI features. The issue was fully resolved at 12:41 PM PT on 2026-08-19. No data was impacted, and no…
Delay in realtime data processingAll systems operational
Aug 14, 2026, 4:59 AM UTC to Aug 14, 2026, 2:30 AM UTC (0 min)resolved
their latest update (Aug 14, 2026, 2:30 AM UTC): On 2026-08-13 at 7:45 PM PT (2:45 AM UTC on 2026-08-14), we experienced a data ingestion latency. The issue was fully resolved at 8:35 PM PT (3:35 AM UTC on 2026-08-14), and all data has since been recovered. There was no data loss, and no customer action is required.
Delay in realtime data processingMinor incident
Aug 12, 2026, 11:39 PM UTC to Aug 13, 2026, 3:45 AM UTC (4h 7m)resolved
their latest update (Aug 13, 2026, 3:45 AM UTC): This incident has been resolved.
Delay in realtime data processingMinor incident
Aug 2, 2026, 5:45 AM UTC to Aug 2, 2026, 6:12 AM UTC (27 min)resolved
their latest update (Aug 2, 2026, 6:12 AM UTC): This incident has been resolved.
We are actively investigating a delay in our pipeline processingMinor incident
Aug 1, 2026, 2:07 AM UTC to Aug 1, 2026, 3:51 AM UTC (1h 45m)resolved
their latest update (Aug 1, 2026, 3:51 AM UTC): This incident has been resolved.
Intermittent Connectivity IssuesAll systems operational
Jul 24, 2026, 5:05 PM UTC to Jul 24, 2026, 5:05 PM UTC (0 min)resolved
their latest update (Jul 24, 2026, 5:05 PM UTC): Between approximately 2026-07-24 03:39–05:00 PT (10:39–12:00 UTC), some customers may have experienced intermittent connectivity issues while accessing Amplitude or sending data, including connection timeouts. This was caused by an AWS networking disruption in the us-west-2 regio…
We are actively investigating bigquery exports taking a long time to completeMinor incident
Jul 24, 2026, 2:45 PM UTC to Jul 24, 2026, 3:59 PM UTC (1h 14m)resolved
their latest update (Jul 24, 2026, 3:59 PM UTC): This incident has been resolved.

Showing the 10 most recent of 53 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, 9 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.