- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 40of 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 2021-10-27 08:20 UTC and 2021-10-27 08:20 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
HTTP(s) clone access has been restored : The issue was narrowed down to a stale nginx configuration which directed authorization requests to the wrong port. The configuration has been corrected and normal service is restored. (08:35 UTC — Oct 27) HTTP(s) clone is currently unavailable for hg.sr.ht : A planned deployment ran afoul and has caused some problems with cloning hg.sr.ht repositories via https. An investigation is ongoing. SSH clone is still working correctly. (08:20 UTC — Oct 27)
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-1db32079ca
Is SourceHut still down?
No, this incident was resolved 2021-10-27 08:20 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2021-10-27 08:20 UTC to 2021-10-27 08:20 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.