Skip to main content
Bitrise

Git operations over ssh seeing increased latency on github.com

Degraded Lasted 2h 35m · started · Bitrise's page

Level
confirmed
Worst impact
Degraded
Components
GitHub Git Operations
Down Index
21of 100

What to do

  • Check whether you use Bitrise GitHub Git Operations. 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 2h 35m it lasted.

    Anything that failed between 2025-10-24 09:48 UTC and 2025-10-24 12:23 UTC may need a replay.
  • Subscribe to Bitrise's feed to hear about the next one first. RSS feed

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

Updates from Bitrise 2

  1. investigating

    Github is currently experiencing issues, which could also affect Bitrise builds using Github ssh: https://www.githubstatus.com/incidents/n7hf73qtpz2l

    provider

  2. resolved

    This incident has been resolved.

    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-9e1533729e

Is Bitrise still down?

No, this incident was resolved 2025-10-24 12:23 UTC. For Bitrise's live state, see https://down.guide/bitrise.

How long did it last?

2h 35m, from 2025-10-24 09:48 UTC to 2025-10-24 12:23 UTC, by the times Bitrise posted.

What was affected?

Bitrise named GitHub Git Operations.

What caused it?

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

Where does this come from?

Bitrise's official status page, https://status.bitrise.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.