- 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 2020-06-28 12:07 UTC and 2020-06-28 12:07 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 unexpected Redis failure caused a partial outage of git.sr.ht The git.sr.ht web service was partially interrupted today due to unexpected Redis errors. Some pages which rely on Redis for caching returned 500 errors, namely the summary and tree pages. The issue has been resolved. To prevent its recurrence, we have filed a ticket to make our caching system more tolerant of Redis outages, and added an alarm to detect this kind of issue earlier. (12:07 UTC — Jun 28)
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-3cb77dad4b
Is SourceHut still down?
No, this incident was resolved 2020-06-28 12:07 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2020-06-28 12:07 UTC to 2020-06-28 12:07 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.