Skip to content

Outage tracker / Amplitude

Is Amplitude down?

I'm having a problem

Vendor reports no incidentWhat Amplitude reports

Amplitude reports no incident on its status page.

As of the last successful poll, 2026-10-19 21:26 UTC.

Amplitude's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 5 minutes ago

Our checks of Amplitude pass from all 10 regions we check.

As of Oct 19, 2026, 9:22 PM UTC, RealUptime's checks of Amplitude passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 19, 2026, 9:22 PM UTC
US-East1110 msChecks passing
US-West260 msChecks passing
Europe493 msChecks passing
Asia-Pacific1930 msChecks passing
US-Central593 msChecks passing
Canada439 msChecks passing
UK487 msChecks passing
Southeast Asia769 msChecks passing
Australia628 msChecks passing
South America625 msChecks passing
their status pagetheir claim, not our reading

Amplitude reports: All systems operational (“All Systems Operational”)

from Amplitude's own status page, checked Oct 19, 2026, 9:19 PM UTC
Amplitude's own status page shows no incident, and our checks of Amplitude pass right now.

Amplitude's own component breakdown, as they publish it

  • Evaluation APIOperational
  • Profile APIOperational
  • Web ApplicationOperational
  • Web ReportingOperational
  • CLI/CodegenOperational
  • Management APIOperational
  • Web ApplicationOperational
  • Web ApplicationOperational
  • Data ProcessingOperational
  • Web ApplicationOperational
  • Data ReceptionOperational
  • Flag Configurations APIOperational
  • Cohort ExportOperational
  • Guides & SurveysOperational
  • Web Experiment ScriptOperational
  • Amazon Web ServicesOperational
  • Event StreamingOperational
  • Data ExportOperational
  • Marketing WebsiteOperational
  • Session ReplayOperational
  • HeatmapsOperational
  • AI FeedbackOperational
  • Resource CenterOperational
  • Agents and ChatOperational
  • MCPOperational

