Skip to main content
GitBook

Sites are failing intermittently with 500 Internal Server Error

Partial outage Lasted 1h 17m · started · GitBook's page

Level
confirmed
Worst impact
Partial outage
Down Index
28of 100

What to do

  • Check whether your product depends on GitBook. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 17m it lasted.

    Anything that failed between 2026-06-22 14:58 UTC and 2026-06-22 16:14 UTC may need a replay.
  • Subscribe to GitBook's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=gitbook works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitBook 3

  1. identified

    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.

    provider

  2. monitoring

    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.

    provider

  3. resolved

    The fix released has solved the issue, all systems should be operational now.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-14c6d949de

Is GitBook still down?

No, this incident was resolved 2026-06-22 16:14 UTC. For GitBook's live state, see https://down.guide/gitbook.

How long did it last?

1h 17m, from 2026-06-22 14:58 UTC to 2026-06-22 16:14 UTC, by the times GitBook posted.

What caused it?

GitBook hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitBook's official status page, https://www.gitbookstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.