[Resolved] LLM crawlers continue to DDoS SourceHut

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 2025-01-23 09:30 UTC and 2025-01-23 09: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. resolvedJan 23, 2025, 9:30 AM UTC

   SourceHut continues to face disruptions due to aggressive LLM crawlers . We are continuously working to deploy mitigations, instead of doing any of the other numerous things we have to do, like develop new features, upgrade our infrastructure, or respond to support emails in a timely manner. We have deployed a number of mitigations which are keeping the problem contained for now. However, some of our mitigations may impact end-users. If you are unable to use the SourceHut web UI : First, log into your SourceHut account. Logged-in users bypass some of our mitigations. If that does not work, please contact support on IRC or via email . If your cloud server is unable to reach SourceHut : We have unilaterally blocked several cloud providers, including GCP and Azure, for the high volumes of bot traffic originating from their networks. If you have a legitimate reason to access SourceHut from these networks, you must email support to request an exception. Explain your use-case and provide the affected IP addresses. Note that our mitigations targetting cloud servers affect git operations. (09:30 UTC — Jan 23)

   provider

Corrections

None so far.

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