Is ReadMe Down?
- ReadMe's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 209 ms
Right now
The verdict is the worse of these two. How we decide
ReadMe's status page
readmestatus.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| ReadMe Hubs | Operational |
| ReadMe Knowledge Base | Operational |
| Admin Dashboard | Operational |
| Developer Metrics | Operational |
| Owlbot AI | Operational |
| ReadMe Micro | Operational |
| Cloudflare CDN/Cache | Operational |
| Cloudflare SSL for SaaS Provisioning | Operational |
| Auth0 User Authentication | Operational |
| Auth0 Machine to Machine Authentication | Operational |
| Auth0 Management API | Operational |
FlareWarden checks
readme.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 209 ms
- Checked
By region
- Ashburn reachable, 119 ms
- Dallas reachable, 243 ms
- Frankfurt reachable, 118 ms
- Johannesburg reachable, 482 ms
- London reachable, 155 ms
- Los Angeles reachable, 153 ms
- Newark reachable, 126 ms
- São Paulo reachable, 280 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 37 ms | 2 ms | 9 ms | 101 ms |
| Dallas | 50 ms | 1 ms | 53 ms | 170 ms |
| Frankfurt | 42 ms | 1 ms | 9 ms | 95 ms |
| Johannesburg | 173 ms | 2 ms | 64 ms | 354 ms |
| London | 57 ms | 3 ms | 9 ms | 137 ms |
| Los Angeles | 55 ms | 2 ms | 26 ms | 126 ms |
| Newark | 35 ms | 5 ms | 21 ms | 109 ms |
| São Paulo | 119 ms | 2 ms | 10 ms | 198 ms |
History
Incidents ReadMe reported
Since Oct 27, 10 days · from readmestatus.com
- Incidents
- 2
- Major or critical
- 1
- Median to resolve
- 1h 1m
- lasted 1h 40m
- lasted 23m
ReadMe website availability
Measured by FlareWarden · readme.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 200ms
Last 30 days
10-day clean streakMeasured by FlareWarden's own checks of readme.com from multiple regions every 6 hours. ReadMe's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 10 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What ReadMe does
ReadMe is a platform companies use to publish API documentation as hosted developer hubs: guides, API reference pages, recipes and changelogs, often on their own subdomain. Teams edit in ReadMe's Admin Dashboard or through bi-directional sync with GitHub, GitLab or Bitbucket. ReadMe also offers Developer Metrics on API usage and Owlbot, an AI chatbot for docs. When ReadMe Hubs fail, customers' public documentation sites fail with them.
What an outage looks like
Docs sites hosted on ReadMe load slowly or return 503 errors, timeouts or 404 pages, and editors cannot reach the Admin Dashboard. On October 23, 2026 documentation pages returned a rise in 503 errors for about 23 minutes; on October 14, 2026 projects showed 404s for 11 minutes. Hubs and the dashboard can fail separately: during the September 8, 2026 admin outage ReadMe said end users could still reach developer hubs.
What to do about it
Check readmestatus.com (status.readme.com redirects there) and see which row is red: ReadMe Hubs for public docs, Admin Dashboard for editing, Developer Metrics for API usage data. Upstream rows cover Cloudflare caching and custom domain SSL, and Auth0 sign-in. ReadMe queues new metrics during processing delays. If 404s linger after a fix, ReadMe has said some may be cached; contact support@readme.io or the in-app chat, staffed weekdays 10 AM to 6 PM Pacific.
Is it down for everyone, or just you?
If this page says ReadMe is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
ReadMe outage FAQ
Are my public docs down when the ReadMe dashboard is down?
Does a Cloudflare or Auth0 outage affect ReadMe?
Will I lose API metrics or Git sync changes during a ReadMe outage?
How long do ReadMe outages usually last?
What does the check on this page measure?
How we measure this
- We request ReadMe's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where ReadMe publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of ReadMe itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when ReadMe goes down
We check ReadMe every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring