- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 100
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 0m it lasted.
Anything that failed between 2026-03-06 16:56 UTC and 2026-03-06 14:36 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.
Updates from GitBook 1
- resolved
Between 14:36 and 14:43 UTC, all GitBook documentation sites using a custom domain were returning a 404 "Not Found" error, making documentation unavailable to users. The issue was caused by a problem introduced by an upstream provider that affected our deployment. The incident was resolved by rolling back the deployment, after which all sites were confirmed to be fully operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-1a9c8bee0b
Is GitBook still down?
No, this incident was resolved 2026-03-06 14:36 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
0m, from 2026-03-06 16:56 UTC to 2026-03-06 14:36 UTC, by the times GitBook posted.
What caused it?
GitBook hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitBook's official status page, https://www.gitbookstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.