Mixpanel Outage History

Started Oct 01, 2025, 10:02 AM UTC· resolved Oct 01, 2025, 03:18 PM UTC

1. identified Oct 01, 2025, 10:02 AM UTC

   We identified an issue beginning at 12:30 AM PST where /import requests experienced elevated delays. Engineering has applied a fix to scale up the system, and it is recovering, though delays may persist until normal processing is fully restored. We will provide an update once performance has returned to normal.

2. monitoring Oct 01, 2025, 11:55 AM UTC

   The Engineering team has released a fix for the issue, and we are currently monitoring. Imported events should now be processed normally, and all reports are expected to return to their usual state.

3. resolved Oct 01, 2025, 03:18 PM UTC

   The issue has been resolved and all reports are showing imported events as usual. No events were lost during this incident, events were only delayed.

Read the full incident report →

Started Sep 08, 2025, 07:24 PM UTC· resolved Sep 08, 2025, 09:12 PM UTC

1. investigating Sep 08, 2025, 07:24 PM UTC

   We are currently experiencing delays in our data ingestion pipeline, which is affecting real-time data for a subset of projects. While no data is being lost, our engineering team is actively investigating the issue and working to restore real-time functionality as quickly as possible. We appreciate your patience as we work to resolve this matter. If you have any questions, please contact support.

2. monitoring Sep 08, 2025, 07:28 PM UTC

   A fix has been implemented. We are monitoring the results and working through the backlog of traffic

3. monitoring Sep 08, 2025, 09:05 PM UTC

   All new data sent to Mixpanel should be ingested without delay. Some older traffic from the start of the incident is still being processed

4. resolved Sep 08, 2025, 09:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 11, 2025, 09:19 AM UTC· resolved Aug 11, 2025, 01:50 PM UTC

1. investigating Aug 11, 2025, 09:19 AM UTC

   We are currently experiencing issues with loading Mixpanel.com and are working to restore service as quickly as possible. Our team is investigating the issue and will provide updates as soon as we have more information. Thank you for your patience.

2. identified Aug 11, 2025, 09:37 AM UTC

   We're continuing to see degraded query performance. The issues we're seeing are due to a latency with a downstream provider. The provider has been contacted and is investigating. We're continuing to work with our provider to resolve these issues.

3. identified Aug 11, 2025, 10:19 AM UTC

   We have requested a capacity increase with the downstream provider. The latency remains high, but the loading issues occur only intermittently now.

4. monitoring Aug 11, 2025, 10:51 AM UTC

   We're continuing to work together with the downstream provider and are seeing a recovery of the latency. Error rates for loading reports dropped to nearly 0. We are monitoring the performance for now and will update once the issue has been resolved completely.

5. monitoring Aug 11, 2025, 11:41 AM UTC

   Mixpanel.com is up and running again. We continue to monitor the performance and its stability, but for now, we are not experiencing any further latency.

6. resolved Aug 11, 2025, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 06, 2025, 06:55 PM UTC· resolved Aug 07, 2025, 04:13 AM UTC

1. investigating Aug 06, 2025, 06:55 PM UTC

   We are experiencing delays with ID Merge where it is taking more than 24 hours for identity management mappings to reflect their merged state in reports for US Projects. As a result, reports such as Funnels may show a decrease in conversion for the last few days. We truly appreciate your patience and apologize for the inconvenience. If you have any questions, please contact support

2. identified Aug 06, 2025, 08:09 PM UTC

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

3. identified Aug 06, 2025, 09:02 PM UTC

   We are continuing to process the data backlog. At this time, more than 24-hour delays with ID Merge are still expected. Thank you for your patience while we work on resolving this.

4. identified Aug 06, 2025, 10:04 PM UTC

   We continue to process the data backlog. Delays with ID Merge can still be expected during this time. Thank you for your patience while we work on resolving this.

5. identified Aug 06, 2025, 11:11 PM UTC

   We are continuing to process the data backlog of merges.

6. identified Aug 07, 2025, 12:38 AM UTC

   We are continuing to process the data backlog of merges. We have made a lot of progress in processing the data queue. Thank you for your patience while we work on resolving this.

7. identified Aug 07, 2025, 02:11 AM UTC

   We are continuing to process the data backlog of merges.

8. monitoring Aug 07, 2025, 04:03 AM UTC

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

9. resolved Aug 07, 2025, 04:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2025, 07:32 AM UTC· resolved Jul 25, 2025, 12:42 AM UTC

1. identified Jul 24, 2025, 07:32 AM UTC

   We identified a Data Pipeline export delay affecting US-based projects. The underlying issue causing the delay has been fixed and we're increasing resources to catch up with the backlog. We'll post an update on progress as soon as we've seen a clear trend once the scale up is complete. Thanks for your patience.

2. identified Jul 24, 2025, 09:38 AM UTC

   Our engineering team continues to work on scaling up our servers. At this time, we don't have a timeline to catching up with delayed tasks, but we continue to work and will post an update as soon as we have a trend.

3. identified Jul 24, 2025, 11:34 AM UTC

   The team continues to work on the backlog. At this time we don't have a clear ETA to catch up on the delayed tasks. It's estimated to require a few more hours. We will keep the page updated once a very estimate is available.

4. identified Jul 24, 2025, 01:38 PM UTC

   The team continues to work on the backlog. We'll post an update as soon as a reliable ETA is available on the backlog. Thanks for your patience.

5. identified Jul 24, 2025, 03:42 PM UTC

   Our engineering team continues to work on the issue. We'll share an update as soon as we have additional news

