Skip to content

Outage tracker / Amplitude

Is Amplitude down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Amplitude from all 10 regions we check.

As of Oct 5, 2026, 9:03 PM UTC, Amplitude answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Amplitude (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 9:03 PM UTC
US-East578 msOperational
US-West123 msOperational
Europe489 msOperational
Asia-Pacific952 msOperational
US-Central155 msOperational
Canada451 msOperational
UK599 msOperational
Southeast Asia785 msOperational
Australia546 msOperational
South America638 msOperational
their status pagetheir claim, not our reading

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

from Amplitude's own status page, checked Oct 5, 2026, 8:58 PM UTC
Our probes and Amplitude's own status page agree: both show Amplitude as reachable 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
679msp95 · 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-06 UTC: p95 801ms2026-09-07 UTC: p95 660ms2026-09-08 UTC: p95 678ms2026-09-09 UTC: p95 645ms2026-09-10 UTC: p95 785ms2026-09-11 UTC: p95 730ms2026-09-12 UTC: p95 668ms2026-09-13 UTC: p95 736ms2026-09-14 UTC: p95 692ms2026-09-15 UTC: p95 698ms2026-09-16 UTC: p95 913ms2026-09-17 UTC: p95 783ms2026-09-18 UTC: p95 890ms2026-09-19 UTC: p95 897ms2026-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 679ms
Sep 6Sep 20Oct 5
US-West
280msp95 · 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-06 UTC: p95 825ms2026-09-07 UTC: p95 953ms2026-09-08 UTC: p95 738ms2026-09-09 UTC: p95 789ms2026-09-10 UTC: p95 771ms2026-09-11 UTC: p95 626ms2026-09-12 UTC: p95 567ms2026-09-13 UTC: p95 667ms2026-09-14 UTC: p95 598ms2026-09-15 UTC: p95 756ms2026-09-16 UTC: p95 790ms2026-09-17 UTC: p95 635ms2026-09-18 UTC: p95 612ms2026-09-19 UTC: p95 676ms2026-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 280ms
Sep 6Sep 20Oct 5
Europe
733msp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.1s2026-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 733ms
Sep 6Sep 20Oct 5
Asia-Pacific
1sp95 · 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-06 UTC: p95 978ms2026-09-07 UTC: p95 900ms2026-09-08 UTC: p95 956ms2026-09-09 UTC: p95 968ms2026-09-10 UTC: p95 900ms2026-09-11 UTC: p95 940ms2026-09-12 UTC: p95 924ms2026-09-13 UTC: p95 960ms2026-09-14 UTC: p95 961ms2026-09-15 UTC: p95 977ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 968ms2026-09-19 UTC: p95 1.3s2026-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 1s
Sep 6Sep 20Oct 5
US-Central
544msp95 · 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-06 UTC: p95 611ms2026-09-07 UTC: p95 590ms2026-09-08 UTC: p95 657ms2026-09-09 UTC: p95 700ms2026-09-10 UTC: p95 602ms2026-09-11 UTC: p95 603ms2026-09-12 UTC: p95 704ms2026-09-13 UTC: p95 711ms2026-09-14 UTC: p95 989ms2026-09-15 UTC: p95 894ms2026-09-16 UTC: p95 618ms2026-09-17 UTC: p95 599ms2026-09-18 UTC: p95 748ms2026-09-19 UTC: p95 785ms2026-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 544ms
Sep 6Sep 20Oct 5
Canada
458msp95 · 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-06 UTC: p95 735ms2026-09-07 UTC: p95 609ms2026-09-08 UTC: p95 779ms2026-09-09 UTC: p95 796ms2026-09-10 UTC: p95 665ms2026-09-11 UTC: p95 692ms2026-09-12 UTC: p95 777ms2026-09-13 UTC: p95 780ms2026-09-14 UTC: p95 972ms2026-09-15 UTC: p95 863ms2026-09-16 UTC: p95 644ms2026-09-17 UTC: p95 672ms2026-09-18 UTC: p95 644ms2026-09-19 UTC: p95 708ms2026-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 458ms
Sep 6Sep 20Oct 5
UK
736msp95 · 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-06 UTC: p95 904ms2026-09-07 UTC: p95 886ms2026-09-08 UTC: p95 962ms2026-09-09 UTC: p95 1s2026-09-10 UTC: p95 928ms2026-09-11 UTC: p95 924ms2026-09-12 UTC: p95 999ms2026-09-13 UTC: p95 946ms2026-09-14 UTC: p95 916ms2026-09-15 UTC: p95 947ms2026-09-16 UTC: p95 934ms2026-09-17 UTC: p95 941ms2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 917ms2026-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 736ms
Sep 6Sep 20Oct 5
Southeast Asia
987msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.3s2026-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 987ms
Sep 6Sep 20Oct 5
Australia
1.1sp95 · 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-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.4s2026-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.1s
Sep 6Sep 20Oct 5
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-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.6s2026-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.0s
Sep 6Sep 20Oct 5

Is it Amplitude, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Amplitude go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Amplitude, and again when they can reach it again. That is our own measurement from ten regions, not Amplitude's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 578msstatus code: 400checked: Oct 5, 2026, 9:00 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
      Operationallatency: 123msstatus code: 400checked: Oct 5, 2026, 9:03 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
      Operationallatency: 155msstatus code: 400checked: Oct 5, 2026, 8:47 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
      Operationallatency: 451msstatus code: 400checked: Oct 5, 2026, 8:49 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
    Operationallatency: 638msstatus code: 400checked: Oct 5, 2026, 8:45 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 489msstatus code: 400checked: Oct 5, 2026, 9:03 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
      Operationallatency: 599msstatus code: 400checked: Oct 5, 2026, 8:47 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 952msstatus code: 400checked: Oct 5, 2026, 8:58 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
      Operationallatency: 785msstatus code: 400checked: Oct 5, 2026, 8:51 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
      Operationallatency: 546msstatus code: 400checked: Oct 5, 2026, 8:57 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 outages

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
Snowflake Data Share export delivery issue, 6h 4mdeclared on their status page2026-09-22
Realtime Data Pipeline Delay, 1h 11mdeclared on their status page2026-09-17
S3 export delivery permissions - Resolved, 1mdeclared on their status page2026-09-11

measured 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 measurements and Amplitude's own claim at the time, side by side.

Full availability history for Amplitude: 90-day availability by region, month-by-month uptime, and every incident 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 measured by RealUptimeLive, from this page's own readings.
[![Amplitude uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Amplitude's SLA implies, from our measurement

At or above your target

We measured none of downtime for Amplitude over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Amplitude's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

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
RealUptime is not affiliated with Amplitude; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.