New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Monitor Features overview Vendor status Uptime & synthetic checks Certificate lifecycle Operate Incident management Live demo
By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard

Mixpanel Outage History

Uptime record, past incidents, and downtime history for Mixpanel.

Checking current status...
80.2% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Feb 25May 25

Monthly Uptime

Month Uptime Days Tracked Days with Issues
May 2026 76% 25 6
April 2026 80% 30 6
March 2026 87.1% 31 4
February 2026 60% 5 2

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

May 2026
Board Access Issues

Started: May 19, 7:03 PM

monitoring
A fix has been implemented and we are monitoring the results.
May 19, 8:23 PM
identified
The issues has been identified and a fix is being implemented. As a workaround boards can be explicitly shared with users who are having issues viewing them currently.
May 19, 7:10 PM
investigating
A subset of users are currently facing issues accessing boards that they previously had access to view. Our Engineering team is actively investigating and will update shortly.
May 19, 7:03 PM
Query API degraded performance
minor

Started: May 14, 11:17 PM

monitoring
A fix has been implemented and we are monitoring the results.
May 16, 1:52 AM
identified
Recovery is continuing to progress. Our current estimate for full recovery is approximately 1-2 hours. Some customers may still see incomplete data in reports until recovery is complete. We will continue to provide updates.
May 16, 12:17 AM
identified
Query latency has returned to normal levels and has been resolved. Recovery is continuing to progress, and our current estimate for full recovery is approximately 4–5 hours. Some customers may still see incomplete data in reports until recovery is complete. We will continue to provide updates.
May 15, 10:14 PM
identified
Query latency has returned to normal levels. We are continuing to monitor.
May 15, 9:23 PM
identified
We are investigating an increase in query latency that appears to be unrelated to the ongoing recovery. You may experience slower-loading reports. Our team is actively looking into the cause and we will provide an update shortly. Recovery is continuing to progress. Our current estimate for full recovery is approximately 3–4 hours. Some customers may still see incomplete data in reports until recovery is complete. We will continue to provide updates.
May 15, 7:56 PM
identified
Recovery is continuing to progress and query latency has returned to normal levels. Our current estimate for full recovery is approximately 3–4 hours. Some customers may still see incomplete data in reports until recovery is complete. We will continue to provide updates.
May 15, 6:47 PM
identified
We are continuing to work on resolving this issue. Our current estimate for full recovery is approximately 3–5 hours. Some customers may still see incomplete data in reports until recovery is complete. We will continue to provide updates.
May 15, 4:37 PM
identified
Recovery is progressing well. Query success rates remain at normal levels, and missing data has now been restored for a portion of affected projects. We're continuing the recovery process for the remaining affected projects and currently estimate full recovery within approximately 3–5 hours. Some customers may still see incomplete data in query results until this work is complete.
May 15, 2:31 PM
identified
We've continued to make progress on the issue affecting some US projects. Query success rates have returned to normal levels, and the related processing delays have also recovered. A subset of affected projects may still see incomplete data in query results while our recovery process runs. We're actively working on this and will share another update in 2 hours. Impact remains limited to our US region. We do not currently believe any data has been permanently lost.
May 15, 12:28 PM
identified
We are continuing to work on a fix for this issue.
May 15, 10:19 AM
identified
We are continuing to work on a fix for this issue.
May 15, 8:18 AM
identified
We are continuing to work on a fix for this issue.
May 15, 3:49 AM
identified
We are continuing to work on a fix for this issue.
May 15, 2:49 AM
identified
We are continuing to work on a fix for this issue.
May 15, 1:49 AM
identified
We are continuing to work on a fix for this issue.
May 15, 12:49 AM
identified
We are continuing to work on a fix for this issue.
May 15, 12:18 AM
identified
The issue has been identified and a fix is being implemented.
May 14, 11:48 PM
investigating
We are experiencing degraded performance with our Query API, including increased latency. You may see slow-loading reports, incomplete query results, query errors, or data discrepancies. We appreciate your patience while our engineers work to restore normal functionality. We will post progress updates on our status page. If you have any questions, please contact support.
May 14, 11:17 PM
Data Volume Monitoring degraded performance

Started: May 13, 4:34 PM

identified
We are continuing to work on a fix for this issue.
May 13, 9:40 PM
identified
Data Volume Monitoring is again experiencing degraded performance due to a recurring upstream provider disruption. We're mitigating now.
May 13, 4:34 PM
Data Volume Monitoring degraded performance

Started: May 12, 5:17 PM

monitoring
A fix has been implemented, and we are monitoring the result.
May 12, 8:24 PM
identified
An upstream service provider outage is causing this issue. We are deploying a fix to mitigate the disruption.
May 12, 5:46 PM
investigating
We are currently investigating an issue that leads to degraded performance of Data Volume Monitoring in a subset of US-based projects. We truly appreciate your patience and apologize for the inconvenience. If you have any questions, please contact support (https://mixpanel.com/get-support).
May 12, 5:45 PM
Snowflake pipeline exports degraded

Started: May 6, 12:00 AM

identified
We have identified the issue affecting Snowflake pipeline exports for a subset of projects, and our engineering team is working on a resolution.
May 6, 9:32 AM
investigating
A subset of projects are experiencing issues exporting data to the Snowflake warehouse via Mixpanel pipelines. We are currently investigating this issue.
May 6, 12:00 AM
April 2026
Credit Card Processing Interruption

Started: Apr 9, 8:03 PM

monitoring
A fix has been deployed, and all impacted accounts have had their billing re-run. If you continue to receive errors, please ensure the card on file is up to date. If you are still experiencing issues, please submit a support ticket.
Apr 9, 9:00 PM
identified
We are currently experiencing an interruption with our credit card processing. Our engineers have identified the issue and are working on a fix.
Apr 9, 8:03 PM
March 2026
Degraded Query API Performance impacting EU Projects
minor

Started: Mar 16, 4:50 PM

monitoring
A fix has been implemented and we are monitoring the results.
Mar 16, 7:29 PM
identified
Mixpanel is experiencing increased query latency for projects with EU residency, which may result in HTTP 500 responses when querying or saving reports. Projects with US and IN residency remain unaffected. Our engineering team is working on a resolution.
Mar 16, 4:50 PM
View live status for Mixpanel Browse all services