Segment: Elevated BigQuery rate limit errors
Timeline of updates
- resolved
The fix has been verified as working. BigQuery warehouses that encountered rate limit errors will catch up during their next sync.
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: minor) posted by Segment, started 2019-03-08 16:57 UTC, resolved after 51 min, 1 update(s).
- Title
- Elevated BigQuery rate limit errors
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/c9cxgj542l5m
Segment profileRecent Segment incidentsAll outages on March 8, 2019Segment in March 2019MarkdownJSON