GitBook Outage History

GitBook is up right now

GitBook had 13 outages in the last 2 years totaling 53h 8m of downtime — averaging 0.5 incidents per month.

There were 13 GitBook outages since September 16, 2025 totaling 53h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.gitbookstatus.com

Minor June 25, 2026

GitBook webapp is returning 500

Detected by Pingoru
Jun 25, 2026, 01:08 PM UTC
Resolved
Jun 25, 2026, 01:08 PM UTC
Duration
—
Affected: GitBook App
Timeline · 4 updates
  1. identified Jun 25, 2026, 11:34 AM UTC

    Status: Identified A faulty SQL migration caused a corrupted deployment. Our team is working on a fix. Affected components GitBook App (Full outage)

  2. identified Jun 25, 2026, 12:29 PM UTC

    Status: Identified A fix is being deployed, we are monitoring the change. Affected components GitBook App (Full outage)

  3. monitoring Jun 25, 2026, 01:07 PM UTC

    Status: Monitoring A fix has been released, and we're monitoring it Affected components GitBook App (Operational)

  4. resolved Jun 25, 2026, 01:08 PM UTC

    Status: Resolved The incident has been resolved and systems are fully operational. Affected components GitBook App (Operational)

Read the full incident report →

Minor June 22, 2026

Sites are failing intermittently with 500 Internal Server Error

Detected by Pingoru
Jun 22, 2026, 04:14 PM UTC
Resolved
Jun 22, 2026, 04:14 PM UTC
Duration
—
Affected: Public Content
Timeline · 3 updates
  1. identified Jun 22, 2026, 02:58 PM UTC

    Status: Identified The issue affects some sites, resulting in Internal Server Error when visiting a site. We have identified a cause and expect to have a fix in near future. Not all sites are affected due to caching. Affected components Public Content (Partial outage)

  2. monitoring Jun 22, 2026, 03:21 PM UTC

    Status: Monitoring As part of the reorderable page actions last week we migrated pageActions into a new shape and removed old values. Our published content wasn't properly updated to no longer check the old values, and thus errored out because it was checking data that wasn't there (depending on what version of the customization object you were served, some sites were still using the old shape and thus functioned). We're mitigating by properly checking both data shapes for the foreseeable future, until all sites are completely using the new format. Affected components Public Content (Degraded performance)

  3. resolved Jun 22, 2026, 04:14 PM UTC

    Status: Resolved The fix released has solved the issue, all systems should be operational now. Affected components Public Content (Operational)

Read the full incident report →

Minor June 2, 2026

Increased API error rate

Detected by Pingoru
Jun 02, 2026, 04:09 PM UTC
Resolved
Jun 02, 2026, 04:09 PM UTC
Duration
—
Affected: GitBook App
Timeline · 3 updates
  1. investigating Jun 02, 2026, 02:40 PM UTC

    Status: Investigating We are investigating an increased error rate in our API. This only affects the GitBook app, and public content is working as expected. Affected components GitBook App (Partial outage)

  2. monitoring Jun 02, 2026, 03:32 PM UTC

    Status: Monitoring A fix has been deployed and the app and the API are responding normally. We are continuing to monitor the performance. Affected components GitBook App (Partial outage)

  3. resolved Jun 02, 2026, 04:09 PM UTC

    Status: Resolved The incident has been resolved, all systems have returned to normal. Affected components GitBook App (Operational)

Read the full incident report →

Minor May 8, 2026

Degraded database performance

Detected by Pingoru
May 08, 2026, 06:15 PM UTC
Resolved
May 08, 2026, 06:15 PM UTC
Duration
—
Affected: GitBook App
Timeline · 3 updates
  1. investigating May 08, 2026, 03:52 PM UTC

    Status: Investigating We are seeing a decrease in our database performance causing various actions in the app to hang. Our engineering team is investigating the root cause. Affected components GitBook App (Partial outage)

  2. monitoring May 08, 2026, 04:39 PM UTC

    Status: Monitoring A fix has been deployed, we are monitoring the performance. Affected components GitBook App (Partial outage)

  3. resolved May 08, 2026, 06:15 PM UTC

    Status: Resolved The fix has improved the performance back to their normal levels. Affected components GitBook App (Operational)

Read the full incident report →

Minor May 4, 2026

500 errors on some *.gitbook.io published sites

Detected by Pingoru
May 04, 2026, 02:00 PM UTC
Resolved
May 04, 2026, 02:00 PM UTC
Duration
—
Affected: Public Content
Timeline · 2 updates
  1. investigating May 04, 2026, 11:55 AM UTC

    Status: Investigating We’re currently investigating an issue affecting some published sites on *.gitbook.io Affected components Public Content (Partial outage)

  2. resolved May 04, 2026, 02:00 PM UTC

    Status: Resolved We issued a fix and have monitored the results of that fix. Pages are now loading at normal rates and our logs are looking healthy. Affected components Public Content (Operational)

Read the full incident report →

Minor April 16, 2026

Git Sync executions are delayed due to third-party outage

Detected by Pingoru
Apr 16, 2026, 04:56 AM UTC
Resolved
Apr 16, 2026, 04:56 AM UTC
Duration
—
Affected: GitBook App
Timeline · 2 updates
  1. 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)

  2. 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)

Read the full incident report →

Minor March 27, 2026

Degraded API performance

Detected by Pingoru
Mar 27, 2026, 06:47 PM UTC
Resolved
Mar 27, 2026, 06:47 PM UTC
Duration
—
Affected: GitBook App
Timeline · 4 updates
  1. investigating Mar 27, 2026, 02:43 PM UTC

    Status: Investigating We are currently experiencing a degradation in API performance causing various endpoints to hang. Affected components GitBook App (Partial outage)

  2. monitoring Mar 27, 2026, 02:55 PM UTC

    Status: Monitoring We have identified the issue and have mitigated it. We are currently monitoring the API and working on a root-cause fix. Affected components GitBook App (Operational)

  3. monitoring Mar 27, 2026, 04:48 PM UTC

    Status: Monitoring We have issued the root-cause fix and are monitoring the results. Affected components GitBook App (Operational)

  4. resolved Mar 27, 2026, 06:47 PM UTC

    Status: Resolved Indicators are pointing to a healthy state now after the fix. Everything should be operating well. Affected components GitBook App (Operational)

Read the full incident report →

Minor February 26, 2026

Site wide outage

Detected by Pingoru
Feb 26, 2026, 05:37 PM UTC
Resolved
Feb 26, 2026, 05:37 PM UTC
Duration
—
Affected: Public ContentGitBook App
Timeline · 3 updates
  1. identified Feb 26, 2026, 05:15 PM UTC

    Status: Identified GitBook is experiencing a downtime site wide. Both the GitBook app and published documentation are affected. Our team is working to revert the situation at this time. Affected components GitBook App (Full outage) Public Content (Partial outage)

  2. monitoring Feb 26, 2026, 05:19 PM UTC

    Status: Monitoring A fix has been deployed, and we are observing the situation going back to normal. Affected components GitBook App (Partial outage) Public Content (Partial outage)

  3. resolved Feb 26, 2026, 05:37 PM UTC

    Status: Resolved Both the application and published content have recovered fully after the fix was released and should be working as expected. Affected components GitBook App (Operational) Public Content (Operational)

Read the full incident report →