GitBook Outage History

14 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live GitBook status99.53% uptime history

Every Recorded GitBook Incident

GitBook incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 17, 2026GitHub outage affecting Git SyncThe 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>7h 18mResolved
Jun 25, 2026GitBook webapp is returning 500The incident has been resolved and systems are fully operational.1h 33mResolved
Jun 22, 2026Sites are failing intermittently with 500 Internal Server ErrorThe fix released has solved the issue, all systems should be operational now.1h 16mResolved
Jun 2, 2026Increased API error rateThe incident has been resolved, all systems have returned to normal.1h 28mResolved
May 8, 2026Degraded database performanceThe fix has improved the performance back to their normal levels.2h 22mResolved
May 4, 2026500 errors on some *.gitbook.io published sitesWe issued a fix and have monitored the results of that fix. Pages are now loading at normal rates and our logs are looking healthy.2h 4mResolved
Apr 15, 2026Git Sync executions are delayed due to third-party outageThe 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…13h 22mResolved
Mar 27, 2026Degraded API performanceIndicators are pointing to a healthy state now after the fix. Everything should be operating well.4h 4mResolved
Mar 6, 2026Documentation sites with a custom domain returned a 404 errorBetween 14:36 and 14:43 UTC, all GitBook documentation sites using a custom domain were returning a 404 "Not Found" error, making documentation unavailable to users. The issue was caused by a problem introduced by an…-140 minResolved
Feb 26, 2026Site wide outageBoth the application and published content have recovered fully after the fix was released and should be working as expected.21 minResolved
Dec 5, 2025App and Public content failures due to Cloudflare outage[Cloudflare have resolved](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident and we have seen full recovery of public content and the app.59 minResolved
Nov 18, 2025Intermittent change request failuresCloudflare has [confirmed](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) that the incident has now been resolved, and we are seeing that change requests are working as expected.2h 51mResolved
Oct 20, 2025Public content not loading or taking longer to loadGitBook is back to normal and fully functional.22h 15mResolved
Sep 16, 2025All AI based features including GitBook Assistant or AI search are failing with "something went wrong"The issue was identified and fixed. All AI features are working as expected.27h 2mResolved

How to Read This GitBook Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GitBook acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single GitBook outage in this window ran 1d 3h, against a mean recovery of 6h 41m. If you depend on GitBook in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.