CircleCI: 503s on https://circleci.com/.
Timeline of updates
- resolved
There was a bug in our scaling and load-balancing, so one particular server was overloaded with requests and went down. We've solved the problem, sorry for the trouble!
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 2015-01-13 21:48 UTC, resolved after 39 min, 1 update(s).
- Title
- 503s on https://circleci.com/.
- Vendor
- CircleCI
- Date
- URL
- https://rewindex.com/company/circleci/incidents/p299wz7lm0fr
CircleCI profileRecent CircleCI incidentsAll outages on January 13, 2015CircleCI in January 2015MarkdownJSON