Amplitude: Unexpected "[Segment]" Prefix in Event Types
Timeline of updates
- resolved
Amplitude has completed a data remediation plan to help impacted customers. The [Segment] prefix has been scrubbed from impacted events as of June 11, 2025. No action is required on your part. If you created an Amplitude event transformation as a short term fix to merge the incorrect event names, it is safe to remove those transformations now.
From Amplitude’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 status.amplitude.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Amplitude, started 2025-06-05 16:01 UTC, resolved after 8 d, 1 update(s).
- Title
- Unexpected "[Segment]" Prefix in Event Types
- Vendor
- Amplitude
- Date
- URL
- https://rewindex.com/company/amplitude/incidents/cnln58d753js
Amplitude profileRecent Amplitude incidentsAll outages on June 5, 2025Amplitude in June 2025MarkdownJSON