Segment: Regulations ConfigAPI Endpoint Errors
Timeline of updates
- resolved
Customers sending requests to Segment's ConfigAPI using the Regulations (ie. Deletions) endpoints between 3/18/22 11:00 and 3/2122 14:00 Pacific Time saw sporadic 503 errors. If you received a 503 error on creating a new regulation request, you will be required to resubmit the request.
From Segment’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.segment.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Segment, started 2022-03-18 17:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Regulations ConfigAPI Endpoint Errors
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/xfvr5gmth0sv
Segment profileRecent Segment incidentsAll outages on March 18, 2022Segment in March 2022MarkdownJSON