- 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 2021-01-21 19:00 UTC and 2021-01-21 19: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
An issue with mail delivery caused some emails to be dropped . Upgrades to our mail server caused authentication to unexpectedly and silently fail, and it took some time to detect. During this period, ticket submission to todo.sr.ht failed, and emails were not forwarded from lists.sr.ht. You can thank Oracle for changing the license terms on Berkely DB, which had wider reaching consequences than we expected. (19:00 UTC — Jan 21)
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-7d1c5186df
Is SourceHut still down?
No, this incident was resolved 2021-01-21 19:00 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2021-01-21 19:00 UTC to 2021-01-21 19: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.