GitBook outage: Degraded database performance

1. resolvedMay 8, 2026, 18:15 UTC

   The fix has improved the performance back to their normal levels.

2. monitoringMay 8, 2026, 16:39 UTC

   A fix has been deployed, we are monitoring the performance.

3. investigatingMay 8, 2026, 15:52 UTC

   We are seeing a decrease in our database performance causing various actions in the app to hang. Our engineering team is investigating the root cause.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitBook'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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Elasticsearch: Issues with Email AlertsMajor · May 8, 2026, 18:10 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
• 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
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• DigitalOcean: Multiple Services in NYC2Minor · May 8, 2026, 18:01 UTC

How often does GitBook have incidents?

GitBook reported 2 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 3h 42m. See GitBook's uptime and incident history