- 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 2025-12-24 13:00 UTC and 2025-12-24 13: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
- resolved
git.sr.ht is experiencing issues due to a crawler botnet. A crawler botnet is aggressively scraping git.sr.ht for content to train large language models and is able to circumvent our usual defenses deployed to prevent them from doing so, and as a result is causing severe performance degradations for the git.sr.ht web frontend. Our sysadmins are investigating the issue now. (13:00 UTC — Dec 24)
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-06c5d9ab1e
Is SourceHut still down?
No, this incident was resolved 2025-12-24 13:00 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2025-12-24 13:00 UTC to 2025-12-24 13: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.