[Resolved] SourceHut disrupted due to DDoS attack

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 2026-04-22 15:30 UTC and 2026-04-22 15:30 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

1. resolvedApr 22, 2026, 3:30 PM UTC

   SourceHut is being disrupted by a DDoS attack . A DDoS attack similar to the one experienced a couple of weeks ago is currently targetting meta.sr.ht. Many services depend on meta.sr.ht and are therefore also affected. We are looking into mitigations. (15:30 UTC — Apr 22) Migitations are being rolled out . We have deployed some mitigations to improve service reliability during the attack. However, we expect further disruptions. We are continuing to monitor the situation. (15:41 UTC — Apr 22)

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.