Is GitBook Public Content down?
Current GitBook Public Content status is UP

If GitBook Public Content is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when GitBook Public Content is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

GitBook Public Content posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitBook Public Content enters a pre-planned maintenance window, keeping you up to date.

GitBook Public Content does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate GitBook Public Content maintenance events into your unified calendar.

When GitBook Public Content posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When GitBook Public Content has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because GitBook Public Content has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.