ReadMe outage: Issues Creating New Changelogs

Affected components

• Admin Dashboard

1. resolvedMay 8, 2026, 03:18 UTC

   This incident has been resolved.

2. monitoringMay 8, 2026, 03:02 UTC

   We have deployed the fix and are monitoring the results

3. identifiedMay 8, 2026, 00:40 UTC

   We have identified the issue preventing the changelog creation page from rendering correctly, and we are working on a fix

4. investigatingMay 7, 2026, 23:43 UTC

   We are currently investigating an issue creating changelogs

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.

• Datadog: Delayed Monitors NotificationsCritical · May 8, 2026, 00:06 UTC
• Convex: Intermittent Impact from AWS OutageMajor · May 8, 2026, 00:16 UTC
• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• RevenueCat: Increased API error rates due to reduced service capacity.Minor · May 8, 2026, 00:51 UTC
• Bitbucket: Multiple Atlassian services are experiencing issuesMinor · May 8, 2026, 01:31 UTC
• Confluence: Multiple Atlassian services are experiencing issuesMinor · May 8, 2026, 01:31 UTC
• MongoDB Atlas: AWS Availability Zone use1-az4 in US-EAST-1 Region is ImpairedMinor · May 8, 2026, 02:24 UTC
• ClickHouse Cloud: Increased Error Rate and Latency on AWS Region (US-EAST-1)Minor · May 8, 2026, 02:46 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