Is Mixpanel Down?

No — Mixpanel is up

Reachable from all 8 checked regions

Average response time: 1066ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://www.mixpanelstatus.com

Mixpanel uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1113ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

71-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn

834ms

DNS 0ms TCP 5ms TLS 8ms TTFB 579ms

cdg

1004ms

DNS 0ms TCP 2ms TLS 6ms TTFB 511ms

dfw

564ms

DNS 0ms TCP 1ms TLS 5ms TTFB 302ms

ewr

693ms

DNS 0ms TCP 7ms TLS 13ms TTFB 434ms

fra

1253ms

DNS 0ms TCP 1ms TLS 5ms TTFB 535ms

gru

1618ms

DNS 0ms TCP 3ms TLS 10ms TTFB 830ms

iad

625ms

DNS 0ms TCP 2ms TLS 6ms TTFB 348ms

jnb

1944ms

DNS 0ms TCP 1ms TLS 4ms TTFB 888ms

What Mixpanel does

Mixpanel is a product analytics platform that tracks user events from web and mobile applications and reports on funnels, retention and segmentation. Product teams use it to see how features are actually used. It runs separate data residencies in the United States, the European Union and India, so where your project lives determines which infrastructure an incident affects.

What an outage looks like

Reports and boards fail to load or return incomplete numbers. Event ingestion can fail independently of the interface, so charts stay reachable while the most recent events never appear. Scheduled exports and warehouse syncs do not run. If your site loads the Mixpanel JavaScript library from its CDN, a CDN incident can slow page loads even though tracking itself is not user-facing.

What to do about it

Check www.mixpanelstatus.com, which reports Application Availability and Ingestion API Availability separately for the US, EU and India residencies, so confirm which one your project uses before reading the page. Warehouse Connectors, Data Export and the JavaScript Library CDN are listed as their own components. An incident in one region says nothing about the others.

Is it down for everyone, or just you?

If this page says Mixpanel is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Mixpanel outage FAQ

Which Mixpanel region does my project use?

Mixpanel lists Application and Ingestion availability separately for the United States, the European Union and India, and a project belongs to exactly one of them. This is chosen at project creation and usually driven by data residency requirements. Reading the wrong region on the status page is the easiest mistake to make during an incident, so confirm the residency in your project settings before concluding you are unaffected.

Are events lost while Mixpanel ingestion is down?

Client SDKs queue and retry, so events are typically delayed rather than dropped, but the guarantee is weaker in a browser than in a mobile app where the queue survives a restart. Ingestion API Availability is separate from Application Availability, so ingestion can stall while reports still load. After recovery, compare event volume for the outage window against a comparable period before assuming a real drop in usage.

Does a Mixpanel outage slow down my website?

It can, if you load the tracking library from Mixpanel's CDN and include it in a blocking position. The JavaScript Library CDN is listed as its own component for that reason. Loading the library asynchronously means a CDN incident costs you analytics data rather than page speed. This is worth checking in your own markup rather than assuming, since the default install snippet is not always what ends up deployed.

Will warehouse syncs backfill after an incident?

Warehouse Connectors is a separate component, so syncs can fail while the rest of Mixpanel is healthy. A missed scheduled run does not necessarily re-run on its own, which means a downstream table can silently hold stale data long after the incident is marked resolved. After a connector incident, check the last successful sync timestamp in the destination rather than trusting the status page alone.

How we measure this

We request Mixpanel's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Mixpanel publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Mixpanel goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required