These are Amplitude's components, named and scored by Amplitude. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Amplitude's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Amplitude response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 900ms2026-09-21 UTC: p95 869ms2026-09-22 UTC: p95 845ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 883ms2026-09-26 UTC: p95 675ms2026-09-27 UTC: p95 818ms2026-09-28 UTC: p95 864ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 678ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 700ms2026-10-04 UTC: p95 720ms2026-10-05 UTC: p95 695ms2026-10-06 UTC: p95 675ms2026-10-07 UTC: p95 524ms2026-10-08 UTC: p95 543ms2026-10-09 UTC: p95 553ms2026-10-10 UTC: p95 664ms2026-10-11 UTC: p95 705ms2026-10-12 UTC: p95 771ms2026-10-13 UTC: p95 791ms2026-10-14 UTC: p95 626ms2026-10-15 UTC: p95 763ms2026-10-16 UTC: p95 783ms2026-10-17 UTC: p95 772ms2026-10-18 UTC: p95 879ms2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
US-West
591msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 618ms2026-09-21 UTC: p95 657ms2026-09-22 UTC: p95 688ms2026-09-23 UTC: p95 597ms2026-09-24 UTC: p95 870ms2026-09-25 UTC: p95 956ms2026-09-26 UTC: p95 668ms2026-09-27 UTC: p95 615ms2026-09-28 UTC: p95 675ms2026-09-29 UTC: p95 669ms2026-09-30 UTC: p95 610ms2026-10-01 UTC: p95 379ms2026-10-02 UTC: p95 244ms2026-10-03 UTC: p95 306ms2026-10-04 UTC: p95 391ms2026-10-05 UTC: p95 428ms2026-10-06 UTC: p95 526ms2026-10-07 UTC: p95 272ms2026-10-08 UTC: p95 289ms2026-10-09 UTC: p95 305ms2026-10-10 UTC: p95 576ms2026-10-11 UTC: p95 457ms2026-10-12 UTC: p95 345ms2026-10-13 UTC: p95 457ms2026-10-14 UTC: p95 356ms2026-10-15 UTC: p95 295ms2026-10-16 UTC: p95 375ms2026-10-17 UTC: p95 294ms2026-10-18 UTC: p95 531ms2026-10-19 UTC: p95 591ms
Sep 20Oct 4Oct 19
Europe
806msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 953ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 981ms2026-09-29 UTC: p95 976ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 744ms2026-10-02 UTC: p95 960ms2026-10-03 UTC: p95 904ms2026-10-04 UTC: p95 740ms2026-10-05 UTC: p95 805ms2026-10-06 UTC: p95 860ms2026-10-07 UTC: p95 598ms2026-10-08 UTC: p95 681ms2026-10-09 UTC: p95 618ms2026-10-10 UTC: p95 762ms2026-10-11 UTC: p95 872ms2026-10-12 UTC: p95 965ms2026-10-13 UTC: p95 798ms2026-10-14 UTC: p95 740ms2026-10-15 UTC: p95 709ms2026-10-16 UTC: p95 818ms2026-10-17 UTC: p95 951ms2026-10-18 UTC: p95 967ms2026-10-19 UTC: p95 806ms
Sep 20Oct 4Oct 19
Asia-Pacific
1.9sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 968ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 990ms2026-09-30 UTC: p95 922ms2026-10-01 UTC: p95 808ms2026-10-02 UTC: p95 923ms2026-10-03 UTC: p95 944ms2026-10-04 UTC: p95 940ms2026-10-05 UTC: p95 990ms2026-10-06 UTC: p95 932ms2026-10-07 UTC: p95 908ms2026-10-08 UTC: p95 738ms2026-10-09 UTC: p95 735ms2026-10-10 UTC: p95 672ms2026-10-11 UTC: p95 738ms2026-10-12 UTC: p95 884ms2026-10-13 UTC: p95 851ms2026-10-14 UTC: p95 648ms2026-10-15 UTC: p95 748ms2026-10-16 UTC: p95 794ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19
US-Central
785msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 719ms2026-09-21 UTC: p95 727ms2026-09-22 UTC: p95 643ms2026-09-23 UTC: p95 749ms2026-09-24 UTC: p95 851ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 774ms2026-09-28 UTC: p95 786ms2026-09-29 UTC: p95 684ms2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 411ms2026-10-02 UTC: p95 308ms2026-10-03 UTC: p95 299ms2026-10-04 UTC: p95 503ms2026-10-05 UTC: p95 537ms2026-10-06 UTC: p95 467ms2026-10-07 UTC: p95 490ms2026-10-08 UTC: p95 438ms2026-10-09 UTC: p95 362ms2026-10-10 UTC: p95 583ms2026-10-11 UTC: p95 602ms2026-10-12 UTC: p95 580ms2026-10-13 UTC: p95 718ms2026-10-14 UTC: p95 561ms2026-10-15 UTC: p95 488ms2026-10-16 UTC: p95 540ms2026-10-17 UTC: p95 634ms2026-10-18 UTC: p95 893ms2026-10-19 UTC: p95 785ms
Sep 20Oct 4Oct 19
Canada
802msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 684ms2026-09-21 UTC: p95 671ms2026-09-22 UTC: p95 884ms2026-09-23 UTC: p95 924ms2026-09-24 UTC: p95 751ms2026-09-25 UTC: p95 746ms2026-09-26 UTC: p95 656ms2026-09-27 UTC: p95 778ms2026-09-28 UTC: p95 818ms2026-09-29 UTC: p95 838ms2026-09-30 UTC: p95 785ms2026-10-01 UTC: p95 443ms2026-10-02 UTC: p95 434ms2026-10-03 UTC: p95 435ms2026-10-04 UTC: p95 517ms2026-10-05 UTC: p95 476ms2026-10-06 UTC: p95 546ms2026-10-07 UTC: p95 533ms2026-10-08 UTC: p95 388ms2026-10-09 UTC: p95 400ms2026-10-10 UTC: p95 421ms2026-10-11 UTC: p95 421ms2026-10-12 UTC: p95 397ms2026-10-13 UTC: p95 439ms2026-10-14 UTC: p95 388ms2026-10-15 UTC: p95 421ms2026-10-16 UTC: p95 473ms2026-10-17 UTC: p95 624ms2026-10-18 UTC: p95 752ms2026-10-19 UTC: p95 802ms
Sep 20Oct 4Oct 19
UK
940msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1s2026-09-21 UTC: p95 960ms2026-09-22 UTC: p95 977ms2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 939ms2026-10-01 UTC: p95 626ms2026-10-02 UTC: p95 629ms2026-10-03 UTC: p95 628ms2026-10-04 UTC: p95 616ms2026-10-05 UTC: p95 741ms2026-10-06 UTC: p95 723ms2026-10-07 UTC: p95 661ms2026-10-08 UTC: p95 717ms2026-10-09 UTC: p95 664ms2026-10-10 UTC: p95 639ms2026-10-11 UTC: p95 652ms2026-10-12 UTC: p95 643ms2026-10-13 UTC: p95 583ms2026-10-14 UTC: p95 538ms2026-10-15 UTC: p95 545ms2026-10-16 UTC: p95 632ms2026-10-17 UTC: p95 768ms2026-10-18 UTC: p95 854ms2026-10-19 UTC: p95 940ms
Sep 20Oct 4Oct 19
Southeast Asia
2.0sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 995ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 924ms2026-10-07 UTC: p95 909ms2026-10-08 UTC: p95 915ms2026-10-09 UTC: p95 970ms2026-10-10 UTC: p95 955ms2026-10-11 UTC: p95 990ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 972ms2026-10-15 UTC: p95 895ms2026-10-16 UTC: p95 930ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.0s
Sep 20Oct 4Oct 19
Australia
1.2sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 935ms2026-10-02 UTC: p95 830ms2026-10-03 UTC: p95 818ms2026-10-04 UTC: p95 987ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 976ms2026-10-08 UTC: p95 929ms2026-10-09 UTC: p95 752ms2026-10-10 UTC: p95 799ms2026-10-11 UTC: p95 832ms2026-10-12 UTC: p95 903ms2026-10-13 UTC: p95 956ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 779ms2026-10-16 UTC: p95 940ms2026-10-17 UTC: p95 900ms2026-10-18 UTC: p95 944ms2026-10-19 UTC: p95 1.2s
Sep 20Oct 4Oct 19
South America
1.0sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 983ms2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 900ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 921ms2026-10-08 UTC: p95 852ms2026-10-09 UTC: p95 821ms2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 876ms2026-10-16 UTC: p95 980ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 849ms2026-10-19 UTC: p95 1.0s
Sep 20Oct 4Oct 19

