[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-05 10:00 UTC and 2026-04-05 10: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

1. resolvedApr 5, 2026, 10:00 AM UTC

   SourceHut was disrupted by a DDoS attack . Over the holidays SourceHut experienced a DDoS attack primarily targetting git.sr.ht. For a period of several hours we experienced severe performance issues and intermittent outages as a result, primarily affecting git.sr.ht. Our upstream network provider identified the malicious traffic and blackholed the appropriate routes, but due to a configuration error SourceHut’s AMS subnet was entirely null routed for a period of about one hour yesterday, causing a complete outage for all services. Once the configuration error was corrected, the DDoS continued to cause performance issues that primarily affected git.sr.ht, until the attack died down later yesterday afternoon. The approximately 1-hour total outage of our AMS installation caused a severe network partition that disrupted systems hosted in other installations, notably our build workers. These issues were not understood until this morning, when the ensuing problems were corrected. However, builds submitted in the meanwhile were cancelled, and users will have to resubmit any builds from this period that still need to be run. You can do this by opening the affected build on the builds.sr.ht web UI and clicking “Resubmit”. Additionally, there have been some issues updating our status page, which resulted in poor communication during the incident. An old outage notice was never properly closed, and during the outage updating the status page was a challenge – and a distraction. We elected to defer the solution until today to allow our engineers to enjoy what remains of their holiday weekends. The status page issues have now been resolved. We apologize for the inconvenience. (10:00 UTC — Apr 6) Attacks have resumed. DDoS attacks targetting git.sr.ht have resumed, disrupting performance and availability. We are looking into mitigations. (15:30 UTC — Apr 6) Attacks are ongoing. We continue to experience a DDoS attack primarily targetting git.sr.ht. We are continuing to explore mitigations but in the meantime you can expect continued degraded performance on git.sr.ht, particularly with SSH operations. (10:30 UTC — Apr 7) Attacks now targeting builds.sr.ht. After a brief pause the attack is now targeting builds.sr.ht. We are once more working on mitigations. (15:30 UTC — Apr 8)

   provider

Corrections

None so far.

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