Readme incident

Refactored Hubs Down

Major Resolved View vendor source →

Readme experienced a major incident on May 28, 2026 affecting ReadMe Hubs and ReadMe Knowledge Base and 1 more component, lasting 4d 3h. The incident has been resolved; the full update timeline is below.

Started
May 28, 2026, 02:35 PM UTC
Resolved
Jun 01, 2026, 06:16 PM UTC
Duration
4d 3h
Detected by Pingoru
May 28, 2026, 02:35 PM UTC

Affected components

ReadMe HubsReadMe Knowledge BaseAdmin Dashboard

Update timeline

  1. investigating May 28, 2026, 01:40 PM UTC

    We're actively investigating this issue.

  2. identified May 28, 2026, 01:43 PM UTC

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

  3. identified May 28, 2026, 02:35 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring May 28, 2026, 03:27 PM UTC

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

  5. monitoring May 28, 2026, 03:33 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring May 28, 2026, 05:53 PM UTC

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

  7. monitoring May 28, 2026, 08:04 PM UTC

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

  8. monitoring May 29, 2026, 01:49 AM UTC

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

  9. monitoring May 29, 2026, 05:03 PM UTC

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

  10. monitoring May 29, 2026, 06:36 PM UTC

    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.

  11. resolved Jun 01, 2026, 06:16 PM UTC

    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.