- 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 2024-10-30 11:30 UTC and 2024-10-30 11: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
Upstream network issues appear resolved . We still know little of the cause but we know it broadly affected numerous providers in our service area. (14:00 UTC — Oct 30) Upstream network issues are causing intermittent availability problems for SourceHut . An issue with our upstream network provider has affected user access to SourceHut. We do not have any further details or an ETA on a solution at this time. We expect the network to be intermittent until the upstream issue is resolved. (11:30 UTC — Oct 30)
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-d20dc8dedf
Is SourceHut still down?
No, this incident was resolved 2024-10-30 11:30 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2024-10-30 11:30 UTC to 2024-10-30 11: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.