GitBook

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-05 18:56 UTC

   Our database provider is experiencing a partial outage, affecting availability of the GitBook application and published documentation sites. It appears to be mitigated and the GitBook app and published docs are available again. We are continuing to monitor for stability and will...

2. resolved 2026-09-05 19:00 UTC

   The incident is now fully resolved, all services are now up and stable.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. investigating 2026-08-17 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...

2. resolved 2026-08-17 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:

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-25 11:34 UTC

   A faulty SQL migration caused a corrupted deployment. Our team is working on a fix.

2. identified 2026-06-25 12:29 UTC

   A fix is being deployed, we are monitoring the change.

3. monitoring 2026-06-25 13:07 UTC

   A fix has been released, and we're monitoring it

4. resolved 2026-06-25 13:08 UTC

   The incident has been resolved and systems are fully operational.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-22 14:58 UTC

   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.

2. monitoring 2026-06-22 15:21 UTC

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

3. resolved 2026-06-22 16:14 UTC

   The fix released has solved the issue, all systems should be operational now.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 14:40 UTC

   We are investigating an increased error rate in our API. This only affects the GitBook app, and public content is working as expected.

2. monitoring 2026-06-02 15:32 UTC

   A fix has been deployed and the app and the API are responding normally. We are continuing to monitor the performance.

3. resolved 2026-06-02 16:09 UTC

   The incident has been resolved, all systems have returned to normal.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-08 15:52 UTC

   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.

2. monitoring 2026-05-08 16:39 UTC

   A fix has been deployed, we are monitoring the performance.

3. resolved 2026-05-08 18:15 UTC

   The fix has improved the performance back to their normal levels.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-04 11:55 UTC

   We’re currently investigating an issue affecting some published sites on `*.gitbook.io`

2. resolved 2026-05-04 14:00 UTC

   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.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-04-15 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:

2. resolved 2026-04-16 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...

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-27 14:43 UTC

   We are currently experiencing a degradation in API performance causing various endpoints to hang.

2. monitoring 2026-03-27 14:55 UTC

   We have identified the issue and have mitigated it. We are currently monitoring the API and working on a root-cause fix.

3. monitoring 2026-03-27 16:48 UTC

   We have issued the root-cause fix and are monitoring the results.

4. resolved 2026-03-27 18:47 UTC

   Indicators are pointing to a healthy state now after the fix. Everything should be operating well.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-06 14:36 UTC

   Between 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 upstream provider that affected our deployment. The incident...

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-26 17:15 UTC

   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.

2. monitoring 2026-02-26 17:19 UTC

   A fix has been deployed, and we are observing the situation going back to normal.

3. resolved 2026-02-26 17:37 UTC

   Both the application and published content have recovered fully after the fix was released and should be working as expected.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-12-05 09:12 UTC

   We are aware of issues loading public content and the GitBook app. The issue is related to a Cloudflare outage. More information on the incident can be found [here](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q).

2. monitoring 2025-12-05 09:32 UTC

   Cloudflare has implemented a [fix for the issue](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q). Public content and the GitBook app are back.

3. resolved 2025-12-05 10:12 UTC

   [Cloudflare have resolved](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident and we have seen full recovery of public content and the app.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2025-11-18 12:55 UTC

   We've identified an ongoing incident with Cloudflare, who have updated their status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). This is impacting change requests, where creating new requests or merging existing ones is working intermittently.

2. monitoring 2025-11-18 13:26 UTC

   We are still monitoring the current incident. Cloudflare has identified and is resolving the issue, and has updated its status page [here](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7).

3. resolved 2025-11-18 15:46 UTC

   Cloudflare 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.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 09:16 UTC

   We are aware of issues in loading public content in GitBook. Our team has identified the issue, and it's related to an issue in AWS, currently affecting several upstream providers. More details on the AWS outage here: https://health.aws.amazon.com/health/status Our team is...

2. monitoring 2025-10-20 10:55 UTC

   We are seeing improvements in loading times and performance overall following updates on AWS' outage. We continue to monitor the performance.

3. resolved 2025-10-21 07:31 UTC

   GitBook is back to normal and fully functional.

Excerpts are shortened. Read the full incident on GitBook's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-16 07:07 UTC

   This means that you cannot use AI search, GitBook Assistant or any other AI based features at this moment. Our team is investigating.

2. identified 2025-09-16 12:36 UTC

   We have issued a temporary fix, and the AI features should be working as expected. Our team is still investigating to fix the underlying issue.

3. resolved 2025-09-17 10:09 UTC

   The issue was identified and fixed. All AI features are working as expected.

Excerpts are shortened. Read the full incident on GitBook's status page.