- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 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 1h 29m it lasted.
Anything that failed between 2026-06-02 14:40 UTC and 2026-06-02 16: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
We are investigating an increased error rate in our API. This only affects the GitBook app, and public content is working as expected.
provider
- monitoring
A fix has been deployed and the app and the API are responding normally. We are continuing to monitor the performance.
provider
- resolved
The incident has been resolved, all systems have returned to normal.
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-b958842217
Is GitBook still down?
No, this incident was resolved 2026-06-02 16:09 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
1h 29m, from 2026-06-02 14:40 UTC to 2026-06-02 16: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.