Skip to main content
SourceHut

git.sr.ht under high load

Degraded Lasted 0m · started · SourceHut's page

Level
confirmed
Worst impact
Degraded
Down Index
18of 100

Summary

SourceHut says git.sr.ht is under very high load, causing intermittent service disruptions. The provider attributes this to a combination of external factors, says it is working on mitigations, and lists the incident as investigating.

Written by anthropic/claude-haiku-5.5 from SourceHut's own updates.

What to do

  • Check whether your product depends on SourceHut. 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 0m it lasted.

    Anything that failed between 2026-11-05 15:00 UTC and 2026-11-05 15:00 UTC may need a replay.
  • Subscribe to SourceHut's feed to hear about the next one first. RSS feed

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

Updates from SourceHut 2

  1. update

    Excessive load on git.sr.ht causes intermittent outages : git.sr.ht is currently under very high load, to the point of occasional service disruptions. It seems to be caused by cooccurrence of a variety of external factors. We are working on mitigations.

    provider

  2. resolved

    Excessive load on git.sr.ht causes intermittent outages : git.sr.ht is currently under very high load, to the point of occasional service disruptions. It seems to be caused by cooccurrence of a variety of external factors. We are working on mitigations.

    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-9971a5a685

Is SourceHut still down?

No, this incident was resolved 2026-11-05 15:00 UTC. For SourceHut's live state, see https://down.guide/sourcehut.

How long did it last?

0m, from 2026-11-05 15:00 UTC to 2026-11-05 15:00 UTC, by the times SourceHut posted.

What caused it?

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

Where does this come from?

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