- 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-08-14 08:00 UTC and 2024-08-14 08: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
Some users are having problems with chat.sr.ht . There are some known issues with chat.sr.ht which are preventing a small number of users from accessing the service. The problem is known and being investigated, but it is complex and difficult to fully understand and address. We request your patience as it may require several days to identify a complete solution. (08:00 UTC — Aug 14)
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-20987799d2
Is SourceHut still down?
No, this incident was resolved 2024-08-14 08:00 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2024-08-14 08:00 UTC to 2024-08-14 08: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.