Skip to main content
ReadMe

Degraded performance due to third-party infrastructure issues

Degraded Lasted 1h 16m · started · ReadMe's page

Level
confirmed
Worst impact
Degraded
Components
ReadMe Hubs, Admin Dashboard
Down Index
22of 100

What to do

  • Check whether you use ReadMe ReadMe Hubs, Admin Dashboard. 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 1h 16m it lasted.

    Anything that failed between 2026-07-24 12:22 UTC and 2026-07-24 13:37 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 2

  1. monitoring

    Experiencing degraded performance due to third-party infrastructure issues. We are monitoring this situation and working to maintain stability on our end.

    provider

  2. resolved

    This incident has been 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-548562a770

Is ReadMe still down?

No, this incident was resolved 2026-07-24 13:37 UTC. For ReadMe's live state, see https://down.guide/readme.

How long did it last?

1h 16m, from 2026-07-24 12:22 UTC to 2026-07-24 13:37 UTC, by the times ReadMe posted.

What was affected?

ReadMe named ReadMe Hubs, Admin Dashboard.

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.