Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

US critical infrastructure monitor

GitBook

Cloud, identity and critical software · CA (headquarters)

Monitoring
From the provider's public status feed: last success Nov 6 17:05 UTC
Public findings
1
Provider status posts on record
20

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

A ConfirmedStatus: recovered

Redeployment with new secrets from 3 Nov 02:34Z; all existing API tokens invalidated and personal API tokens revoked; GitHub app keys rotated 10:52Z; all secrets rotated by 11:56Z; GitLab Git Sync tokens rotated 22:51Z. Customers told to rotate integration and third-party secrets. A dependent, Trade.xyz, publicly reported unauthorized activity on its GitBook-hosted docs (restored by 14:15Z 2 Nov) about four hours before GitBook's own 18:10Z alert.

Event: Nov 2
First public: Nov 2
Third-party report: Nov 2 15:22 UTC
Acknowledged: Nov 2

Other explanations considered: Customer-side account compromise unrelated to GitBook platform flaw.

  1. Nov 2 00:00 UTC · REC
    Trade.xyz found unauthorized activity on its GitBook-hosted documentation early 2 Nov, rolled docs back by 09:15 ET (14:15Z), told users not to click documentation links. Did not name GitBook as cause.
    Source
  2. Nov 2 12:27 UTC · DET
    Internal alert 2 Nov 18:10Z; investigation starts. Postmortem timeline: first hijacked account at targeted customer 12:27Z, staff sessions 16:32Z, production 17:48Z (dwell before alert about 22 min from production access, about 6 h from first account).
    Source
  3. Nov 2 20:32 UTC · CON
    SSO flaw fixed 19:58Z; compromised accounts disabled, attacker cut off and GitBook app taken offline 2 Nov 20:32Z. Authenticated docs offline; public content served from cache. Back office disabled.
    Source
  4. Nov 3 02:34 UTC · REM
    Redeployment with new secrets from 3 Nov 02:34Z; all existing API tokens invalidated and personal API tokens revoked; GitHub app keys rotated 10:52Z; all secrets rotated by 11:56Z; GitLab Git Sync tokens rotated 22:51Z. Customers told to rotate integration...
    Source
  5. Nov 3 11:56 UTC · REC
    Fully back online 3 Nov 11:56Z (about 15.5 h offline); 16:21 CET update says app, API and docs back with some degradation; incident declared resolved 4 Nov 11:36 CET (10:36Z), Git Sync still affected by an unrelated GitHub outage.
    Source
  6. Nov 4 19:30 UTC · DIS
    Postmortem published 4 Nov 20:30 CET (19:30Z) with IOCs, entry path (SSO login flaw allowing staff sessions), and statement that speed suggests heavy automation, possibly AI. Earlier notice said 'Action required: None' before being revised.
    Source

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

  • Git Sync affected by GitHub disruptionNov 4 10:15 UTC · resolved · major impact
    Service restricted or degradedRestoration reported
    1. Nov 4 10:15 UTC identified: GitHub has reported a disruption affecting Git operations, Pull Requests and Issues, which may cause Git sync failures or delays for connected GitHub repositories. You can follow updates on [GitHub’s status page](https://www.githubstatus.com/incidents/smtdswd1h2w4). We’ll also...
    2. Nov 4 12:03 UTC resolved: GitHub has [resolved](https://www.githubstatus.com/incidents/smtdswd1h2w4) the disruption, and Git Sync with GitHub is operating normally again. If you’re still experiencing issues, please contact our support team. Thank you for your patience.
  • Security incident impacting published sites and GitBook appNov 3 05:16 UTC · resolved · critical impact
    Service restricted or degradedProvider used security languageInvestigation mentionedRestoration reported
    1. Nov 3 05:16 UTC investigating: We’re currently experiencing downtime affecting published documentation sites and the GitBook editor. Our team is working to restore service, and we’ll share updates here. Sorry for the disruption.
    2. Nov 3 12:15 UTC monitoring: On November 2 we detected unauthorized access to parts of GitBook’s infrastructure. We contained it quickly and took some services offline as a precaution. Our team is now working to bring GitBook back online. We’ll post another update here within the next few hours. Our...
    3. Nov 3 12:32 UTC monitoring: Both the GitBook App and public content should be online. We are continuing to monitor the situation. Further updates as they come.
    4. Nov 3 14:58 UTC monitoring: We are aware of some specific issues affecting some customers related to published sites. A few services may still be degraded as we finish restoring everything to full performance. We continue to monitor the situation closely, and will provide updates.
    5. Nov 4 11:24 UTC resolved: Our team has monitored over night and we can confirm that this is now resolved. We sent communications over email to all customers with details on any actions that are needed. [You can also read more here](https://www.gitbook.com/status/security-incident-2026-11-03). We’re...
    6. Nov 4 19:49 UTC resolved: As promised, now that the incident is resolved, we’ve published our full post-mortem on the recent security incident. [**Read the full post-mortem**](https://www.gitbook.com/status/security-incident-2026-11-03) The post explains what happened, a full timeline, exactly which...
  • GitBook services unavailableNov 2 20:26 UTC · resolved · critical impact
    Service restricted or degradedSign-in disruptionInvestigation mentionedRestoration reported
    1. Nov 2 20:26 UTC identified: We’re currently investigating an issue affecting logging in to the GitBook app via SSO, as well as published sites that use authenticated access. Users may be unable to sign in, and visitors to authenticated sites may be unable to load content. Public sites are not affected and...
    2. Nov 3 03:37 UTC monitoring: The incident has now been mitigated and all published content, editing, and Git services are back up. We are continuing to monitor and will post a detailed post-mortem in the next 24 hours.
    3. Nov 3 03:40 UTC monitoring: Both app and public content components are operational.
    4. Nov 3 12:52 UTC resolved: This incident should be fully resolved. We are continuing our monitoring on the security incident more recently.
  • Git Sync causing missing page contentNov 2 13:56 UTC · resolved · major impact
    Investigation mentionedRestoration reported
    1. Nov 2 13:56 UTC investigating: We are investigating an issue where Git Sync operations can cause page content to become empty. Our team is working urgently to resolve this.
    2. Nov 2 15:32 UTC monitoring: Cause identified as a build tooling change that affected Git Sync. The change has been rolled back, so new Git Sync operations are no longer affected. Recovery of affected spaces started at 15:00 GMT.
    3. Nov 2 19:09 UTC resolved: This incident has been resolved. The build change that caused the Git Sync issue was rolled back, and Git Sync operations are now working normally. Affected spaces have been restored. If you still see missing or empty content in any space, please contact our support team at...
  • API operations are slower than usualOct 28 09:15 UTC · resolved · minor impact
    No classified wording
    1. Oct 28 09:15 UTC identified: Our API is responding slower than usual due to a known incident on Cloudflare. Any operations going through the affected region are slower or timing out. We are monitoring the incident closely. Cloudflare incident: <https://www.cloudflarestatus.com/incidents/snth5ero95rz>
    2. Oct 28 14:28 UTC monitoring: We have routed parts of our API connection to other regions to improve stability while this gets fixed by Cloudflare. We continue to monitor the situation as it progresses.
    3. Oct 29 08:48 UTC resolved: The incident on Cloudflare is solved and our monitoring confirms that things are back to normal.
  • App and published docs unavailableSep 5 18:56 UTC · resolved · critical impact
    Service restricted or degradedRestoration reported
    1. Sep 5 18:56 UTC monitoring: 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...
    2. Sep 5 19:00 UTC resolved: The incident is now fully resolved, all services are now up and stable.
  • GitHub outage affecting Git SyncAug 17 13:56 UTC · resolved · minor impact
    Service restricted or degradedRestoration reported
    1. Aug 17 13:56 UTC investigating: 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. Aug 17 21:14 UTC resolved: 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: <https://www.githubstatus.com/incidents/zkxwbgr0cnmx>
  • GitBook webapp is returning 500Jun 25 11:34 UTC · resolved · critical impact
    Restoration reported
    1. Jun 25 11:34 UTC identified: A faulty SQL migration caused a corrupted deployment. Our team is working on a fix.
    2. Jun 25 12:29 UTC identified: A fix is being deployed, we are monitoring the change.
    3. Jun 25 13:07 UTC monitoring: A fix has been released, and we're monitoring it
    4. Jun 25 13:08 UTC resolved: The incident has been resolved and systems are fully operational.
  • Sites are failing intermittently with 500 Internal Server ErrorJun 22 14:58 UTC · resolved · major impact
    No classified wording
    1. Jun 22 14:58 UTC 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.
    2. Jun 22 15:21 UTC 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...
    3. Jun 22 16:14 UTC resolved: The fix released has solved the issue, all systems should be operational now.
  • Increased API error rateJun 2 14:40 UTC · resolved · major impact
    Investigation mentionedRestoration reported
    1. Jun 2 14:40 UTC investigating: We are investigating an increased error rate in our API. This only affects the GitBook app, and public content is working as expected.
    2. Jun 2 15:32 UTC monitoring: A fix has been deployed and the app and the API are responding normally. We are continuing to monitor the performance.
    3. Jun 2 16:09 UTC resolved: The incident has been resolved, all systems have returned to normal.
  • Degraded database performanceMay 8 15:52 UTC · resolved · major impact
    Service restricted or degradedInvestigation mentioned
  • 500 errors on some *.gitbook.io published sitesMay 4 11:55 UTC · resolved · major impact
    Investigation mentioned
  • Git Sync executions are delayed due to third-party outageApr 15 15:34 UTC · resolved · major impact
    Service restricted or degradedRestoration reported
  • Degraded API performanceMar 27 14:43 UTC · resolved · major impact
    Service restricted or degraded
  • Documentation sites with a custom domain returned a 404 errorMar 6 16:56 UTC · resolved · major impact
    Service restricted or degradedRestoration reported
  • Site wide outageFeb 26 17:15 UTC · resolved · critical impact
    Service restricted or degradedRestoration reported
  • App and Public content failures due to Cloudflare outageDec 5 09:12 UTC · resolved · critical impact
    Service restricted or degradedRestoration reported
  • Intermittent change request failuresNov 18 12:55 UTC · resolved · minor impact
    Restoration reported
  • Public content not loading or taking longer to loadOct 20 09:16 UTC · resolved · major impact
    Service restricted or degraded
  • All AI based features including GitBook Assistant or AI search are failing with "something went wrong"Sep 16 07:07 UTC · resolved · major impact
    Investigation mentioned

Documented dependents

Organisations publicly documented as relying on this provider. A relationship is not an impact.

GitBook
verified (customer-wide revocation); hypothesized (Trade.xyz link)
  • All GitBook customers (API tokens invalidated, secrets rotation...No confirmed impact
  • one unnamed targeted customerNo confirmed impact
  • possibly Trade.xyzImpact reported publicly