Major impactResolvedDevOps

GitBook outage: Degraded API performance

GitBook reported this major-impact incident on its official status page on Mar 27, 2026, 14:43 UTC. It was resolved after 4h 4m.

Right now GitBook is operational. Live GitBook status →

🔔 Get alerted when GitBook has issuesFree · email alerts · no credit card
Mar 27, 2026, 14:43 UTC
started
Mar 27, 2026, 18:47 UTC
resolved
4h 4m
duration
Major
impact
  1. resolvedMar 27, 2026, 18:47 UTC

    Indicators are pointing to a healthy state now after the fix. Everything should be operating well.

  2. monitoringMar 27, 2026, 16:48 UTC

    We have issued the root-cause fix and are monitoring the results.

  3. monitoringMar 27, 2026, 14:55 UTC

    We have identified the issue and have mitigated it. We are currently monitoring the API and working on a root-cause fix.

  4. investigatingMar 27, 2026, 14:43 UTC

    We are currently experiencing a degradation in API performance causing various endpoints to hang.

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 Mar 27, 2026: Degraded API performance · APIStatus.watch