On this page
Is Amplitude Down? How to Tell and What to Do
Amplitude powers product analytics for thousands of SaaS teams — tracking user events, funnels, retention, and cohorts. When it degrades, your data pipeline silently drops events. By the time you notice a gap in your charts, hours of behavioral data may already be lost.
Statusfield brings reported Amplitude incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
Follow Amplitude incidents with your team
Statusfield brings reported status for Amplitude together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Common Signs of an Amplitude Outage
| Symptom | What's likely happening |
|---|---|
| Event counts flat or dropping unexpectedly | Ingestion API is degraded or rejecting events |
| Charts in dashboards not updating | Data processing or query pipeline is lagging |
| SDK throwing network errors in browser console | Amplitude ingestion endpoint is unreachable |
| Funnels showing 0 completions despite user activity | Event processing is backlogged or dropped |
| Cohort syncs not updating in destination tools | Cohort export pipeline is degraded |
| Behavioral emails not triggering | Amplitude → downstream integration sync is failing |
| Dashboard load times extremely slow | Query / serving infrastructure is overloaded |
How to Confirm It's Amplitude, Not You
Before changing SDK configuration or escalating internally, rule out your own setup:
1. Check SDK network requests in browser DevTools
Open DevTools → Network → filter for api.amplitude.com or api2.amplitude.com. A healthy event send returns HTTP 200. Repeated 500 or connection-refused errors with no change to your code indicate a platform issue.
2. Verify your API key is active
A 403 or 401 response means credential issue — not a platform outage. Confirm in your Amplitude project settings that the API key being used is active and not rotated.
3. Check ingestion vs. querying separately
Amplitude has separate pipelines for event ingestion (accepting new events) and data querying (serving dashboards). An ingestion outage drops new data. A query outage makes dashboards unavailable but data is not lost — it will appear once the query layer recovers. These fail independently.
4. Review SDK batch upload behavior
Amplitude SDKs buffer events client-side and send them in batches. During a degradation, the SDK will retry. Check whether events are queuing up in the SDK buffer (visible in the SDK's debug logs) — this means data is not lost yet, but it will be if the buffer overflows or the session ends.
Use vendor reports as investigation context
Statusfield brings reported Amplitude incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.
What to Do During an Amplitude Outage
Immediate (first 5 minutes)
- Confirm ingestion vs. dashboards — are new events failing to ingest, or are existing dashboards just slow/unavailable? These require different responses.
- Check SDK buffer size — Amplitude SDKs have a configurable event queue. If events are queuing but not sending, the data is not yet lost — as long as the session stays open and the buffer doesn't overflow.
- Evaluate your data criticality — if you're in a high-stakes period (launch, A/B test, campaign), note the exact time ingestion degraded so you can annotate charts later.
- Check downstream integrations — Amplitude → Slack, Salesforce, or email tools may stop firing. Alert those teams.
Communication (first 15 minutes)
- Alert your product and data teams that analytics may be unreliable for this window.
- If you have a live experiment running, note that the data gap will need to be documented for statistical validity.
- Do not make product decisions based on Amplitude data until ingestion is confirmed recovered.
Recovery
- After Amplitude recovers, check ingestion timestamps to identify the exact gap window.
- Compare event counts before and after the outage to estimate data loss vs. delayed processing (Amplitude sometimes backfills after recovery).
- Annotate your dashboards with the outage window so future trend analysis accounts for the gap.
Amplitude Components and What Each Outage Looks Like
Amplitude is not one monolithic service — components can degrade independently:
| Component | Impact when degraded |
|---|---|
| HTTP API (ingestion) | Events fail to ingest; SDK retries exhaust; data is lost |
| Batch API | Bulk server-side event uploads fail |
| Data processing pipeline | Events ingested but not appearing in dashboards (delay, not loss) |
| Dashboard / query layer | Charts and funnels unavailable; data intact but inaccessible |
| Cohort sync | Cohorts not updating in connected tools (HubSpot, Braze, etc.) |
| Behavioral email triggers | Event-based email automations stop firing |
| Data export (S3/BigQuery) | Scheduled exports fail; no new data lands in your data warehouse |
A data processing delay is recoverable — events are queued and will appear once the backlog clears. An ingestion API outage is not recoverable for events that were never buffered by the SDK.
Match the check to the failure you need to catch
Follow supported Amplitude components for vendor-reported incidents. Add a public HTTPS check for your own website or API and define acceptable response codes, response time and body checks. A successful request is evidence about that endpoint, not proof that an entire customer journey works.
Use application logs and end-to-end tests for authenticated workflows, data correctness and transactions. Statusfield brings the monitoring results and vendor context together; it does not run a complete checkout or login flow.
Bring Amplitude updates to your team
Follow reported Amplitude status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Eligible first-time customers can start a free trial, no credit card required.
Follow Amplitude incidents with your team
Follow Amplitude and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
FAQ
Is Amplitude down right now?
This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.
How can I get alerts about Amplitude incidents?
Follow reported Amplitude status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Does an operational Amplitude status mean my application is working?
No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.
Browse the service catalog and plans and alert destinations.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.