Minor impactResolvedAnalytics

Mixpanel incident: Query API degraded performance

Mixpanel reported this minor-impact incident on its official status page on May 14, 2026, 23:17 UTC. It was resolved after 1d 3h.

Right now Mixpanel is operational. Live Mixpanel status →

🔔 Get alerted when Mixpanel has issuesFree · email alerts · no credit card
May 14, 2026, 23:17 UTC
started
May 16, 2026, 02:50 UTC
resolved
1d 3h
duration
Minor
impact

Affected components

  • Application Availability (US)
  1. postmortemMay 21, 2026, 21:43 UTC

    # Mixpanel RCA: Transient Data Access Issue, May 14, 2026 ## Summary On Thursday, May 14, 2026 at approximately 2:30 PM PT, a routine but infrequent cleanup operation in Mixpanel's storage system mistakenly removed a portion of production data files in addition to the unused files it was intended to remove. Some customers experienced query errors during the hours that followed. We detected the issue within minutes, deployed mitigations the same evening that returned query success rates and latency to normal, and restored the affected files from backup by 5:15 PM PT on Friday, May 15. Mixpanel's ingestion pipeline was not affected and no event data was lost in transit. ## What happened This incident was triggered by a storage cleanup procedure that runs periodically to remove files no longer referenced by Mixpanel's metadata. The procedure was more involved than usual: it followed a recent enhancement to our file storage strategy that left a set of unused files behind in our storage

  2. resolvedMay 16, 2026, 02:50 UTC

    This incident has been resolved.

  3. monitoringMay 16, 2026, 01:52 UTC

    A fix has been implemented and we are monitoring the results.

  4. identifiedMay 16, 2026, 00:17 UTC

    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.

  5. identifiedMay 15, 2026, 22:14 UTC

    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.

  6. identifiedMay 15, 2026, 21:23 UTC

    Query latency has returned to normal levels. We are continuing to monitor.

  7. identifiedMay 15, 2026, 19:56 UTC

    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.

  8. identifiedMay 15, 2026, 18:47 UTC

    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.

  9. identifiedMay 15, 2026, 16:37 UTC

    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.

  10. identifiedMay 15, 2026, 14:31 UTC

    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.

  11. identifiedMay 15, 2026, 12:28 UTC

    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.

  12. identifiedMay 15, 2026, 10:19 UTC

    We are continuing to work on a fix for this issue.

  13. identifiedMay 15, 2026, 08:18 UTC

    We are continuing to work on a fix for this issue.

  14. identifiedMay 15, 2026, 03:49 UTC

    We are continuing to work on a fix for this issue.

  15. identifiedMay 15, 2026, 02:49 UTC

    We are continuing to work on a fix for this issue.

  16. identifiedMay 15, 2026, 01:49 UTC

    We are continuing to work on a fix for this issue.

  17. identifiedMay 15, 2026, 00:49 UTC

    We are continuing to work on a fix for this issue.

  18. identifiedMay 15, 2026, 00:18 UTC

    We are continuing to work on a fix for this issue.

  19. identifiedMay 14, 2026, 23:48 UTC

    The issue has been identified and a fix is being implemented.

  20. investigatingMay 14, 2026, 23:17 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Mixpanel's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Mixpanel have incidents?

Mixpanel reported 4 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 4h 59m. See Mixpanel's uptime and incident history

Mixpanel incident on May 14, 2026: Query API degraded performance · APIStatus.watch