Mixpanel: Timestamp offset on a subset of events
Timeline of updates
- resolved
An issue affecting timestamps for a subset of events was identified on February 14th. The cause of this bug was a software update on our servers last week that caused the timezone offset of projects to not be applied to events at ingestion. This resulted in some events being stored in UTC time in projects. If your project is in UTC then you will be unaffected. Our engineering team deployed a fix in two stages: the first on the afternoon of February 14 and the second on the morning of February 16th. This has caused projects to see an anomaly in event volume around 3PM and 4PM PST on February 14th when the first fix went out causing events moving forward to appear with accurate timestamps. There was no data loss and all the events sent to Mixpanel were tracked in your project.
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 2019-02-15 14:36 UTC, resolved after 6 d, 1 update(s).
- Title
- Timestamp offset on a subset of events
- Vendor
- Mixpanel
- Date
- URL
- https://rewindex.com/company/mixpanel/incidents/6y8x2z6j3b8s
Mixpanel profileRecent Mixpanel incidentsAll outages on February 15, 2019Mixpanel in February 2019MarkdownJSON