We started checking Mixpanel on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Mixpanel reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Mixpanel's own status page declared. Below it, any public chatter we saw about Mixpanel and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Mixpanel's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Mixpanel in the last 24 hours, which is not evidence that nothing is wrong.
Mixpanel's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Mixpanel's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Mixpanel next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
588
US-West
100.00%
454
Europe
100.00%
412
Asia-Pacific
100.00%
250
Their declared record
Mixpanel's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Duplicate charges on a subset of customer accountsAll systems operational
Nov 5, 2026, 5:00 AM UTC to Nov 5, 2026, 5:00 AM UTC (0 min)resolved
their latest update (Nov 5, 2026, 5:00 AM UTC): A technical issue with one of our payment systems caused charges to automatically rerun on a subset of customer accounts, so some customers were charged more than once for the same invoice.
Invoice amounts were correct. Only the payment charges were in error. All amounts charged…
Degraded Service for Requests to decide.mixpanel.comAll systems operational
Oct 21, 2026, 6:00 PM UTC to Oct 22, 2026, 1:34 AM UTC (7h 33m)postmortem published
their latest update (Oct 24, 2026, 1:58 AM UTC): # **Mixpanel RCA: Requests to** [**decide.mixpanel.com**](http://decide.mixpanel.com) **Failed, October 15–21, 2026**
### **Summary**
From Oct 15, 2026 to Oct 21, 2026, requests sent to `decide.mixpanel.com` and `api-decide.mixpanel.com` failed.
This affected customers who sen…
Temporary Data Ingestion Delay for US ProjectsAll systems operational
Oct 8, 2026, 4:32 PM UTC to Oct 9, 2026, 12:22 AM UTC (7h 50m)resolved
their latest update (Oct 9, 2026, 12:22 AM UTC): This incident has been resolved. The upstream issue with our cloud storage provider has been fixed, and our ingestion pipeline has been operating normally with no active delays. No events were lost throughout this incident, all affected data was fully reprocessed.
Thank you for …
Degraded Query API Performance impacting US ProjectsPartial outage
Aug 26, 2026, 9:39 PM UTC to Aug 26, 2026, 10:45 PM UTC (1h 7m)postmortem published
their latest update (Sep 8, 2026, 6:25 PM UTC): # Mixpanel RCA: Temporary Query Service Disruption for US Projects August 26, 2026
# Summary
Between approximately **2:02 PM and 3:19 PM PT on August 26, 2026**, projects in the US region experienced failures loading reports and running queries through the Mixpanel UI and Query…
Issues Populating Event Properties in dropdown menusPartial outage
Aug 19, 2026, 11:20 PM UTC to Aug 20, 2026, 3:05 AM UTC (3h 45m)resolved
their latest update (Aug 20, 2026, 3:05 AM UTC): This incident has been resolved.
Mixpanel MCP: Get-Report degradedMinor incident
Aug 6, 2026, 7:19 AM UTC to Aug 6, 2026, 1:32 PM UTC (6h 13m)resolved
their latest update (Aug 6, 2026, 1:32 PM UTC): This incident has been resolved.
Issues serving responses by the Mixpanel agentAll systems operational
Jul 22, 2026, 8:03 AM UTC to Jul 22, 2026, 2:47 PM UTC (6h 44m)resolved
their latest update (Jul 22, 2026, 2:47 PM UTC): This incident has been resolved.
Temporary Data Ingestion Delay for US ProjectsMinor incident
Jul 11, 2026, 7:53 AM UTC to Jul 11, 2026, 3:54 PM UTC (8h 1m)postmortem published
their latest update (Jul 16, 2026, 11:47 PM UTC): # Summary
Between approximately **11:35 PM PT on July 10 and 7:19 AM PT on July 11, 2026**, data ingestion for Mixpanel projects in the US region ran behind by up to ~2 hours. During this window, reports and dashboards temporarily showed incomplete data — recent time ranges coul…
Query API Degraded PerformanceMinor incident
Jun 29, 2026, 7:47 PM UTC to Jun 30, 2026, 3:30 AM UTC (7h 43m)resolved
their latest update (Jun 30, 2026, 3:30 AM UTC): This incident has been resolved.
Issue with Inviting and Deleting UsersAll systems operational
Jun 3, 2026, 8:05 PM UTC to Jun 3, 2026, 9:27 PM UTC (1h 22m)resolved
their latest update (Jun 3, 2026, 9:27 PM UTC): This incident has been resolved.
Showing the 10 most recent of 51 incidents Mixpanel has declared in the history we hold.
These entries are Mixpanel's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Mixpanel's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.