Why are my Mixpanel events not showing up?

If Mixpanel events are not appearing, first check status.mixpanel.com for any data ingestion or processing incidents. If status is operational, common causes include: Mixpanel's standard ingestion delay (events can take 1-2 hours to appear in reports due to deduplication and processing), incorrect project token, SDK version bugs, or network issues on your client side. The Mixpanel Ingestion API is at api.mixpanel.com — check if it's reachable from your environment.

Does Mixpanel lose events during an outage?

Mixpanel SDKs queue events locally (in localStorage for web, in-memory or SQLite for mobile) when the ingestion API is unreachable. Queued events are sent when connectivity restores. However, if a user closes the browser or app before the retry succeeds, those queued events may be permanently lost. Server-side tracking libraries also queue events in memory — a process restart during an outage would lose the queue.

What is the Mixpanel data ingestion delay?

Mixpanel normally processes events within a few minutes, but reports have a display delay. In Mixpanel's standard reports, there is typically a 1-2 hour lag before recent events appear in charts and funnels due to batching and deduplication. This is expected behavior, not an outage. If events are more than 3-4 hours delayed, check status.mixpanel.com for a processing incident.

How do I get alerts when Mixpanel goes down?

Subscribe to status.mixpanel.com email notifications. For proactive monitoring, set up an external check that periodically hits the Mixpanel Ingestion API (api.mixpanel.com/track) with a test event and monitors for non-200 responses. This gives you early warning of ingestion issues before they appear on the status page.

Mixpanel / Product Analytics

Mixpanel Status: How to Check If Mixpanel Is Down Right Now (2026)

Updated June 2026 · 7 min read · API Status Check

Quick Answer

Check Mixpanel status at status.mixpanel.com (official) for real-time data ingestion, processing, and dashboard status.

Staff Pick

📡 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.

Start Free →

Affiliate link — we may earn a commission at no extra cost to you

The Official Mixpanel Status Page

Mixpanel maintains an official status page at status.mixpanel.com. It shows real-time status for each component of the Mixpanel platform:

Data Ingestion: The Mixpanel Ingestion API (api.mixpanel.com/track, /import, /engage) — events sent from SDKs and server-side code hit this endpoint first. An ingestion outage means events are not being received by Mixpanel.

Data Processing: The pipeline that transforms raw events into the queries and aggregations used in Mixpanel reports. Processing outages cause delays in reports and funnels — events may be ingested but not yet visible.

Reports & Dashboards: The Mixpanel UI for Insights, Funnels, Flows, Retention, and Cohort reports. UI outages affect report viewing but not data ingestion — events continue flowing even if dashboards are inaccessible.

Notifications: Mixpanel's notification system for sending reports via email and Slack on a schedule, and for alerting on metric anomalies.

Mixpanel API: The Query API and JQL (JavaScript Query Language) API for programmatic data export and custom analysis. Powers integrations with BI tools and data pipelines.

What Each Mixpanel Status Means

Operational: All Mixpanel systems are working normally. Events are ingested within seconds, processed within 1-2 hours, and reports reflect recent data. Note: even in operational state, Mixpanel reports have a natural 1-2 hour delay due to deduplication processing — this is not an outage.

Degraded Performance: Mixpanel is accessible but experiencing issues such as elevated ingestion latency, longer report processing times, or slow dashboard rendering. Events are being received but processing is delayed. Your charts may show older data than usual.

Partial Outage: A specific Mixpanel component is affected. Common partial outages: Ingestion working but Processing delayed (events received but not yet in reports), or Reports down while Ingestion continues (events safe but dashboards unavailable). Check which component is affected.

Major Outage: Mixpanel is broadly unavailable. Ingestion may fail (events lost at the source), processing is halted, and dashboards are inaccessible. If ingestion is down, your SDK-queued events may be lost if users close their browser or app.

Under Maintenance: Planned maintenance window. Mixpanel typically schedules maintenance during off-peak hours. Check status.mixpanel.com for the expected duration. SDKs will queue events and retry once maintenance completes.

📡

Recommended

Monitor your Mixpanel ingestion pipeline independently

Better Stack lets you set up an external check on Mixpanel's ingestion API and alert you when events stop flowing — before it shows up on the status page. Free tier included.

Try Better Stack Free →

Mixpanel Ingestion: How Events Flow (and Where They Can Break)

Understanding the Mixpanel data pipeline helps you diagnose whether an issue is on your side or Mixpanel's:

Step 1: SDK / Server-Side Send

Your frontend SDK (mixpanel-browser) or server-side library (mixpanel-python, mixpanel-node, etc.) collects events and sends them to api.mixpanel.com/track (or /import for batch). SDKs automatically retry on failure and queue events locally. Server-side libraries typically queue in memory — a process restart loses the queue.

Step 2: Ingestion API Acceptance

Mixpanel's Ingestion API accepts events and returns HTTP 200 with body 1 (success). A 200 response means Mixpanel has received the event — not that it has been processed or will appear in reports immediately. Events are queued internally for processing.

Step 3: Data Processing Pipeline

Ingested events go through Mixpanel's processing pipeline: deduplication (by $insert_id), identity resolution (user stitching via $distinct_id), property transformation, and aggregation into report data. This pipeline introduces the normal 1-2 hour report display delay.

Step 4: Report Availability

Processed events become queryable in Insights, Funnels, Flows, and other Mixpanel reports. A 'partial outage' in Processing means events were received at Step 2 but are stuck in the pipeline — data will appear once processing resumes. A 'partial outage' in Ingestion means events are not reaching Step 2 and may be permanently lost.

