GitBook outage: GitBook webapp is returning 500

1. resolvedJun 25, 2026, 13:08 UTC

   The incident has been resolved and systems are fully operational.

2. monitoringJun 25, 2026, 13:07 UTC

   A fix has been released, and we're monitoring it

3. identifiedJun 25, 2026, 12:29 UTC

   A fix is being deployed, we are monitoring the change.

4. identifiedJun 25, 2026, 11:34 UTC

   A faulty SQL migration caused a corrupted deployment. Our team is working on a fix.

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.

• Vercel: Increase in Workflow runs stuck as pendingMajor · Jun 25, 2026, 07:45 UTC
• Smartsheet: Increased spam activity with Smartsheet FormsMinor · Jun 18, 2026, 21:42 UTC
• Snyk: Third-Party Vendor Security Incident (Klue)Minor · Jun 19, 2026, 23:15 UTC
• Snyk: Degraded Peformance Affecting SNYK-US-01Minor · Jun 24, 2026, 21:39 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