GitBook reported this major-impact incident on its official status page on Jun 22, 2026, 14:58 UTC. It was resolved after 1h 17m.
Right now GitBook is operational. Live GitBook status →
The fix released has solved the issue, all systems should be operational now.
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 what version of the customization object you were served, some sites were still using the old shape and thus functioned). We're mitigating by properly checking both data shapes for the foreseeable future, until all sites are completely using the new format.
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.
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.
Overlapping incidents aren't necessarily related.
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