Skip to main content
Travis CI

GitHub sync blocked or lasting long - degraded performance

Degraded Lasted 3h 17m · started · Travis CI's page

Level
confirmed
Worst impact
Degraded
Components
User Sync
Down Index
21of 100

What to do

  • Check whether you use Travis CI User Sync. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 3h 17m it lasted.

    Anything that failed between 2023-11-03 12:29 UTC and 2023-11-03 15:46 UTC may need a replay.
  • Subscribe to Travis CI's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=travis-ci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Travis CI 3

  1. identified

    We received information on issues with data synchronization with GitHub since Nov/1st. We have identified reason and are working on restoring system to normal operation.

    provider

  2. monitoring

    A fix is in place and we're monitoring.

    provider

  3. resolved

    Data synchronization issues with GitHub have been fully resolved and all systems are operational

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5a9455c693

Is Travis CI still down?

No, this incident was resolved 2023-11-03 15:46 UTC. For Travis CI's live state, see https://down.guide/travis-ci.

How long did it last?

3h 17m, from 2023-11-03 12:29 UTC to 2023-11-03 15:46 UTC, by the times Travis CI posted.

What was affected?

Travis CI named User Sync.

What caused it?

Travis CI hasn't published a root cause. If it does, it shows here.

Where does this come from?

Travis CI's official status page, https://www.traviscistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.