Major impactResolvedDevOps

GitBook outage: Increased API error rate

GitBook reported this major-impact incident on its official status page on Jun 2, 2026, 14:40 UTC. It was resolved after 1h 29m.

Right now GitBook is operational. Live GitBook status →

🔔 Get alerted when GitBook has issuesFree · email alerts · no credit card
Jun 2, 2026, 14:40 UTC
started
Jun 2, 2026, 16:09 UTC
resolved
1h 29m
duration
Major
impact
  1. resolvedJun 2, 2026, 16:09 UTC

    The incident has been resolved, all systems have returned to normal.

  2. monitoringJun 2, 2026, 15:32 UTC

    A fix has been deployed and the app and the API are responding normally. We are continuing to monitor the performance.

  3. investigatingJun 2, 2026, 14:40 UTC

    We are investigating an increased error rate in our API. This only affects the GitBook app, and public content is working as expected.

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.

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

GitBook outage on Jun 2, 2026: Increased API error rate · APIStatus.watch