All status pages

Mixpanel statusLiveFetched seconds agoSource: mixpanelstatus.com

Is Mixpanel down?

Live status check · All systems operational

NO

Live status pulled from mixpanelstatus.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.

About Mixpanel status

Mixpanel is one of the longest-running product analytics platforms, used to track events, funnels, retention, and AB tests. Incidents usually scope to a single surface: event ingestion, the query engine behind reports and funnels, or the dashboard itself.

Components and surfaces that can break

  • Surface 01

    Event ingestion (api.mixpanel.com and api-eu.mixpanel.com).

  • Surface 02

    Query engine for reports, funnels, and cohorts.

  • Surface 03

    Dashboard and integrations (Slack alerts, data warehouse export).

Recent Mixpanel incidents

Mixpanel maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.

What to do if Mixpanel is actually down

  1. SDKs queue events client-side during brief outages

    Mixpanel's web and mobile SDKs buffer events locally when the ingestion API is unreachable, then flush on the next successful request. For short incidents your events arrive late but aren't lost, so don't rush to build a fallback pipeline.

  2. Check whether the incident is US or EU

    Mixpanel runs separate US (api.mixpanel.com) and EU (api-eu.mixpanel.com) ingestion clusters with independent status. Confirm your project's data residency before assuming you're affected — the incident on the status page may not be your region.

  3. Warehouse export pipelines run independently

    Mixpanel to Snowflake or BigQuery export pipelines run on their own schedule and tend to catch up automatically once ingestion recovers. If your dashboards are powered by the warehouse copy, they may stay accurate even while Mixpanel's own reports are degraded.

Keep firing through the incident

Schedule your own Mixpanel health check with Crontap

Weekly funnel-conversion rollup, monthly cohort retention export, daily AB test stats digest. Crontap fires the endpoint that runs your JQL query against Mixpanel and posts the result to Slack or a warehouse, with retries on transient API errors so the digest still lands when Mixpanel has a blip.

External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.

Mixpanel status: FAQ

Where can I see the official Mixpanel status?
www.mixpanelstatus.com publishes component status for ingestion, the query engine, and the dashboard, with separate signals for US and EU. The history page tracks past incidents with timestamps and post-mortems.
Can I verify Mixpanel is receiving my events on a schedule?
Yes. Set up a Crontap heartbeat that hits a small endpoint on your app, fires a known test event into Mixpanel (e.g. 'crontap_heartbeat'), then queries Mixpanel a minute later to assert that event landed. If the assertion fails, Crontap emails you — independent of Mixpanel's own status page.
Will queued events be lost during a Mixpanel outage?
Usually no. The official Mixpanel SDKs buffer events in local storage (web) or on disk (mobile) when the ingestion API is unavailable, and flush on the next successful request. Server-side senders are different: if you POST directly to api.mixpanel.com from your backend, you need to handle 5xx retries yourself, otherwise those events do get dropped.