- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 31of 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 4h 4m it lasted.
Anything that failed between 2026-03-27 14:43 UTC and 2026-03-27 18:47 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
- investigating
We are currently experiencing a degradation in API performance causing various endpoints to hang.
provider
- monitoring
We have identified the issue and have mitigated it. We are currently monitoring the API and working on a root-cause fix.
provider
- monitoring
We have issued the root-cause fix and are monitoring the results.
provider
- resolved
Indicators are pointing to a healthy state now after the fix. Everything should be operating well.
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-d15cdfcb5c
Is GitBook still down?
No, this incident was resolved 2026-03-27 18:47 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
4h 4m, from 2026-03-27 14:43 UTC to 2026-03-27 18:47 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.