Skip to main content
SourceHut

[Resolved] Planned outage for hg.sr.ht

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

Level
confirmed
Worst impact
Partial outage
Down Index
28of 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 2020-07-29 17:00 UTC and 2020-07-29 17: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. resolved

    Maintenance complete . Depending on how soon your DNS server picks up the updates, you should find service restored shortly. (21:00 UTC — Jul 29) We’re still waiting on the latest data to transfer from the old server to the new. It is taking longer than we expected. The process is about halfway complete. We apologise for the delay. (19:00 UTC — Jul 29) Maintenance may require more time than expected . (17:50 UTC — Jul 29) Planned maintenance has begun . (17:00 UTC — Jul 29) Planned maintenance on July 29th will cause an hg.sr.ht outage : At 17:00 UTC on July 29th, we will conduct planned maintenance on hg.sr.ht to migrate the primary server to newer hardware. It is expected to take no more than an hour, during which time hg.sr.ht will be available in read-only mode. (17:00 UTC — Jul 29)

    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-4852afecf5

Is SourceHut still down?

No, this incident was resolved 2020-07-29 17:00 UTC. For SourceHut's live state, see https://down.guide/sourcehut.

How long did it last?

0m, from 2020-07-29 17:00 UTC to 2020-07-29 17:00 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.