- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 14h 33m it lasted.
Anything that failed between 2026-10-28 09:15 UTC and 2026-10-28 23:48 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
Our API is responding slower than usual due to a known incident on Cloudflare. Any operations going through the affected region are slower or timing out. We are monitoring the incident closely. Cloudflare incident:
provider
- monitoring
We have routed parts of our API connection to other regions to improve stability while this gets fixed by Cloudflare. We continue to monitor the situation as it progresses.
provider
- resolved
The incident on Cloudflare is solved and our monitoring confirms that things are back 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-fc455749a2
Is GitBook still down?
No, this incident was resolved 2026-10-28 23:48 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
14h 33m, from 2026-10-28 09:15 UTC to 2026-10-28 23:48 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.