- Level
- confirmed
- Worst impact
- Major outage
- Down Index
- 37of 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 21m it lasted.
Anything that failed between 2026-02-26 17:15 UTC and 2026-02-26 17:37 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
- identified
GitBook is experiencing a downtime site wide. Both the GitBook app and published documentation are affected. Our team is working to revert the situation at this time.
provider
- monitoring
A fix has been deployed, and we are observing the situation going back to normal.
provider
- resolved
Both the application and published content have recovered fully after the fix was released and should be 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-2b61b0be90
Is GitBook still down?
No, this incident was resolved 2026-02-26 17:37 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
21m, from 2026-02-26 17:15 UTC to 2026-02-26 17:37 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.