- 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 2024-12-04 12:30 UTC and 2024-12-04 12:30 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
Mitigations complete . We have finished mitigating the attack and have removed user-impacting mitigations. (17:00 UTC — Dec 4) Attack partially mitigated . We have partially mitigated the attack to restore service to git.sr.ht, but many features of the web UI are currently disabled to reduce load. (12:53 UTC — Dec 4) A distributed denial of service (DDoS) attack on git.sr.ht is underway : A denial of service attack against git.sr.ht is currently underway. We are working on deploying a mitigation. (12:42 UTC — Dec 4)
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-86ff61a043
Is SourceHut still down?
No, this incident was resolved 2024-12-04 12:30 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2024-12-04 12:30 UTC to 2024-12-04 12:30 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.