CheckUpstream measured Amplitude at 100.000% availability across 2827 independent checks (global · api). 30 incidents were recorded in the past 12 months; the most recent resolved 5 days ago after 3 hours. Status signals are polled from Amplitude's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2827 · p95 620ms (30d)
Share of our own checks against Amplitude endpoints that returned Amplitude's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 3 incidents · 28 of 30 days with none posted · 2h 25m of declared impact
Fewer incidents in the last 30 days than 21% of 232 tracked services.
Share of each window with no impact declared by Amplitude
7d
99.416%
30d
99.664%
90d
99.888%
180d
99.497%
1y
99.752%
Downtime like this can be refundable
If you're a paying Amplitude customer, outages in these windows may count against Amplitude's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Amplitude entitlement →Does Amplitude actually matter to you?
A Amplitude outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 26, 15:23 UTC · resolved in 3h 16m · Resolved
Aug 25, 02:06 UTC · resolved in 13m · Resolved
Aug 12, 23:39 UTC · resolved in 4h 15m · Resolved
Live Amplitude status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/amplitude)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Amplitude is currently Operational. CheckUpstream tracks Amplitude in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Amplitude's last resolved incident started 5 days ago and lasted 3h 16m (degraded performance).
Looking for the live "is Amplitude down" view? See the Amplitude Live status page.
Aug 2, 05:45 UTC · resolved in 34m · Resolved
Jul 13, 07:53 UTC · resolved in 46m · Resolved
Jun 18, 19:29 UTC · resolved in 9h 6m · Resolved
Jun 4, 18:55 UTC · resolved in 4h 15m · Resolved
Jun 3, 12:25 UTC · resolved in 35m · Resolved
May 19, 12:45 UTC · resolved in 24m · Resolved
May 14, 21:42 UTC · resolved in 4h 27m · Resolved
May 5, 19:13 UTC · resolved in 36m · Resolved
Apr 29, 08:15 UTC · resolved in 6h 24m · Resolved
Apr 23, 19:56 UTC · resolved in 43m · Resolved
Apr 15, 23:09 UTC · resolved in 2h 10m · Resolved
Amplitude's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Amplitude endpoints. It is the share of checks that returned the expected response, not a figure taken from Amplitude's status page.
Sign up to CheckUpstream and add Amplitude to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Amplitude's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.