6. monitoring Jul 24, 2025, 04:32 PM UTC

   We are making significant progress on the backlog. At this moment, our estimated time for resolution is 1 hour.

7. monitoring Jul 24, 2025, 06:17 PM UTC

   We've made significant progress in addressing our backlog. The majority of tasks have been processed, with a small number still undergoing resolution. While most tasks have been cleared, a few may require additional time.

8. monitoring Jul 24, 2025, 10:06 PM UTC

   We're continuing to work through the remaining backlog, and we've narrowed it down to a small subset of tasks. Our team is actively addressing these remaining items to bring everything to full resolution. We appreciate your patience as we finalize these efforts.

9. resolved Jul 25, 2025, 12:42 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 16, 2025, 11:24 AM UTC· resolved Jul 16, 2025, 12:59 PM UTC

1. investigating Jul 16, 2025, 11:24 AM UTC

   We are currently experiencing issues with loading Mixpanel reports and are working to restore service as quickly as possible. Our team is investigating the issue and will provide updates as soon as we have more information. Thank you for your patience.

2. identified Jul 16, 2025, 11:43 AM UTC

   The issue has been identified and the Engineering team is working on a fix.

3. monitoring Jul 16, 2025, 12:05 PM UTC

   A fix has been implemented and all reports are loading now. Incident is considered resolved and from Support we will keep monitoring the situation.

4. resolved Jul 16, 2025, 12:59 PM UTC

   This incident has been fully resolved.

Read the full incident report →

Started Jul 15, 2025, 08:20 PM UTC· resolved Jul 15, 2025, 08:20 PM UTC

1. resolved Jul 15, 2025, 10:58 PM UTC

   From approximately 1:20-1:25PM Pacific time customers may have experienced elevated error rates when trying to load reports on Mixpanel.com. The issue arose from a misconfigured deploy that was quickly fixed. No other Mixpanel services were affected by this incident.

Read the full incident report →

Started Jun 15, 2025, 07:49 AM UTC· resolved Jun 16, 2025, 04:53 PM UTC

1. investigating Jun 15, 2025, 07:49 AM UTC

   We are currently investigating an issue impacting schematized BigQuery export pipelines, which has caused job delays and failure.

2. identified Jun 15, 2025, 03:14 PM UTC

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

3. monitoring Jun 15, 2025, 04:29 PM UTC

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

4. resolved Jun 16, 2025, 04:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:29 PM UTC· resolved Jun 13, 2025, 02:04 AM UTC

1. investigating Jun 12, 2025, 06:29 PM UTC

   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.

2. identified Jun 12, 2025, 07:33 PM UTC

   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. Potential Action Required 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 the recommended retry behavior, 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 the same $insert_id, time, distinct_id, and event name, 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.

3. monitoring Jun 12, 2025, 08:40 PM UTC

   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.

4. monitoring Jun 12, 2025, 09:30 PM UTC

   Data ingestion in EU and IN servers have caught up and is no longer delayed. Data ingestion in US servers is still catching up.

5. monitoring Jun 12, 2025, 11:50 PM UTC

   The Mixpanel website and Export API have recovered. Data ingestion in US servers is still catching up.

6. monitoring Jun 13, 2025, 12:18 AM UTC

   Data ingestion in US servers has caught up and is no longer delayed. We will continue to monitor the situation.

7. resolved Jun 13, 2025, 02:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 16, 2025, 08:26 PM UTC· resolved May 16, 2025, 08:54 PM UTC

1. investigating May 16, 2025, 08:26 PM UTC

   We're currently experiencing an issue with our blog page. Our team is actively working to resolve the problem and restore full access as soon as possible. We apologize for the inconvenience and appreciate your patience.

2. resolved May 16, 2025, 08:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 15, 2025, 02:55 PM UTC· resolved Apr 15, 2025, 08:36 PM UTC

1. monitoring Apr 15, 2025, 02:55 PM UTC

   From April 15th at 5:38 PM to April 16th at 5:56 AM (PST), Mixpanel experienced degraded performance in one of our ingestion APIs, /import, where some data may not have been ingested correctly. At this moment, we advise our customers to resend any requests that received an empty response along with the '200 OK' code. This disruption only affected projects hosted in our US data center, and more information will be shared shortly. If you have any questions, please don't hesitate to contact our Support team.

2. monitoring Apr 15, 2025, 05:16 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Apr 15, 2025, 08:36 PM UTC

   This incident has been resolved.

4. postmortem Apr 15, 2025, 08:39 PM UTC

   On April 15th, from 12:38 AM UTC to 12:45 PM UTC, our US /import API sent incorrect API responses for up to 10% of traffic. During this period, some requests to the US /import API \(and only this endpoint\) may have received a 200 OK response, even though the events were not successfully ingested. This disruption only affected projects hosted in our US data center. ### Potential Action Required Data sent to the US /import API during this period of time will require resubmission to ensure complete data. * Please ensure those events maintain the same **$insert\_id, time, distinct\_id and event name** so that Mixpanel properly deduplicates any existing data. If you exclusively use Warehouse Connectors and/or the /track API to send data to Mixpanel, no action is required. 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.

Read the full incident report →

Started Mar 20, 2025, 09:13 PM UTC· resolved Mar 20, 2025, 09:49 PM UTC

1. identified Mar 20, 2025, 09:13 PM UTC

   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.

2. resolved Mar 20, 2025, 09:49 PM UTC

   This incident has been resolved.

Read the full incident report →