[Resolved] Our upstream network provider is experiencing issues

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 2021-12-20 20:03 UTC and 2021-12-20 20:03 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. resolvedDec 20, 2021, 8:03 PM UTC

   The issue has been resolved : The upstream network has corrected the problem. Normal service should be restored. Over the course of 19 minutes, we dropped 10 of our ~500 upstream chat.sr.ht connections. We are still experiencing internal issues, but they are not service impacting and we expect them to clear up shortly. (20:22 UTC — Dec 20) An ongoing issue with our upstream network provider is causing chat.sr.ht reliability problems : An issue with our network provider is causing some unreliability for our services. The full extent of the problem is still not known, but the most important consequence of it so far is that chat.sr.ht connections to upstream networks are unreliable. You may experience disconnections and intermittent service. (20:03 UTC — Nov 16)

   provider

Corrections

None so far.

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