PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if ReadMe is down?

PulseWatch evaluates user reports and replay-approved automated evidence for ReadMe. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported ReadMe issues today?

As of Sep 29, 2026 14:20 UTC, 0 users had reported issues with ReadMe in the previous 24 hours.

How can I report a ReadMe outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is ReadMe down right now?

NormalOfficial status last polled Sep 29, 2026 13:04 UTCreadme.com Official status page

Are you on the ReadMe team and see something inaccurate? Report it to us. We respond within one business day.

Is ReadMe down right now?

No. ReadMe has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 29, 2026 14:20 UTC

Normal

ReadMe is operating normally

As of Sep 29, 2026 14:20 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 22, 2026 17:26 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for ReadMe.

Incident days

No recorded incident

2h 58m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for ReadMe. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

2h 58m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

ReadMe outage on September 22 — 2h 57m disruption

Sep 22, 02:29 PM → Sep 22, 05:26 PM · 2h 57m · medium

A medium-severity service disruption affected ReadMe for approximately 2 hours and 57 minutes. The incident began on September 22, 2026, at 14:29 UTC. The service was fully restored and the incident resolved at 17:26 UTC on the same day.

Peak reports

in 15 min

Total reports

during outage

Duration

2h 57m

until recovery

Impact

During the 2 hour and 57 minute period of this medium-severity incident, the ReadMe service experienced a disruption. This incident was detected through automated monitoring signals, including the vendor's status page. No user-reported data was collected for this incident.

Outage timeline

Sep 22, 02:29 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 22, 02:29 PM
Status updated: possible issue
Sep 22, 05:26 PM
Signals cleared — incident resolved

Official updates

Sep 22, 02:29 PM
ReadMe status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.59%

90-day uptime

99.46%

Calculated from ReadMe's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

ReadMe: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/22/2026, 2:29:11 PM · 2h 57m

02:29 PM05:26 PM

Detection9/22/2026, 2:29:11 PM · 6d ago

Detected — medium severity

ReadMe: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium