Companies / Mixpanel / incidents
Mixpanel: Mixpanel.com and APIs experiencing elevated errors
Mixpanel reported a critical website outage and ingestion/export errors caused by a Google Cloud Platform outage, affecting EU, IN and US services. It started at 2025-06-12 18:29 UTC and was resolved at 2025-06-13 02:04 UTC, lasting 7 h 34 min. Data sent to ingestion APIs that returned errors was not stored and should be re-sent.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Application Availability - Application Availability (US)Application Availability (US)Data Ingestion - Ingestion API Availability (EU)Ingestion API Availability (EU)Data Ingestion - Ingestion API Availability (US)Ingestion API Availability (US)Data Ingestion - Ingestion API Availability (IN)Ingestion API Availability (IN)Application Availability - Application Availability (EU)Application Availability (EU)Data ExportData Ingestion - Warehouse ConnectorsWarehouse ConnectorsApplication Availability - Application Availability (IN)Application Availability (IN)
Timeline of updates
- investigating
Mixpanel is experiencing a website outage due to an issue with Google Cloud Platform. Data ingestion and export are affected as well. We are working to restore service as quickly as possible.
- identified
Due to the Google Cloud Platform outage, Mixpanel's Ingestion API endpoints, including event data (via /track and /import), user profile data (via /engage), and group profile data (via /groups) are experiencing elevated error rates. Data sent to these APIs that resulted in an error will not be stored on our end and should be re-sent. <strong>Potential Action Required</strong> If you are using one of our client-side SDKs which has built-in retry logic OR if you are using a server-side SDK and have already implemented <a href="https://developer.mixpanel.com/reference/import-events?#rate-limits" target="_blank">the recommended retry behavior</a>, your requests to our ingestion APIs will likely be ingested once the services are restored and no additional action is necessary. If you are using a server-side SDK and have not implemented the recommended retry behavior, you will need to resend data for the affected period. The data you are resending may include events already seen in Mixpanel, so please ensure those events maintain <strong>the same $insert_id, time, distinct_id, and event name</strong>, so that Mixpanel properly deduplicates the data. If you have not already implemented automatic retry behavior for your ingestion pipeline we would highly recommend doing so. We are committed to delivering accurate, timely analysis to support your critical decision-making, and we prioritize fast, high-quality customer support. If you have any questions or concerns, please feel free to reach out.
- monitoring
Google has reported that their infrastructure is almost fully recovered. Mixpanel's EU and IN servers are fully recovered, while the US servers are still recovering. The website is back up, and error rates on the Ingestion API endpoints are decreasing. We are starting to receive a large amount of data as services recovers, so ingestion will be delayed as it processes through our system. We really appreciate your patience as we work to restore everything back to normal. If you have any questions or concerns, please feel free to reach out.
- monitoring
Data ingestion in EU and IN servers have caught up and is no longer delayed. Data ingestion in US servers is still catching up.
- monitoring
The Mixpanel website and Export API have recovered. Data ingestion in US servers is still catching up.
- monitoring
Data ingestion in US servers has caught up and is no longer delayed. We will continue to monitor the situation.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Critical incident: Mixpanel.com and APIs experiencing elevated errors 2025-06-12 18:29 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Mixpanel profile · Recent Mixpanel incidents · Markdown · JSON