Mixpanel: Failure to store specific event formats for a subset of projects
Timeline of updates
- resolved
We identified an issue in the latest versions of our web and mobile SDKs that caused the SDKs to send events to our /track API in a format that our servers failed to ingest. The issue had a chance to occur when the SDK's identify function was called with the current Distinct ID as an argument (e.g.
mixpanel.identify(mixpanel.get_distinct_id())), leading to events from that client device session not being properly received by Mixpanel. This issue was most likely to occur with our iOS Swift SDK. The issue was fully resolved with server-side changes on March 29th, 8:15PM PST. No SDK updates are necessary. Customers using the latest SDK versions before March 29th could be missing events sent from client devices that encountered this issue.
From Mixpanel’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.mixpanelstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Mixpanel, started 2023-03-29 07:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Failure to store specific event formats for a subset of projects
- Vendor
- Mixpanel
- Date
- URL
- https://rewindex.com/company/mixpanel/incidents/4b0h00g5hfvs
Mixpanel profileRecent Mixpanel incidentsAll outages on March 29, 2023Mixpanel in March 2023MarkdownJSON