GitBook incident
Git Sync executions are delayed due to third-party outage
Affected components
Update timeline
- identified Apr 15, 2026, 03:34 PM UTC
Status: Identified 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 Affected components GitBook App (Partial outage)
- resolved Apr 16, 2026, 04:56 AM UTC
Status: 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! Affected components GitBook App (Operational)
Looking to track GitBook downtime and outages?
Pingoru polls GitBook's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when GitBook reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track GitBook alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required