Minor impactResolvedDevOps

ReadMe incident: Slightly elevated error rates

ReadMe reported this minor-impact incident on its official status page on May 19, 2025, 17:35 UTC. It was resolved after 4h 8m.

Right now ReadMe is operational. Live ReadMe status →

🔔 Get alerted when ReadMe has issuesFree · email alerts · no credit card
May 19, 2025, 17:35 UTC
started
May 19, 2025, 21:43 UTC
resolved
4h 8m
duration
Minor
impact

Affected components

  • ReadMe Hubs

Timeline

updates from ReadMe's status page ↗
  1. resolvedMay 19, 2025, 21:43 UTC

    We have eliminated the slightly elevated error rates.

  2. identifiedMay 19, 2025, 18:49 UTC

    The issue has been identified and a fix is being implemented.

  3. investigatingMay 19, 2025, 17:35 UTC

    We are continuing to investigate this issue.

  4. investigatingMay 19, 2025, 17:35 UTC

    We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in ReadMe's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does ReadMe have incidents?

ReadMe reported 4 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 30m. See ReadMe's uptime and incident history

← Previous: Search results not showing up in "All" tab on hubs (May 19, 2025)Next: ReadMe Hubs and Dashboard are down (May 30, 2025) →
ReadMe incident on May 19, 2025: Slightly elevated error rates · APIStatus.watch