Minor impactResolvedDevOps

GitBook incident: GitHub outage affecting Git Sync

GitBook reported this minor-impact incident on its official status page on Aug 17, 2026, 13:56 UTC. It was resolved after 7h 18m.

Right now GitBook is operational. Live GitBook status →

🔔 Get alerted when GitBook has issuesFree · email alerts · no credit card
Aug 17, 2026, 13:56 UTC
started
Aug 17, 2026, 21:14 UTC
resolved
7h 18m
duration
Minor
impact
  1. resolvedAug 17, 2026, 21:14 UTC

    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: <https://www.githubstatus.com/incidents/zkxwbgr0cnmx>

  2. investigatingAug 17, 2026, 13:56 UTC

    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: <https://www.githubstatus.com/incidents/zkxwbgr0cnmx>

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitBook's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitBook have incidents?

GitBook reported 2 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 3h 42m. See GitBook's uptime and incident history

GitBook incident on Aug 17, 2026: GitHub outage affecting Git Sync · APIStatus.watch