Skip to main content
ReadMe

Degraded Performance Across Hubs

Degraded Lasted 2h 22m · started · ReadMe's page

Level
confirmed
Worst impact
Degraded
Components
ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard
Down Index
24of 100

What to do

  • Check whether you use ReadMe ReadMe Hubs, ReadMe Knowledge Base, 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 2h 22m it lasted.

    Anything that failed between 2026-09-22 14:22 UTC and 2026-09-22 16:44 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 5

  1. investigating

    We're currently investigating elevated latency and slow response times affecting hubs. Actively working to identify the root cause and restore normal service.

    provider

  2. monitoring

    A fix has been implemented and we're currently monitoring the results. Performance should be returning to normal.

    provider

  3. monitoring

    We've identified additional contributing factors and are actively working to fix them.

    provider

  4. monitoring

    We are continuing to monitor for any further issues.

    provider

  5. 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-3c2faba204

Is ReadMe still down?

No, this incident was resolved 2026-09-22 16:44 UTC. For ReadMe's live state, see https://down.guide/readme.

How long did it last?

2h 22m, from 2026-09-22 14:22 UTC to 2026-09-22 16:44 UTC, by the times ReadMe posted.

What was affected?

ReadMe named ReadMe Hubs, ReadMe Knowledge Base, 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.