GitBook reported this critical-impact incident on its official status page on Nov 3, 2026, 05:16 UTC. It was resolved after 1d 6h.
Right now GitBook is operational. Live GitBook status →
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 customer data was accessible, how we responded to protect our customers, and what we’re doing next. We apologize again for the disruption. We hold ourselves to the highest standards, and we know an incident like this affects the trust you place in GitBook. We hope the transparency in this post-mortem, our previous communications, and the actions we’ve taken help rebuild it. If you have questions, contact your account manager or reply to this email to speak to our support team. For live updates, visit [status.gitbook.com](http://status.gitbook.com). **Sara Tandowsky, GitBook CEO** **Samy Pessé, GitBook Co-founder & CTO**
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 committed to being transparent about what happened and how we responded. We’ll share a full postmortem within the next 24 hours, including a timeline and details of the incident, our response, and the steps we’re taking to prevent similar incidents in the future. We apologize again for any disruption this incident has caused, and appreciate your patience and understanding.
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.
Both the GitBook App and public content should be online. We are continuing to monitor the situation. Further updates as they come.
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 investigation is still in progress. Once it’s complete, we’ll confirm whether any customer data was affected. You don’t need to do anything right now. If there are steps you need to take after services are restored, we’ll share them with you. We’ll also publish a full post-incident report when the investigation is complete. We’re sorry for the disruption, and thank you for your patience. If you have questions, please contact your account manager.
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.
Overlapping incidents aren't necessarily related.
GitBook reported 7 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 7h 18m. See GitBook's uptime and incident history