We are investigating widespread downtime across all hubs

What to do

• Check whether you use ReadMe ReadMe Hubs. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 32m it lasted.

  Anything that failed between 2025-06-23 14:16 UTC and 2025-06-23 15:48 UTC may need a replay.

• Subscribe to ReadMe's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=readme works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from ReadMe 6

1. investigatingJun 23, 2025, 1:29 PM UTC

   We are currently investigating and will update as/when we know more.

   provider

2. investigatingJun 23, 2025, 2:16 PM UTC

   We have identified a likely cause and are working on remediating.

   provider

3. monitoringJun 23, 2025, 2:16 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

4. monitoringJun 23, 2025, 2:19 PM UTC

   We are continuing to monitor for any further issues.

   provider

5. monitoringJun 23, 2025, 3:37 PM UTC

   We've identified the root cause of the issue: a cold cache, which temporarily prevented some pages from loading. The cache is regenerating, and things are coming back to normal.

   provider

6. resolvedJun 23, 2025, 3:48 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.