ReadMe status history
29 incidents over the last year, newest first; 99.99% uptime (90 days), 99.98% uptime (12 months). History from before down.guide started reading the page is imported from ReadMe's own archive.
Month
2026-11
1 incident
Month
2026-10
2 incidents
- ReadMePartial outageElevated 503 Errors and Documentation Availability
- ReadMeMajor outageProjects are not loading
Month
2026-09
2 incidents
- ReadMeDegradedDegraded Performance Across Hubs
- ReadMeMajor outageAdmin interface outage
Month
2026-08
1 incident
Month
2026-07
1 incident
Month
2026-06
1 incident
- ReadMeDegradedAPI Reference Degradation
Month
2026-05
7 incidents
- ReadMePartial outageRefactored Hubs Down
- ReadMeMajor outageReadMe Refactored Outage
- ReadMePartial outageSlow performance across customer hubs
- ReadMePartial outageDegraded performance across Admin Hubs
- ReadMeDegradedDegraded performance across Admin Hubs
- ReadMeDegradedDegraded performance across Admin Hubs
- ReadMeMajor outageIssues Creating New Changelogs
Month
2026-04
8 incidents
- ReadMeDegradedCreating branches is resulting in 500 errors
- ReadMeMajor outageService disruption
- ReadMePartial outageAdmin downtime
- ReadMeDegradedSlow performance, increased 500 errors upon page load
- ReadMeDegradedIncreased Admin Response Times
- ReadMeDegradedSlow performance / 500 error pages
- ReadMeDegradedSlow page performance
- ReadMePartial outageDiscussion posts throwing 500 errors
Month
2026-03
2 incidents
- ReadMePartial outageReadme high response times.
- ReadMeDegradedIssues with saving MDX
Month
2025-12
2 incidents
- ReadMeDegradedReadMe Hub Down
- ReadMePartial outageDash and Hub Outage
Month
2025-11
1 incident
- ReadMePartial outageCloudflare outage
Month
2025-10
1 incident