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

OperationalChecked 31m agoLive, rechecked every 60s
Start monitoring ReadMeOfficial 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

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.

Create a free account

Component statuses may change independently during partial outages.

Recent ReadMe Outages & Incidents

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

Uptime history4 days observed
Aug 8100.00% averageAug 11
Degraded performance due to third-party infrastructure issuesResolved Jul 24, 2026 · 1h 15mResolved

This incident has been resolved. --- [2026-07-24T05:22:10.461-07:00] (monitoring) Experiencing degraded performance due to third-party infrastructure issues. We are monitoring this situation and working to maintain stability on our end.

API Reference DegradationResolved Jun 17, 2026 · 2h 41mResolved

This incident was resolved and normal site function has been resolved --- [2026-06-17T08:28:57.931-07:00] (investigating) We are currently investigating an incident related to API Reference pages.

Bi-directional sync maintenanceScheduled for Jun 8, 2026 · 3h 0mScheduled

Maintenance has completed. --- [2026-06-08T11:10:07.310-07:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-06-08T11:09:43.571-07:00] (scheduled) Bi-directional sync is currently undergoing extended maintenance. Content syncing may be delayed. Any changes queued during this window will sync automatically once service is restored, in the order they were received.

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?

PulsAPI checks ReadMe every 60 seconds. 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.

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%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for ReadMe.

How fast does PulsAPI detect ReadMe outages?

PulsAPI polls the official ReadMe status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

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 PulsAPI account and subscribe to ReadMe. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever ReadMe status changes.

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. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor ReadMe alongside up to 9 other services at pulsapi.com/signup.

Track ReadMe with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when ReadMe status changes.

Start free trial