Is GitBook Down?

PulsAPI checks GitBook every 60 seconds. The verdict at the top of this page comes from the latest poll of the official GitBook status feed and refreshes automatically, so you are not looking at a stale cached answer.

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until GitBook recovers.

PulsAPI tracks GitBook uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.80%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for GitBook.

PulsAPI polls the official GitBook status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Yes. PulsAPI monitors 3 individual GitBook components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Yes. Create a PulsAPI account and subscribe to GitBook. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever GitBook status changes.

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot GitBook problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Yes. PulsAPI's Starter plan is free forever and covers up to 5 monitored services with email alerts, so GitBook plus four more costs nothing. Every new account also gets a 30-day Business trial — unlimited monitors, Slack alerts, SLA reporting — with no credit card.