ReadMe incident: Slow search within customer hubs

Affected components

• ReadMe Hubs

1. resolvedAug 21, 2026, 18:21 UTC

   We have re-indexed the search and performance has improved. Please e-mail [email protected] if you're still seeing issues with search

2. identifiedAug 21, 2026, 16:36 UTC

   We are currently experiencing slow search results across customer hubs

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.

• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Zoom: Service Degradation Affecting Meta integration for Zoom.Minor · Aug 21, 2026, 11:04 UTC

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