Skip to main content
SourceHut

[Resolved] Unreachable database host

Major outage Lasted 0m · started · SourceHut's page

Level
confirmed
Worst impact
Major outage
Down Index
40of 100

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 2023-01-11 13:38 UTC and 2023-01-11 13:38 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. resolved

    Service restored . We have migrated the database to a temporary host and brought our services back online. We had to use one of our build servers to host it for the time being, so our build system is operating at half its normal capacity – you may notice longer-than-usual build times while we roll out a permanent solution. Thank you for your patience. (17:00 UTC — Jan 11) Investigating . We have a technician on-site and are diagnosing the issue further. (15:47 UTC — Jan 11) Unreachable host causing disruption of multiple services . Our database host has suddenly become unreachable, causing all services requiring it to become unavailable. We are currently working with people on location to determine the exact issue. (14:00 UTC — Jan 11)

    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-3388d5c1f4

Is SourceHut still down?

No, this incident was resolved 2023-01-11 13:38 UTC. For SourceHut's live state, see https://down.guide/sourcehut.

How long did it last?

0m, from 2023-01-11 13:38 UTC to 2023-01-11 13:38 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.