Skip to main content
SourceHut

[Resolved] SourceHut disrupted by LLM crawlers

Degraded Lasted 0m · started · SourceHut's page

Level
confirmed
Worst impact
Degraded
Down Index
18of 100

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-06-06 19:00 UTC and 2026-06-06 19: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 1

  1. resolved

    git.sr.ht is being disrupted by aggressive LLM crawlers . An aggressive botnet is scraping git.sr.ht to obtain data to train large language models. It has been able to circumvent the defenses we ordinarily deploy to mitigate these botnets, and as a consequence git.sr.ht is unstable. We have taken some aggressive measures to ensure some service remains available, but for the time being we have disabled a large number of routes for the web service to keep the load managable, which will cause disruptions to ordinary users. (19:00 UTC — Jun 6) Mitigations have been deployed. The mitigations we deployed are working, for the time being, and we were able to narrow the impact to affect fewer legitimate users. However, some users may still experience issues using git.sr.ht at this time. (20:45 UTC — Jun 6)

    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-8cfe16194c

Is SourceHut still down?

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

How long did it last?

0m, from 2026-06-06 19:00 UTC to 2026-06-06 19: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.