A GitBook code migration last week changed the shape of `pageActions` data, but the published content layer was not updated to handle the new format, causing intermittent 500 errors for some public sites over roughly 1.3 hours. Sites still served cached content using the old data shape were unaffected. The issue was resolved by updating the code to support both data shapes simultaneously until all sites fully transition to the new format.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with