Critical impactOngoingDevOps

GitBook outage: GitBook services unavailable

GitBook reported this critical-impact incident on its official status page on Nov 2, 2026, 20:26 UTC. It has not been marked resolved yet.

Right now GitBook is having a major outage. Live GitBook status →

🔔 Get alerted when GitBook has issuesFree · email alerts · no credit card
Nov 2, 2026, 20:26 UTC
started
—
resolved
ongoing
duration
Critical
impact
  1. monitoringNov 3, 2026, 03:40 UTC

    Both app and public content components are operational.

  2. 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.

  3. 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.

What APIStatus.watch saw

  • Nov 2, 2026, 20:29 UTCoperational → partial outage
  • Nov 3, 2026, 03:39 UTCpartial outage → major outage
  • Nov 3, 2026, 03:44 UTCmajor outage → operational
  • Nov 3, 2026, 05:19 UTCoperational → major outage

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitBook have incidents?

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