Travis CI: Missed private build requests, Tuesday 4 October 2016
Timeline of updates
- resolved
Starting at 06:35 UTC on Tuesday, 4 October 2016, we were unable to receive build requests on travis-ci.com for approximately 50 minutes. That morning, GitHub experienced a service outage. Once the issue at GitHub was rectified, our system was flooded with build requests at a much greater rate than usual. This caused our Redis instances to hit their maximum allocated memory usage. Our system recovered quickly, but sadly, around 4000 build requests were irretrievably dropped. We are sorry for the difficulties this will have caused. We are already taking steps to avoid this in the future, including splitting our Redis usage across a greater number of dedicated instances and storing GitHub API events redundantly, in order to replay them in the event of an outage.
From Travis CI’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 www.traviscistatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Travis CI, started 2016-10-05 16:50 UTC, resolved after 0 min, 1 update(s).
- Title
- Missed private build requests, Tuesday 4 October 2016
- Vendor
- Travis CI
- Date
- URL
- https://rewindex.com/company/travis-ci/incidents/2wp961zdsjz8
Travis CI profileRecent Travis CI incidentsAll outages on October 5, 2016Travis CI in October 2016MarkdownJSON