Is Mixpanel Down Right Now?
Events not showing up, funnels stale, reports timing out — product analytics gaps are invisible until someone asks why conversion dropped. This guide separates Mixpanel platform outages from SDK and ingestion configuration issues.
📡 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 Mixpanel Status Now
Mixpanel's official status page shows health for Event Ingestion, Query API, Reports UI, and Data Pipelines:
Mixpanel Service Components
Mixpanel separates ingestion from query processing. An ingestion incident means data is delayed but not necessarily lost — Mixpanel buffers and replays. A query incident means reports are stale but your data is safe.
HTTP endpoints receiving track/import events
Report computation engine for funnels, retention, flows
Web interface for building and viewing reports
Export pipelines to BigQuery, Snowflake, Redshift
User identity merge and alias computation
Dynamic and static cohort computation
Event and property catalog management
Public REST API for data export and management
Know when Mixpanel ingestion drops — before your product meeting
Mixpanel ingestion gaps are invisible until a PM asks why conversion looks different this week. Better Stack monitors Mixpanel from multiple regions and alerts your Slack the moment ingestion degrades — so you have context, not surprises.
Try Better Stack Free →Diagnostic Playbook
Work through these steps to isolate whether the problem is Mixpanel's platform, your SDK, or an ad blocker.
Check status.mixpanel.com
Look for incidents affecting Event Ingestion or the Query API. Subscribe to status updates to avoid checking manually.
→ Mixpanel Status PageTest ingestion via HTTP API
Send a test event directly: `curl -s "https://api.mixpanel.com/track" -d 'data=eyJldmVudCI6InRlc3QiLCJwcm9wZXJ0aWVzIjp7InRva2VuIjoiWU9VUl9UT0tFTiIsImRpc3RpbmN0X2lkIjoidGVzdCJ9fQ=='`. A 1 response confirms the API is accepting events.
Check the SDK initialization
Verify your project token is correct. In browser console, run `mixpanel.get_property("$device_id")` — if it returns a value, the SDK is initialized. If undefined, the SDK didn't initialize.
Check for ad blocker interference
Open browser Network tab and filter for "mixpanel" — blocked requests show as ERR_BLOCKED_BY_CLIENT. Switch to server-side tracking via Mixpanel's Node.js, Python, or Go SDK to bypass blockers.
Verify event schema in Lexicon
Go to Mixpanel → Lexicon → Events. Check if your event exists and has recent data. A missing event here means ingestion failed or the event name changed.
Common Mixpanel Failure Modes
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Mixpanel goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Mixpanel + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Frequently Asked Questions
Is Mixpanel down right now?
Check the official Mixpanel status page at status.mixpanel.com. It shows health for Event Ingestion, the Query API, Reports UI, and Data Pipelines. If the status page is green but your data looks wrong, the issue is likely ingestion lag (events can take up to 60 seconds to appear), an SDK misconfiguration, or a Mixpanel identity resolution issue — not a platform-wide outage.
Why are my Mixpanel events not showing up?
Events missing from Mixpanel reports have several causes: (1) Ingestion lag — Mixpanel processes events within 60 seconds for standard ingestion; wait and refresh. (2) Wrong project token — verify your project token in Mixpanel Settings → Project Settings → Project Token. (3) SDK initialization issue — confirm mixpanel.init() or Mixpanel.initialize() is called before track() calls. (4) Ad blocker interference — client-side ad blockers block api.mixpanel.com; use server-side tracking as a fallback. (5) Identity mismatch — if you use distinct_id, verify consistent user identification across sessions. Check the Mixpanel ingestion API directly with a curl test to isolate the issue.
Why are Mixpanel reports loading slowly or timing out?
Mixpanel query timeouts occur when: (1) Mixpanel Query API is degraded — check status.mixpanel.com for query performance incidents, (2) Your query spans too much data — add date range filters; Mixpanel queues large queries and may timeout on free/growth plans, (3) Report has too many breakdowns — reduce the number of event properties in group-by clauses, (4) Funnel/retention query complexity — complex funnels with many steps and large user bases take minutes to compute; Mixpanel caches results but cache misses trigger full recompute. Use Mixpanel Lexicon to check event volume and optimize high-cardinality properties.
How do I test if Mixpanel ingestion is working?
Test ingestion directly via the Mixpanel HTTP API: `curl https://api.mixpanel.com/track -d 'data=BASE64_ENCODED_EVENT'`. For server-side, use: `curl -s https://api.mixpanel.com/import -u PROJECT_TOKEN: -H "Content-Type: application/json" -d '[{"event":"test","properties":{"token":"PROJECT_TOKEN","distinct_id":"test-user","time":UNIX_TIMESTAMP}}]'`. A 200 response with `{"code":1,"status":"ok"}` confirms ingestion is working. Then check your Mixpanel project in 60 seconds for the test event.
How do I get notified when Mixpanel is down?
Set up multiple alert channels: (1) Subscribe to Mixpanel status page emails at status.mixpanel.com → "Subscribe to Updates", (2) Use Better Stack to monitor your Mixpanel ingestion endpoint from multiple regions — get an alert before your product team notices gaps in their funnels, (3) Create a synthetic ingestion test: a server-side cron job that sends a test event every 5 minutes and verifies receipt via the Mixpanel Query API. A gap in the synthetic event stream means ingestion is down.