- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 100
What to do
Check whether your product depends on GitBook. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 3h it lasted.
Anything that failed between 2025-09-16 07:07 UTC and 2025-09-17 10:09 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 3
- investigating
This means that you cannot use AI search, GitBook Assistant or any other AI based features at this moment. Our team is investigating.
provider
- identified
We have issued a temporary fix, and the AI features should be working as expected. Our team is still investigating to fix the underlying issue.
provider
- resolved
The issue was identified and fixed. All AI features are working as expected.
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-020b197ff4
Is GitBook still down?
No, this incident was resolved 2025-09-17 10:09 UTC. For GitBook's live state, see https://down.guide/providers/gitbook.
How long did it last?
1d 3h, from 2025-09-16 07:07 UTC to 2025-09-17 10:09 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.