GitBook outage: Git Sync executions are delayed due to third-party outage

1. resolvedApr 16, 2026, 04:56 UTC

   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!

2. identifiedApr 15, 2026, 15:34 UTC

   Due to an outage in Inngest, Git Sync operations are being affected and are being delayed. We are monitoring changes closely. Inngest outage: <https://status.inngest.com/incidents/01KP8H3NQM34K0RTB0BH7VNNMP>

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.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• 1Password: SSO sign-in failing on some attempts for some usersMajor · Apr 13, 2026, 17:24 UTC
• Mailgun: TLS Certificate Validation Errors for Clients Without SNIMajor · Apr 15, 2026, 13:40 UTC
• Datadog: Delayed MetricsMajor · Apr 15, 2026, 22:38 UTC
• LiveKit: Increased Latency in RoomService APIs, brief period of higher error rateMajor · Apr 15, 2026, 23:23 UTC
• Inngest: Delays in function run schedulingMinor · Apr 15, 2026, 12:15 UTC
• Intercom: Fin is experiencing issuesMinor · Apr 15, 2026, 16:57 UTC
• ReadMe: Slow page performanceMinor · Apr 15, 2026, 17:18 UTC
• Amplitude: Event Streaming DelayMinor · Apr 15, 2026, 23:09 UTC

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