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.
Posted Jun 01, 2026 - 11:16 PDT
Update
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.
Posted May 29, 2026 - 11:36 PDT
Update
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.
Posted May 29, 2026 - 10:03 PDT
Update
Systems remain stable. Improvements and fixes have been rolled out and we are continuing to monitor.
Posted May 28, 2026 - 18:49 PDT
Update
Systems appear stable and we are actively rolling out a series of fixes. We will continue to monitor and provide updates
Posted May 28, 2026 - 13:04 PDT
Update
We are receiving reports of degraded performance and are actively investigating. We will provide updates as more information becomes available.
Posted May 28, 2026 - 10:53 PDT
Update
We are continuing to monitor for any further issues.
Posted May 28, 2026 - 08:33 PDT
Monitoring
A fix has been implemented and we are monitoring the results.
Posted May 28, 2026 - 08:27 PDT
Update
Systems are getting back up. We're continuing to work on a permanent fix for this issue.
Posted May 28, 2026 - 07:35 PDT
Identified
The issue has been identified and a fix is being implemented.
Posted May 28, 2026 - 06:43 PDT
Investigating
We're actively investigating this issue.
Posted May 28, 2026 - 06:40 PDT
This incident affected: ReadMe Hubs, ReadMe Knowledge Base, and Admin Dashboard.