Readme incident

Very high request volume as well as high error rate

Critical Resolved View vendor source →

Readme experienced a critical incident on May 20, 2024 affecting ReadMe Hubs and ReadMe Knowledge Base and 1 more component, lasting 2h 39m. The incident has been resolved; the full update timeline is below.

Started
May 20, 2024, 07:39 PM UTC
Resolved
May 20, 2024, 10:18 PM UTC
Duration
2h 39m
Detected by Pingoru
May 20, 2024, 07:39 PM UTC

Affected components

ReadMe HubsReadMe Knowledge BaseAdmin DashboardOwlbot AI

Update timeline

  1. investigating May 20, 2024, 07:39 PM UTC

    We are currently investigating this issue.

  2. investigating May 20, 2024, 07:40 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 20, 2024, 07:42 PM UTC

    We are continuing to investigate this issue.

  4. investigating May 20, 2024, 07:42 PM UTC

    We are continuing to investigate this issue.

  5. monitoring May 20, 2024, 07:55 PM UTC

    We've discovered the culprit and blocked traffic to the offending IP. Our dashboard is now back up, and we are currently monitoring the situation.

  6. resolved May 20, 2024, 10:18 PM UTC

    This incident has been resolved.

  7. postmortem May 21, 2024, 03:57 PM UTC

    On Monday, May 20, ReadMe users experienced issues accessing the ReadMe Dashboard \([dash.readme.com](http://dash.readme.com)\) from 19:33 to 19:45 UTC. Users may have experienced errors or slow response times when accessing the Dash. Mitigations were applied by 19:45 UTC and the dashboard quickly resumed normal operation.