- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 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 22h 16m it lasted.
Anything that failed between 2025-10-20 09:16 UTC and 2025-10-21 07:31 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
We are aware of issues in loading public content in GitBook. Our team has identified the issue, and it's related to an issue in AWS, currently affecting several upstream providers. More details on the AWS outage here: https://health.aws.amazon.com/health/status Our team is looking into mitigation options.
provider
- monitoring
We are seeing improvements in loading times and performance overall following updates on AWS' outage. We continue to monitor the performance.
provider
- resolved
GitBook is back to normal and fully functional.
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-1881d7efc0
Is GitBook still down?
No, this incident was resolved 2025-10-21 07:31 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
22h 16m, from 2025-10-20 09:16 UTC to 2025-10-21 07:31 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.