ReadMe incident: Creating branches is resulting in 500 errors

Affected components

• ReadMe Hubs

1. resolvedApr 28, 2026, 19:31 UTC

   Branches and versions can now be created successfully

2. identifiedApr 28, 2026, 19:02 UTC

   We have identified the issue and are currently looking into a fix

3. investigatingApr 28, 2026, 18:38 UTC

   We are currently investigating an issue where customers are unable to create branches

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.

• Elasticsearch: Missing Metrics in Cloud Console — US East (us-east-1)Major · Apr 28, 2026, 14:46 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• DigitalOcean: Elevated 5xx “context canceled” errors impacting serverless inferenceMinor · Apr 28, 2026, 13:45 UTC
• Akamai: Intermittent Edge Delivery Delays in Chennai, IN (MAA) RegionMinor · Apr 28, 2026, 16:42 UTC
• Linode: Service Issue - Connectivity Issues - Chennai (IN-MAA)Minor · Apr 28, 2026, 17:17 UTC
• LaunchDarkly: Issues with Observability Alert NotificationMinor · Apr 28, 2026, 18:34 UTC
• Inngest: Increased function execution latencyMinor · Apr 28, 2026, 19:11 UTC
• Discord: Connection DelaysMinor · Apr 28, 2026, 19:20 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