Skip to main content
down.guideby Sazabi
ReadMe
DWN-86185dbba9ReadMeResolved

Refactored Hubs Down

Partial outage Lasted 4d 3h · started · ReadMe's page

Level
confirmed
Worst impact
Partial outage
Components
ReadMe Hubs, ReadMe Knowledge Base, Admin Dashboard
Down Index
38of 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 4d 3h it lasted.

    Anything that failed between 2026-05-28 14:35 UTC and 2026-06-01 18:16 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 11

  1. investigating

    We're actively investigating this issue.

    provider

  2. identified

    The issue has been identified and a fix is being implemented.

    provider

  3. identified

    Systems are getting back up. We're continuing to work on a permanent fix for this issue.

    provider

  4. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  5. monitoring

    We are continuing to monitor for any further issues.

    provider

  6. monitoring

    We are receiving reports of degraded performance and are actively investigating. We will provide updates as more information becomes available.

    provider

  7. monitoring

    Systems appear stable and we are actively rolling out a series of fixes. We will continue to monitor and provide updates

    provider

  8. monitoring

    Systems remain stable. Improvements and fixes have been rolled out and we are continuing to monitor.

    provider

  9. monitoring

    Systems remain stable, and we are continuing to monitor the situation. Bi-directional sync was on a maintenance job from 9:50 - 11:59 AM (ET) and is now operational.

    provider

  10. monitoring

    Systems remain stable and our team continues to deploy targeted fixes. Work is ongoing to address degraded read performance across the system, including serving all 404s from cache. We’ll be actively monitoring over the weekend, and we will provide a full RCA next week.

    provider

  11. resolved

    Our systems have been stable since Friday, May 29th. We're monitoring closely and improving spike detection to prevent recurrence and adding proactive capacity monitoring to detect admin dashboard degradation before it impacts customers. Full root cause analysis coming soon. Thanks for your patience and understanding.

    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-86185dbba9

Is ReadMe still down?

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

How long did it last?

4d 3h, from 2026-05-28 14:35 UTC to 2026-06-01 18:16 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.

Sources

More from ReadMe

Feed