GitBook reported this critical-impact incident on its official status page on Nov 3, 2026, 05:16 UTC. It has not been marked resolved yet.
Right now GitBook is operational. Live GitBook status →
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 6 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 7h 18m. See GitBook's uptime and incident history