- 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 13h 23m it lasted.
Anything that failed between 2026-04-15 15:34 UTC and 2026-04-16 04:56 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
- identified
Due to an outage in Inngest, Git Sync operations are being affected and are being delayed. We are monitoring changes closely. Inngest outage:
provider
- resolved
The Inngest incident causing Git Sync delays has been resolved. Everything should be back to normal! Please note that any syncs that didn't go through during the incident won't be retried automatically, so you'll need to push again to trigger a new sync. If you're still seeing any issues, reach out and we'll take a look!
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-3bcf24bae4
Is GitBook still down?
No, this incident was resolved 2026-04-16 04:56 UTC. For GitBook's live state, see https://down.guide/gitbook.
How long did it last?
13h 23m, from 2026-04-15 15:34 UTC to 2026-04-16 04:56 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.