GitBook services unavailable

What to do

• Check whether your product depends on GitBook. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 8h 25m it lasted.

  Anything that failed between 2026-11-02 20:26 UTC and 2026-11-03 04:52 UTC may need a replay.

• Subscribe to GitBook's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=gitbook works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

• Watch for the root-cause report GitBook said it would publish (said 2026-11-03 03:37 UTC); it shows on this page when it lands.

Root cause

GitBook said 2026-11-03 03:37 UTC that it would publish a root-cause report; none published yet.

Updates from GitBook 4

1. identifiedNov 2, 2026, 8:26 PM 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.

   provider

2. monitoringNov 3, 2026, 3:37 AM 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.

   provider

3. monitoringNov 3, 2026, 3:40 AM UTC

   Both app and public content components are operational.

   provider

4. resolvedNov 3, 2026, 4:52 AM UTC

   This incident should be fully resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.