Mixpanel: DNS Resolution Issue
Timeline of updates
- resolved
We changed our DNS provider in response to the Dyn DNS incident yesterday. As a result, some of our DNS responses for api.mixpanel.com became larger than they were before. For clients that disallow extended DNS results over TCP, the consequence was an inability to resolve api.mixpanel.com. We have now updated our DNS so that all responses can be sent in a regular size (UDP) DNS response.
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 2016-10-23 01:04 UTC, resolved after 0 min, 1 update(s).
- Title
- DNS Resolution Issue
- Vendor
- Mixpanel
- Date
- URL
- https://rewindex.com/company/mixpanel/incidents/8xx2zgmz76mq
Mixpanel profileRecent Mixpanel incidentsAll outages on October 23, 2016Mixpanel in October 2016MarkdownJSON