- 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-05-14 12:00 UTC and 2021-05-14 12: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
Snapshot growth caused an outage on git.sr.ht git.sr.ht’s ZFS snapshots grew to consume all available disk space. This is normally an understood pathology of the server configuration, but due to a change in billing with Twilio, our paging script did not alert the operators to the imminent issue. It seems that there is not a grace period with Twilio; they reported the billing issue to us only yesterday. The issue with git.sr.ht has been resolved, the bill has been paid, and we are researching ways to avoid this occuring again in the future. (15:00 UTC — May 14)
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-d5ecda3a4d
Is SourceHut still down?
No, this incident was resolved 2021-05-14 12:00 UTC. For SourceHut's live state, see https://down.guide/sourcehut.
How long did it last?
0m, from 2021-05-14 12:00 UTC to 2021-05-14 12:00 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.