GitBook outage: Documentation sites with a custom domain returned a 404 error

1. resolvedMar 6, 2026, 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 was resolved by rolling back the deployment, after which all sites were confirmed to be fully operational.

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.

• Snowflake: AWS - Middle East (UAE): INC0152681Critical · Mar 1, 2026, 13:33 UTC
• Smartsheet: Brandfolder Monthly Reports DelayedMajor · Feb 27, 2026, 21:55 UTC
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Major · Mar 1, 2026, 19:30 UTC
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Mar 2, 2026, 07:19 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