Skip to content

Outage tracker / Amplitude

Is Amplitude down?

I'm having a problem

Vendor reports an incidentWhat Amplitude reports

Amplitude reports an incident on its status page: Delayed S3 export.

Impact: minor. Since 2026-11-05 14:22 UTC.

Latest update, 2026-11-05 15:32 UTC: We are continuing to monitor for any further issues. We will provide another update in 30 minutes.

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 1 minute ago

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

As of Nov 5, 2026, 3:41 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 Nov 5, 2026, 3:41 PM UTC
US-East639 msChecks passing
US-West227 msChecks passing
Europe2154 msChecks passing
Asia-Pacific483 msChecks passing
US-Central399 msChecks passing
Canada216 msChecks passing
UK553 msChecks passing
Southeast Asia2183 msChecks passing
Australia726 msChecks passing
South America959 msChecks passing
their status pagetheir claim, not our reading

Amplitude reports: Minor incident (“Partially Degraded Service”)

from Amplitude's own status page, checked Nov 5, 2026, 3:14 PM UTC

Amplitude reports an active incident: Delayed S3 export (minor incident, since Nov 5, 2026, 2:22 PM UTC)

Amplitude's status page reports Partially Degraded Service. Our checks of Amplitude currently pass with normal latency. Our checks currently pass from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

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 ExportDegraded performance
  • Marketing WebsiteOperational
  • Session ReplayDegraded performance
  • 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.4sp95 · 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-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.1s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 896ms2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 966ms2026-10-25 UTC: p95 881ms2026-10-26 UTC: p95 968ms2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 903ms2026-11-01 UTC: p95 937ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
2.3sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 582ms2026-10-20 UTC: p95 627ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 363ms2026-10-24 UTC: p95 315ms2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 928ms2026-10-28 UTC: p95 536ms2026-10-29 UTC: p95 566ms2026-10-30 UTC: p95 390ms2026-10-31 UTC: p95 992ms2026-11-01 UTC: p95 891ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Europe
2.1sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 799ms2026-10-20 UTC: p95 672ms2026-10-21 UTC: p95 679ms2026-10-22 UTC: p95 711ms2026-10-23 UTC: p95 667ms2026-10-24 UTC: p95 639ms2026-10-25 UTC: p95 583ms2026-10-26 UTC: p95 584ms2026-10-27 UTC: p95 928ms2026-10-28 UTC: p95 857ms2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 979ms2026-10-31 UTC: p95 888ms2026-11-01 UTC: p95 733ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Asia-Pacific
2.2sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.9s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 732ms2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 696ms2026-11-01 UTC: p95 757ms2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
US-Central
1.0sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 783ms2026-10-20 UTC: p95 914ms2026-10-21 UTC: p95 361ms2026-10-22 UTC: p95 433ms2026-10-23 UTC: p95 727ms2026-10-24 UTC: p95 713ms2026-10-25 UTC: p95 749ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 671ms2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 853ms2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 947ms2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Canada
1.1sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 821ms2026-10-20 UTC: p95 921ms2026-10-21 UTC: p95 661ms2026-10-22 UTC: p95 502ms2026-10-23 UTC: p95 417ms2026-10-24 UTC: p95 437ms2026-10-25 UTC: p95 702ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 931ms2026-10-28 UTC: p95 954ms2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
1.2sp95 · 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-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 940ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 579ms2026-10-22 UTC: p95 724ms2026-10-23 UTC: p95 604ms2026-10-24 UTC: p95 598ms2026-10-25 UTC: p95 586ms2026-10-26 UTC: p95 609ms2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 668ms2026-10-30 UTC: p95 662ms2026-10-31 UTC: p95 654ms2026-11-01 UTC: p95 800ms2026-11-02 UTC: p95 768ms2026-11-03 UTC: p95 576ms2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Southeast Asia
2.4sp95 · 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-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.0s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Australia
2.0sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.3s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 960ms2026-10-26 UTC: p95 945ms2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 3.2s2026-10-29 UTC: p95 3.2s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
South America
2.4sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.0s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 6.1s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 987ms2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5

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: 639msstatus code: 400checked: Nov 5, 2026, 3:40 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: 227msstatus code: 400checked: Nov 5, 2026, 3:34 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: 399msstatus code: 400checked: Nov 5, 2026, 3:39 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: 216msstatus code: 400checked: Nov 5, 2026, 3:41 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: 959msstatus code: 400checked: Nov 5, 2026, 3:39 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: 2154msstatus code: 400checked: Nov 5, 2026, 3:34 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: 553msstatus code: 400checked: Nov 5, 2026, 3:39 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: 483msstatus code: 400checked: Nov 5, 2026, 3:23 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: 2183msstatus code: 400checked: Nov 5, 2026, 3:39 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: 726msstatus code: 400checked: Nov 5, 2026, 3:40 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

Session Replay capturing more sessions than configured, 28mdeclared on their status page2026-11-05
Delayed S3 exportdeclared on their status page2026-11-05
Data Ingestion Delays, 1h 15mdeclared on their status page2026-10-26
Delayed/Blocked Event Delivery to Amazon Kinesis Destination, 23mdeclared on their status page2026-10-24
Streaming to External Destinations Unavailable, 4h 38mdeclared on their status page2026-10-22
Amplitude Website Outage, 1mdeclared on their status page2026-10-22
Notice: Amplitude not impacted by recent PHP vulnerabilities, 1mdeclared on their status page2026-10-22
Export API returns 500 errors across multiple organizations, 8mdeclared on their status page2026-10-20

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

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>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

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.