- Level
- confirmed
- Worst impact
- Maintenance
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.Check that everything you run on SourceHut came back after the window closed 2025-04-03 12:00 UTC.
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
Restart completed . Again, note that some upstream connections may take a while to be re-established due to rate limits. (12:05 UTC — Apr 3) Planned bouncer upgrade is scheduled for Thursday, April 3rd . On Thursday at 12:00 UTC we will be rolling out an upstream update for soju, the software that powers the chat.sr.ht bouncer. The bouncer will be restarted, causing everyone to be disconnected. Most clients will reconnect automatically. Note that some upstream connections may take a while to be re-established due to rate limits. (09:55 UTC — Mar 31)
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-00724dcabe
Is this SourceHut maintenance still going on?
No, it ended 2025-04-03 12:00 UTC.
How long did it last?
0m, from 2025-04-03 12:00 UTC to 2025-04-03 12: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.