Skip to main content
GitBook

Git Sync causing missing page content

Partial outage Lasted 5h 14m · started · GitBook's page

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 5h 14m it lasted.

    Anything that failed between 2026-11-02 13:56 UTC and 2026-11-02 19:09 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

  1. investigating

    We are investigating an issue where Git Sync operations can cause page content to become empty. Our team is working urgently to resolve this.

    provider

  2. monitoring

    Cause identified as a build tooling change that affected Git Sync. The change has been rolled back, so new Git Sync operations are no longer affected. Recovery of affected spaces started at 15:00 GMT.

    provider

  3. resolved

    This incident has been resolved. The build change that caused the Git Sync issue was rolled back, and Git Sync operations are now working normally. Affected spaces have been restored. If you still see missing or empty content in any space, please contact our support team at [support@gitbook.com](mailto:support@gitbook.com) and we will investigate promptly.

    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-84581500c4

Is GitBook still down?

No, this incident was resolved 2026-11-02 19:09 UTC. For GitBook's live state, see https://down.guide/gitbook.

How long did it last?

5h 14m, from 2026-11-02 13:56 UTC to 2026-11-02 19:09 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.