GitBook outage: Site wide outage

1. resolvedFeb 26, 2026, 17:37 UTC

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

2. monitoringFeb 26, 2026, 17:19 UTC

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

3. identifiedFeb 26, 2026, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitBook's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors ratesMajor · Feb 25, 2026, 05:01 UTC
• Confluent Cloud: Network provisioning service in Azure East US region is degradedMajor · Feb 26, 2026, 13:59 UTC
• Cloudinary: Saved search fails for SMDs with spaces in name.Minor · Feb 26, 2026, 12:50 UTC

How often does GitBook have incidents?

GitBook reported 2 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 3h 42m. See GitBook's uptime and incident history