- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 28of 100
What to do
Check whether you use SourceHut in us. 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 2021-01-08 09:03 UTC and 2021-01-08 09:03 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
An issue with our upstream ISP caused an outage . Our ISP decided to ring in the new year by unplugging us for 12 minutes last night. Sorry about that. (09:03 UTC — Jan 8)
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-76521ee59a
Is SourceHut still down?
No, this incident was resolved 2021-01-08 09:03 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2021-01-08 09:03 UTC to 2021-01-08 09:03 UTC, by the times SourceHut posted.
What was affected?
SourceHut named in us.
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.