Skip to main content
ReadMe

Intermittent hub sites going down

Partial outage Lasted 13h 5m · started · ReadMe's page

Level
confirmed
Worst impact
Partial outage
Components
ReadMe Hubs
Down Index
35of 100

What to do

  • Check whether you use ReadMe ReadMe Hubs. 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 13h 5m it lasted.

    Anything that failed between 2025-06-24 10:27 UTC and 2025-06-24 23:32 UTC may need a replay.
  • Subscribe to ReadMe's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=readme works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from ReadMe 6

  1. investigating

    We are currently investigating downtime across some hubs. This appears to be the same issue as yesterday, we are actively working on resolving.

    provider

  2. monitoring

    A temporary fix has been applied to our cache infrastructure. We will be applying more permanent fixes in the background while we monitor the situation.

    provider

  3. identified

    ReadMe Refactored projects are currently down and returning errors; our team is actively working on a solution.

    provider

  4. identified

    ReadMe Refactored projects are back up as cache is refreshed. We are aware of the cause and are implementing a permanent fix.

    provider

  5. monitoring

    We have deployed changes to our infrastructure and performance is holding steady. Our engineers will continue to monitor systems to guarantee overall stability.

    provider

  6. resolved

    We've validated our infrastructure changes and are marking the incident as resolved.

    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-7e09cd16bb

Is ReadMe still down?

No, this incident was resolved 2025-06-24 23:32 UTC. For ReadMe's live state, see https://down.guide/readme.

How long did it last?

13h 5m, from 2025-06-24 10:27 UTC to 2025-06-24 23:32 UTC, by the times ReadMe posted.

What was affected?

ReadMe named ReadMe Hubs.

What caused it?

ReadMe hasn't published a root cause. If it does, it shows here.

Where does this come from?

ReadMe's official status page, https://www.readmestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.