Temporary Data Ingestion Delay for US Projects
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 your patience throughout this incident.
The latest update from Mixpanel.
State
Resolved
Started
24 d ago
2026-10-08 16:32 UTC
Lasted
7 h 50 min
until 2026-10-09 00:22 UTC
Worst impact
Notice
Timeline
9 updatesInvestigating
1 h 13%
Identified
1 h 58 min 25%
Monitoring
4 h 52 min 62%
Updates
Times in UTCAs posted by Mixpanel
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 your patience throughout this incident.
Systems have remained stable with no recurrence of the ingestion delay. We’re keeping a close eye on things while we wait for final confirmation from our upstream provider.
We are continuing to monitor for any further issues.
No change since our last update, we continue to observe no active ingestion delay on our end, and all systems remain healthy. We’re continuing to monitor closely.
We are continuing to monitor for any further issues.
Our metrics show ingestion is caught up and no longer experiencing delay. Google has not yet confirmed resolution of the underlying upstream issue on their end, so we’re continuing to monitor closely in case of recurrence.
We've identified the cause of the ingestion delay as an upstream issue with our cloud storage provider, Google Cloud, impacting a subset of US projects. Google has confirmed this as a high-priority issue on their end but hasn't provided an ETA yet. We've deployed mitigations to ensure a smooth recovery once it clears. No events are being lost. This is strictly an ingestion delay, all affected data will continue to be reprocessed once the issue is resolved.
The issue has been identified and a fix is being implemented.
We are currently experiencing delays in our data ingestion pipeline, which is affecting real-time data for projects enrolled in the US projects, resulting in delays for a subset of projects. While no data is being lost, our engineering team is actively investigating the matter and working to restore real-time functionality as quickly as possible. We appreciate your patience during this time. If you have any questions, please contact support.
Mixpanel in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
8
Median duration
6 h 13 min
This incident
1.3× the median
Other Mixpanel incidents
All incidentsMixpanel·Degraded Service for Requests to decide.mixpanel.com
# **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 sent event tracking, profile updates, or feature flag requests to this hostname, usually through a proxy. Events sent to this domain during this window were not received by Mixpanel and this data cannot be restored by Mixpanel. **Traffic sent to** `api.mixpanel.com`**,** `api-js.mixpanel.com,` `api-eu.mixpanel.com`**, and** `api-in.mixpanel.com` **were not affected.** Service on this hostname was unintentionally impacted while we were removing the `/decide` endpoint infrastructure. The hostnames were treated as part of the endpoint due to an incorrect understanding of system dependencies. To prevent this class of issue, we are adding traffic monitoring for the `decide.mixpanel.com` and `api-decide.mixpanel.com` hostn
Mixpanel·Degraded Query API Performance impacting US Projects
# 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 API. During this window, some queries in the region failed or returned errors. **No customer data was lost, and data ingestion was not affected.** All events continued to be collected and stored normally throughout the incident; once query service was restored, all reports reflected complete, accurate data with no customer action required. The cause was identified as a recently deployed internal tool for diagnostic query replay, a capability our engineers use to re-run copies of past queries to debug performance, which unexpectedly wrote large amounts of data to the disks of our query servers, consuming storage capacity the servers need to operate. When those disks filled, the affected servers took themselves ou
Mixpanel·Issues Populating Event Properties in dropdown menus
This incident has been resolved.
Mixpanel·Mixpanel MCP: Get-Report degraded
This incident has been resolved.
Follow Mixpanel
Your coding agent knows when Mixpanel is down, and tells you when a failure is theirs, not yours. You can also get Mixpanel incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mixpanel" and tell me if Mixpanel has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=mixpanel/feed subscribe https://outages.cc/feed.xml?providers=mixpanelFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane