Critical impactResolvedDevOps

GitBook outage: GitBook services unavailable

GitBook reported this critical-impact incident on its official status page on Nov 2, 2026, 20:26 UTC. It was resolved after 8h 25m.

Right now GitBook is operational. Live GitBook status →

Nov 2, 2026, 20:26 UTC

started

Nov 3, 2026, 04:52 UTC

resolved

8h 25m

duration

Critical

impact

Timeline

resolvedNov 3, 2026, 04:52 UTC
This incident should be fully resolved.
monitoringNov 3, 2026, 03:40 UTC
Both app and public content components are operational.
monitoringNov 3, 2026, 03:37 UTC
The incident has now been mitigated and all published content, editing, and Git services are back up. We are continuing to monitor and will post a detailed post-mortem in the next 24 hours.
identifiedNov 2, 2026, 20:26 UTC
We’re currently investigating an issue affecting logging in to the GitBook app via SSO, as well as published sites that use authenticated access. Users may be unable to sign in, and visitors to authenticated sites may be unable to load content. Public sites are not affected and are loading as normal. Our team is actively working on a fix and we’ll share another update as soon as we have more information.

Overlapping incidents aren't necessarily related.

GitBook reported 7 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 7h 18m. See GitBook's uptime and incident history