- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 40of 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 33m it lasted.
Anything that failed between 2026-06-25 11:34 UTC and 2026-06-25 13:08 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 4
- identified
A faulty SQL migration caused a corrupted deployment. Our team is working on a fix.
provider
- identified
A fix is being deployed, we are monitoring the change.
provider
- monitoring
A fix has been released, and we're monitoring it
provider
- resolved
The incident has been resolved and systems are 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-ca7939c6de
Is GitBook still down?
No, this incident was resolved 2026-06-25 13:08 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
1h 33m, from 2026-06-25 11:34 UTC to 2026-06-25 13:08 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.