Is Amplitude Down Right Now?
Dashboards loading blank, events not appearing, funnels not updating — Amplitude issues can mean an outage, an ingestion delay, or an SDK misconfiguration. This guide helps you tell the difference and gives you the fastest path to answers.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
Check Amplitude Status Now
Amplitude's official status page shows component health for event ingestion, dashboards, data pipelines, and the Amplitude API:
Amplitude Service Components
Amplitude is composed of multiple independent services. An event ingestion slowdown doesn't mean the app is broken — identify the affected component first.
Receiving events via SDK and HTTP API
Web UI for analysis, notebooks, dashboards
Live event stream and real-time charts
Multi-step conversion and cohort retention
Export to BigQuery, Snowflake, Redshift, S3
Customer Data Platform and audience sync
Feature flags and experiment analysis
Typed analytics SDK generation
Monitor Amplitude from outside your analytics stack
When Amplitude's ingestion pipeline degrades, you lose visibility into your product — and you won't know until a PM asks why the funnel looks wrong. Better Stack monitors Amplitude externally and alerts your team before data gaps compound.
Try Better Stack Free →Diagnostic Playbook
Check status.amplitude.com
Look for incidents affecting event ingestion or the Amplitude app. Subscribe to status page emails for proactive notification.
→ Amplitude Status PageCheck Event Debugger
Go to Data → Event Debugger in Amplitude. This shows events arriving in real-time. If events appear here but not in charts, it's a processing delay — not an SDK issue.
Test the Amplitude HTTP API directly
Send a test event via curl: `curl -X POST https://api2.amplitude.com/2/httpapi -H "Content-Type: application/json" -d '{"api_key":"YOUR_KEY","events":[{"user_id":"debug-test","event_type":"debug_test_event"}]}'`. 200 = API is receiving events.
Check browser console for SDK errors
Open DevTools → Console and look for Amplitude SDK errors. Common issues: wrong API key (initialization fails silently), ad blocker blocking api2.amplitude.com, CORS errors from misconfigured CSP headers.
Verify chart date range and filters
A chart showing "no data" often has a filter or date range issue — not an Amplitude outage. Check: Is the date range correct? Are there user property filters narrowing to zero users? Is the event name spelled correctly?
Amplitude Data Processing Delays (Normal)
Most "Amplitude is down" reports are actually expected processing delays. Here's what's normal:
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Amplitude goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Amplitude + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Frequently Asked Questions
Is Amplitude down right now?
Check the official Amplitude status page at status.amplitude.com. It shows health for event ingestion, the Amplitude app (dashboards/charts), data pipelines (Ampli, ETL connectors), and the Amplitude API. If the status page shows operational but your data is missing or delayed, check: (1) your SDK is correctly initialized, (2) you're looking at the right project and date range, (3) event ingestion can have a natural 5–15 minute delay even during normal operation.
Why are Amplitude charts showing blank or no data?
Amplitude charts appear blank for several reasons: (1) Amplitude outage — check status.amplitude.com, (2) Wrong date range — Amplitude defaults to the last 30 days; if you just launched, events may not appear on charts set to "Last 30 days" without any prior data, (3) Segment filters too narrow — check if you have user property filters that exclude all users, (4) SDK not initialized — check your browser console for Amplitude initialization errors (window.amplitude.init not called, or wrong API key), (5) Events blocked by ad blockers — Amplitude's JavaScript SDK is commonly blocked; use server-side tracking for critical events.
Why is there a data delay in Amplitude?
Amplitude has built-in data processing delays: (1) Real-time charts (Event Segmentation with "Real-time") have a 1–5 minute delay, (2) Most chart types process data with a 15–60 minute delay, (3) Funnel analysis and retention reports can lag 2–4 hours during heavy processing periods, (4) During Amplitude incidents, ingestion delays can stretch to 6–12 hours with backfill after recovery. Always check the "Data Freshness" indicator in chart settings — Amplitude shows the last time data was processed for each chart.
How do I verify Amplitude is receiving my events?
Use Amplitude's Event Debugger (Data → Event Debugger) to see events arriving in real time. For server-side events, use the Amplitude HTTP API directly: `curl -X POST https://api2.amplitude.com/2/httpapi -H "Content-Type: application/json" -d '{"api_key":"YOUR_KEY","events":[{"user_id":"test","event_type":"test_event"}]}'`. A 200 response with `{"code":200,"server_upload_time":...}` confirms events are being received. If you get a 400 or 429, check your API key and rate limits.
What should I do during an Amplitude outage?
During Amplitude outages: (1) Events sent via the SDK are queued in localStorage (browser) or memory (server) — most SDKs automatically retry, so events are usually not lost, (2) For server-side ingestion, add a local queue or use a message queue (Kafka, SQS) as a buffer and retry when Amplitude recovers, (3) For urgent product decisions that depend on data, check if you have a data warehouse (BigQuery, Snowflake) with an Amplitude integration — the raw event data may already be there even if the Amplitude UI is down, (4) Subscribe to status.amplitude.com for recovery notification.