CircleCI: GET Calls To The /api/v2/runner Endpoint Resulted In A 301 Error
Timeline of updates
- resolved
Today from 16:05 UTC to 16:31 UTC we saw an issue where users making a GET call the /api/v2/runner endpoint would see a 301 error. A patch was made to address the issue and we are no longer seeing this behavior.
From CircleCI’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.circleci.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by CircleCI, started 2024-07-31 16:00 UTC, resolved after 0 min, 1 update(s).
- Title
- GET Calls To The /api/v2/runner Endpoint Resulted In A 301 Error
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/hc031g8j0yc6
CircleCI profileRecent CircleCI incidentsAll outages on July 31, 2024CircleCI in July 2024MarkdownJSON