Mixpanel: Track API Endpoint Partially Unavailable
Timeline of updates
- resolved
On Feb 20th, from approximately 4:00 AM PST to 6:30 AM PST, Mixpanel experienced degraded performance on one of our Ingestion APIs, appearing as an increase in 504 errors to our /track endpoint. During this period, Mixpanel was unable to accept certain event data sent through the /track endpoints. Event data sent via our /import endpoint, user profile data (via /engage) and group profile data (via /groups) were unaffected. Following this discovery, a fix was deployed and the /track endpoint resumed normal functionality. This disruption primarily affected projects hosted in our US data center. Projects hosted in EU and India through our Data Residency Programs were unaffected.
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: minor) posted by Mixpanel, started 2025-02-20 12:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Track API Endpoint Partially Unavailable
- Vendor
- Mixpanel
- Date
- URL
- https://rewindex.com/company/mixpanel/incidents/3xl440zvc4zd
Mixpanel profileRecent Mixpanel incidentsAll outages on February 20, 2025Mixpanel in February 2025MarkdownJSON