rewindex

CompaniesTravis CIIncidents

Travis CI: Heroku API in read-only emergency maintaince

No impact listedStatus: resolvedStarted Resolved (12 min)1 updatewww.traviscistatus.com (opens in new tab)

Timeline of updates

  1. resolved

    Heroku has re-enabled there API and everything is looking good on Travis.

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 2015-08-06 19:07 UTC, resolved after 12 min, 1 update(s).

Title
Heroku API in read-only emergency maintaince
Vendor
Travis CI
Date
URL
https://rewindex.com/company/travis-ci/incidents/vpl1xq2nw1xp

Travis CI profileRecent Travis CI incidentsAll outages on August 6, 2015Travis CI in August 2015MarkdownJSON