- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 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 7h 18m it lasted.
Anything that failed between 2026-08-17 13:56 UTC and 2026-08-17 21:14 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 2
- investigating
GitHub currently has an outage with a few components that Git Sync uses to sync your content to and from GitBook. This means that some operations might not work properly while this issue is ongoing. We'll keep this status updated as soon as we have more to share. GitHub's original status page for this incident:
provider
- resolved
The GitHub operations should be returning to normal as its service is back online. We’ll keep monitoring for any updates to the incident. GitHub Incident status:
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-aa049bec37
Is GitBook still down?
No, this incident was resolved 2026-08-17 21:14 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
7h 18m, from 2026-08-17 13:56 UTC to 2026-08-17 21:14 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.