ReadMe Outage History

29 incidents recorded over the last 365 days, 28 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live ReadMe status99.94% uptime history

Every Recorded ReadMe Incident

ReadMe incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 2, 2026Degraded performance on documentation sitesThis incident has been resolved.1h 40mResolved
Oct 23, 2026Elevated 503 Errors and Documentation AvailabilityThis incident has been resolved.23 minResolved
Oct 14, 2026Projects are not loadingProjects should be showing again. Please contact support@readme.com if you are still running into any 404 errors.11 minResolved
Sep 22, 2026Degraded Performance Across HubsThis incident has been resolved.2h 21mResolved
Sep 8, 2026Admin interface outageThis incident has been resolved.11 minResolved
Aug 21, 2026Slow search within customer hubsWe have re-indexed the search and performance has improved. Please e-mail support@readme.com if you're still seeing issues with search1h 45mResolved
Jul 24, 2026Degraded performance due to third-party infrastructure issuesThis incident has been resolved.1h 15mResolved
Jun 17, 2026API Reference DegradationThis incident was resolved and normal site function has been resolved2h 41mResolved
Jun 8, 2026Bi-directional sync maintenanceMaintenance has completed.3h 0mScheduled
May 28, 2026Refactored Hubs DownOur 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…99h 41mResolved
May 27, 2026ReadMe Refactored Outage### What Happened Beginning Tuesday, May 26, 2026, customers were experiencing slow loading and 503 errors across ReadMe-hosted docs and the admin dashboard. The outage was intermittent but recurring, with the worst…5h 29mResolved
May 26, 2026Slow performance across customer hubsThis incident has been resolved.10h 13mResolved
May 26, 2026Degraded performance across Admin HubsThis incident has been resolved.1h 58mResolved
May 12, 2026Degraded performance across Admin HubsThis incident has been resolved.6h 55mResolved
May 11, 2026Degraded performance across Admin HubsThis incident has been resolved.2h 51mResolved
May 7, 2026Issues Creating New ChangelogsThis incident has been resolved.3h 34mResolved
Apr 28, 2026Creating branches is resulting in 500 errorsBranches and versions can now be created successfully52 minResolved
Apr 24, 2026Service disruptionThis incident has been resolved.2h 53mResolved
Apr 22, 2026Admin downtimeIssues with admin requests have been resolved.2h 0mResolved
Apr 22, 2026Slow performance, increased 500 errors upon page loadFix has been implemented and performance has stabilized.44 minResolved
Apr 20, 2026Increased Admin Response TimesThis incident has been resolved.1h 15mResolved
Apr 16, 2026Slow performance / 500 error pagesPerformance has stabilized and we are no longer returning errors upon loading pages.3h 18mResolved
Apr 15, 2026Slow page performanceThis incident has been resolved.6h 15mResolved
Apr 8, 2026Discussion posts throwing 500 errorsThis incident has been resolved.3h 35mResolved
Mar 31, 2026Readme high response times.This incident has been resolved.24 minResolved
Mar 30, 2026Issues with saving MDXYou should be able to save again!5 minResolved
Dec 20, 2025ReadMe Hub DownThis incident has been resolved.1h 23mResolved
Dec 5, 2025Dash and Hub OutageThis has now been resolved upstream.42 minResolved
Nov 18, 2025Cloudflare outageThis incident has been resolved.1h 41mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next ReadMe incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This ReadMe Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before ReadMe acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single ReadMe outage in this window ran 4d 3h, against a mean recovery of 5h 50m. If you depend on ReadMe in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.