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 September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment ReadMe breaks

ReadMe is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official ReadMe status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

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 Across HubsResolved Sep 22, 2026 · 2h 21mResolved

This incident has been resolved. --- [2026-09-22T08:16:56.541-07:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-09-22T08:03:23.286-07:00] (monitoring) We've identified additional contributing factors and are actively working to fix them. --- [2026-09-22T07:41:03.319-07:00] (monitoring) A fix has been implemented and we're currently monitoring the results. Performance should be returning to normal. --- [2026-09-22T07:22:36.134-07:00] (investigating) We're currently investigating elevated latency and slow response times affecting hubs. Actively working to identify the root cause and restore normal service.

Admin interface outageResolved Sep 8, 2026 · 11 minResolved

This incident has been resolved. --- [2026-09-08T09:15:46.569-07:00] (investigating) We were able to resolve the situation. There may be some intermittent sluggishness for the next few minutes. --- [2026-09-08T09:04:53.736-07:00] (investigating) Our Admin interface is experiencing an outage. The ability of end-users to visit your ReadMe developer hub is unaffected.

Slow search within customer hubsResolved Aug 21, 2026 · 1h 45mResolved

We have re-indexed the search and performance has improved. Please e-mail support@readme.com if you're still seeing issues with search --- [2026-08-21T09:36:43.961-07:00] (identified) We are currently experiencing slow search results across customer hubs

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 history49 days observed
Aug 899.90% average · 6 days with incidentsSep 25

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 99.99%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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 99.99%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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

2463+ 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