ReadMe logo

Is ReadMe Down?

SaaSLive status, outages, and incident history

No. ReadMe is up right now.

Every monitored ReadMe system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment ReadMe breaks

ReadMe is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official ReadMe status page
How we know: the official ReadMe status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

ReadMe Status Summary

As of 16:56 UTC on 9 November 2026, ReadMe is operational. PulsAPI checked ReadMe's official status page and found 11 of 11 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for ReadMe, counting degraded performance as up. The latest incident, "Degraded performance on documentation sites", was on Nov 2, 2026 and lasted 1h 40m.

Cite as: PulsAPI, “ReadMe status”, checked 9 November 2026, 16:56 UTC. https://www.pulsapi.com/services/readme

ReadMe Component Status

The main ReadMe systems on this page. All 11 are operational right now.

11operational
Admin Dashboard
Operational
Developer Metrics
Operational
Owlbot AI
Operational

8 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking ReadMe Hubs, ReadMe Knowledge Base, ReadMe Micro, Upstream Providers » Auth0 Machine to Machine Authentication, Upstream Providers » Auth0 Management API, Upstream Providers » Auth0 User Authentication, Upstream Providers » Cloudflare CDN/Cache, Upstream Providers » Cloudflare SSL for SaaS Provisioning.

See all of them free

Component statuses may change independently during partial outages.

Recent ReadMe Outages & Incidents

Incident history from the official ReadMe status page, including resolution updates.

Degraded performance on documentation sitesResolved Nov 2, 2026 · 1h 40mResolved

This incident has been resolved. --- [2026-11-02T15:31:03.712-08:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-11-02T14:52:34.116-08:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-11-02T14:39:16.503-08:00] (investigating) We identified an issue that is slowing down page loads on some ReadMe-hosted documentation sites.

Elevated 503 Errors and Documentation AvailabilityResolved Oct 23, 2026 · 23 minResolved

This incident has been resolved. --- [2026-10-23T09:07:52.495-07:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-23T08:47:56.255-07:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-23T08:46:43.147-07:00] (investigating) We are continuing to investigate this issue. --- [2026-10-23T08:46:05.500-07:00] (investigating) We're currently investigating an issue causing elevated 503 errors and timeouts when loading documentation pages.

Projects are not loadingResolved Oct 14, 2026 · 11 minResolved

Projects should be showing again. Please contact support@readme.com if you are still running into any 404 errors. --- [2026-10-14T15:52:59.763-07:00] (monitoring) The fix has been deployed and we're currently deploying the operational servers. There may be some cached 404s, so please let support know if you are still running into issues --- [2026-10-14T15:51:19.338-07:00] (identified) We have identified the issue and are working on a fix --- [2026-10-14T15:44:20.393-07:00] (investigating) We are currently investigating why pages are showing 404

ReadMe Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a ReadMe incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1199.94% average · 10 days with incidentsNov 9

Going further back: ReadMe uptime by month and every recorded ReadMe outage.

Live ReadMe Outage Reports

Problems reported by engineers using ReadMe. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No ReadMe problems reported yet.

Something wrong with ReadMe on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About ReadMe

Is ReadMe down? ReadMe reports live availability for 12 components at status.readme.com, among them ReadMe Hubs, ReadMe Knowledge Base and Admin Dashboard. Track ReadMe outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured ReadMe uptime at 100.00%. Response times, incident history, and SLA tracking for ReadMe are available on the PulsAPI dashboard.

ReadMe Status FAQ

Is ReadMe down right now?

The verdict at the top of this page comes from the latest poll of the official ReadMe status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if ReadMe is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until ReadMe recovers.

How do I check ReadMe uptime history?

PulsAPI tracks ReadMe uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever ReadMe changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect ReadMe outages?

PulsAPI reads the official ReadMe status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual ReadMe components?

Yes. PulsAPI monitors 11 individual ReadMe components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when ReadMe goes down?

Yes. Create a free account and subscribe to ReadMe: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with ReadMe to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot ReadMe problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor ReadMe?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so ReadMe plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track ReadMe with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services