- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 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 2023-04-20 18:10 UTC and 2023-04-20 18:10 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
The services are online and working . We have been monitoring the mitigations we put in place last night and, though we’re still tying off some loose ends, all services should be available for users. (07:00 UTC — Apr 21) A distributed denial of service (DDoS) attack on sr.ht is underway . We have identified the source of the networking issues as a denial of service attack and we are deploying a mitigation. (19:10 UTC — Apr 20) Networking issues caused an unplanned outage . Some networking issues are causing degraded availability for all our services. (18:10 UTC — Apr 20)
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-3d75d4c8a3
Is SourceHut still down?
No, this incident was resolved 2023-04-20 18:10 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2023-04-20 18:10 UTC to 2023-04-20 18:10 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.