GitBook outage: 500 errors on some *.gitbook.io published sites

1. resolvedMay 4, 2026, 14:00 UTC

   We issued a fix and have monitored the results of that fix. Pages are now loading at normal rates and our logs are looking healthy.

2. investigatingMay 4, 2026, 11:55 UTC

   We’re currently investigating an issue affecting some published sites on `*.gitbook.io`

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.

• Contentful: Some customers are experiencing issues logging inMajor · May 4, 2026, 13:20 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · Apr 29, 2026, 05:19 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC
• LaunchDarkly: Elevated Streaming Errors in EuropeMinor · May 4, 2026, 10:14 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