5 Ways to Check Mixpanel Status Right Now

Official Mixpanel Status Page

Visit status.mixpanel.com for per-component status. Subscribe to email notifications to receive incident updates.

status.mixpanel.com →

Send a Test Event via cURL

Send a test track event directly to the Mixpanel Ingestion API. A 200 response with body '1' means ingestion is working.

# Test Mixpanel ingestion (replace YOUR_TOKEN)
curl -s "https://api.mixpanel.com/track" \
  -d 'data=eyJldmVudCI6InRlc3QiLCJwcm9wZXJ0aWVzIjp7InRva2VuIjoiWU9VUl9UT0tFTiJ9fQ=='

# Response "1" = ingestion working, "0" or error = issue

Check the Mixpanel Dashboard

Log in to mixpanel.com and navigate to a project. If Insights or Funnels show a loading spinner indefinitely, the Reports component is affected. If data stops at a timestamp, Processing may be delayed.

X/Twitter Search

Search 'Mixpanel down' or 'Mixpanel not tracking' on X. Product and growth teams report Mixpanel issues quickly.

Search X for 'Mixpanel down' →

Mixpanel Support

Contact Mixpanel support at help.mixpanel.com or submit a ticket. For business-critical tracking loss, use the chat support for faster response.

Mixpanel Help Center →

Common Mixpanel Issues During Outages

These are the symptoms and errors you'll see when Mixpanel is experiencing issues:

"Events not showing in Mixpanel reports"Check the time range — Mixpanel has a normal 1-2 hour processing delay. If events from 3+ hours ago are missing, check status.mixpanel.com for a Processing incident. If very recent events are missing, this is expected behavior and not an outage.

"Funnel steps showing 0% conversion"Could be a Processing delay affecting recent events, or a data quality issue (event names changed, identity resolution broken). Check if the funnel shows 0% across all time ranges or just recent periods — a recent-only drop suggests a processing issue.

"Mixpanel SDK returning error / timeout"The Mixpanel Ingestion API is unreachable or returning errors. Events are queuing in the SDK. Check status.mixpanel.com for an Ingestion incident. The mixpanel-browser SDK queues up to 500 events in localStorage by default.

"Reports loading infinitely / blank dashboard"The Mixpanel Reports component is experiencing issues. Your event data is safe — it is the query/display layer that is affected. Wait for status recovery or use the Mixpanel Query API directly as a workaround.

"Data export / JQL queries returning errors"The Mixpanel API component is degraded. Export jobs and programmatic queries will fail or return stale results. Check status.mixpanel.com for an API incident and retry after recovery.

"User profiles not updating"Mixpanel Engage (the People/Profile system) is a separate component from event ingestion. Profile update calls go to api.mixpanel.com/engage. If Engage is degraded, $set, $add, and $union operations queue and may be delayed or lost.

What to Do When Mixpanel Is Down

Immediate Response

Confirm on status.mixpanel.com — is this Ingestion, Processing, or UI?
If Ingestion is down: events are at risk — enable server-side buffering immediately
If Processing is down: events are safe, reports will catch up after recovery
Notify product/growth teams that Mixpanel data may be stale during the incident
Do not make product decisions based on Mixpanel data during a Processing outage
Document the outage window for post-mortem data gap analysis

Long-Term Resilience

Use server-side event tracking — more reliable than client-side during outages
Implement a Customer Data Platform (Segment, RudderStack) to route events to multiple destinations
Store raw events in your own data warehouse as a backup (BigQuery, Snowflake)
Use $insert_id for deduplication so replayed events don't create duplicates
Subscribe to status.mixpanel.com email notifications for incident awareness

Frequently Asked Questions

Where is the official Mixpanel status page?

Mixpanel's official status page is at status.mixpanel.com. It tracks Data Ingestion, Data Processing, Reports & Dashboards, Notifications, and the Mixpanel API separately. Subscribe to email notifications to receive incident updates automatically.

Why are my Mixpanel events delayed by 1-2 hours?

A 1-2 hour delay in Mixpanel reports is normal behavior, not an outage. Mixpanel batches and deduplicates events before they appear in reports. This delay allows Mixpanel to stitch user identities and remove duplicate events (using $insert_id). If delays exceed 3-4 hours or events from yesterday are missing, check status.mixpanel.com for a Processing incident.

Does Mixpanel lose events when it goes down?

It depends on where the outage occurs. If Data Ingestion is down, events sent by SDKs are queued locally (localStorage for web, in-memory for servers). If the user session ends before the retry succeeds, those events are lost. If only Data Processing is down, events are received and stored safely — they will appear in reports once processing resumes.

Can I use Mixpanel with a CDP for redundancy?

Yes — using a Customer Data Platform like Segment or RudderStack as a collection layer lets you send the same events to Mixpanel and a data warehouse simultaneously. If Mixpanel is down, your raw events are stored in the warehouse. You can replay events to Mixpanel later using the Import API after the outage. This is the recommended pattern for production analytics at scale.

How does Mixpanel compare to Amplitude for reliability?

Both Mixpanel and Amplitude are similar in architecture and reliability profile for product analytics. Mixpanel's status page (status.mixpanel.com) and Amplitude's (status.amplitude.com) both provide per-component visibility. For critical analytics tracking, both vendors recommend server-side tracking with retry logic rather than relying solely on client-side SDKs, which are subject to network conditions and ad blockers.

Alert Pro

14-day free trial

Stop 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

Start Free Trial →Compare all plans →

Also recommended:

Better Stack — all-in-one monitoring 1Password — secure your API keys