Travis CI: Retroactive: Errors fetching logs from the API
Timeline of updates
- resolved
We identified an issue with our API that caused errors to be returned when attempting to fetch logs through the API, and therefore logs weren't being displayed on our website. We've since fixed the issue, and logs are being returned correctly again. This only affected fetching the logs, so no logs were lost during while the issue was live.
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-07-12 11:47 UTC, resolved after 0 min, 1 update(s).
- Title
- Retroactive: Errors fetching logs from the API
- Vendor
- Travis CI
- Date
- URL
- https://rewindex.com/company/travis-ci/incidents/vz8hdxtkt6zh
Travis CI profileRecent Travis CI incidentsAll outages on July 12, 2016Travis CI in July 2016MarkdownJSON