Check your own site while you wait on Amplitude

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Amplitude. It cannot diagnose Amplitude's own systems.

What we measured, function by function

Amplitude answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Amplitude reports an incident on its status page, and again when it reports it resolved.

Get an email when Amplitude reports an incident

Email me when Amplitude reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Amplitude's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1110msstatus code: 400checked: Oct 19, 2026, 9:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Amplitude normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 260msstatus code: 400checked: Oct 19, 2026, 9:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Amplitude normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 593msstatus code: 400checked: Oct 19, 2026, 9:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Amplitude normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 439msstatus code: 400checked: Oct 19, 2026, 9:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Amplitude normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 625msstatus code: 400checked: Oct 19, 2026, 9:17 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Amplitude normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 493msstatus code: 400checked: Oct 19, 2026, 9:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Amplitude normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 487msstatus code: 400checked: Oct 19, 2026, 9:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Amplitude normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1930msstatus code: 400checked: Oct 19, 2026, 9:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Amplitude normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 769msstatus code: 400checked: Oct 19, 2026, 9:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Amplitude normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 628msstatus code: 400checked: Oct 19, 2026, 9:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Amplitude normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Amplitude, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Amplitude yet, which is not evidence that nothing is wrong.

Recent probe events

We are actively investigating an issue with our ingestion systems lagging, 1h 56mdeclared on their status page2026-10-17
Degraded Performance- Funnel charts renders as white text on a white/near-white background in light theme, 1mdeclared on their status page2026-10-13
BigQuery exports are lagging for US., 1h 31mdeclared on their status page2026-10-08
Guides and Surveys Service Disruption, 1mdeclared on their status page2026-10-05
Amplitude- Platform Loading Issues, 9mdeclared on their status page2026-10-02
We are actively investigating an incident in our data exports, 5h 24mdeclared on their status page2026-09-28
Export Destinations data delivery issue, 1h 34mdeclared on their status page2026-09-24
Export Destinations data delivery issue, 6h 5mdeclared on their status page2026-09-23

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Amplitude since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Amplitude covering any window you pick, with our check readings and Amplitude's own claim at the time, side by side.

Full check history for Amplitude: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Amplitude uptime by RealUptime's checksLive, from this page's own readings.
[![Amplitude uptime by RealUptime's checks](https://realuptime.io/outages/amplitude/badge.svg?days=30)](https://realuptime.io/outages/amplitude)
<a href="https://realuptime.io/outages/amplitude"><img src="https://realuptime.io/outages/amplitude/badge.svg?days=30" alt="Amplitude uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Amplitude down?", https://realuptime.io/outages/amplitude. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api2.amplitude.com/2/httpapi
secondary
https://amplitude.com/
secondary
https://status.amplitude.com/api/v2/status.json

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api2.amplitude.com

RealUptime is not affiliated with Amplitude; the name identifies what we checked, and nothing here speaks for Amplitude's own team. We send a single web request to Amplitude from 10 regions on our own schedule and time the response. We do not see inside Amplitude's systems, do not use an account or real transaction, and are not the same signal Amplitude's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Amplitude is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.