rewindex

CompaniesTravis CIIncidents

Travis CI: Delays with GitHub syncs on travis-ci.com

MinorStatus: resolvedStarted Resolved (1.8 h)1 updatewww.traviscistatus.com (opens in new tab)

Timeline of updates

  1. resolved

    GitHub syncs are now running normally. We had to clear out one of the queues to prevent a component from running out of memory, which means that some syncs that had been scheduled got cancelled. If you've added some new repositories in the past day or two that haven't showed up on Travis CI yet, you can click the "Sync account" button on https://travis-ci.com/profile (opens in new tab) to schedule a new sync

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: minor) posted by Travis CI, started 2017-02-07 09:53 UTC, resolved after 1.8 h, 1 update(s).

Title
Delays with GitHub syncs on travis-ci.com
Vendor
Travis CI
Date
URL
https://rewindex.com/company/travis-ci/incidents/1tmnmxqx19f3

Travis CI profileRecent Travis CI incidentsAll outages on February 7, 2017Travis CI in February 2017MarkdownJSON