Is GitBook Down?

No — GitBook is up

GitBook's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 164 ms

Right now

The verdict is the worse of these two. How we decide

GitBook's status page

gitbookstatus.com · read 1 minute ago · checked every 3 minutes

Operational

GitBook's components, as its status page reports them
Component	Status
GitBook App	Operational
Public Content	Operational
Homepage	Operational

Open their status page

FlareWarden checks

gitbook.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 164 ms
Checked: 2 hours ago

By region

Amsterdam reachable, 135 ms
Dallas reachable, 215 ms
Paris reachable, 100 ms
San Jose reachable, 189 ms
Singapore reachable, 62 ms
Stockholm reachable, 275 ms
Sydney reachable, 179 ms
Toronto reachable, 160 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	58 ms	3 ms	11 ms	113 ms
Dallas	49 ms	1 ms	8 ms	181 ms
Paris	23 ms	1 ms	9 ms	74 ms
San Jose	67 ms	2 ms	8 ms	155 ms
Singapore	8 ms	1 ms	10 ms	44 ms
Stockholm	142 ms	1 ms	12 ms	240 ms
Sydney	125 ms	1 ms	6 ms	158 ms
Toronto	51 ms	1 ms	8 ms	135 ms

We check that gitbook.com loads, not every feature behind it. Test it yourself

History

Incidents GitBook reported

Since Oct 22, 2 days · from gitbookstatus.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

GitBook website availability

Measured by FlareWarden · gitbook.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 242ms

Last 30 days

64-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of gitbook.com from multiple regions every 6 hours. GitBook's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 64 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What GitBook does

GitBook is a documentation platform where teams write, publish and maintain product docs and internal knowledge bases. It supports a docs-as-code workflow with Git sync alongside a web editor, and it publishes public sites for customer-facing documentation. Engineering and support teams depend on it, so an outage takes down the pages customers reach for when something else is already broken.

What an outage looks like

Published documentation sites return errors or fail to load for readers, which is the most visible symptom because those pages are public. The editor will not open spaces, or edits fail to save. Git sync stops mirroring changes between GitBook and the repository, so the two drift apart. Search inside a published site stops returning results while the pages themselves still render.

What to do about it

gitbookstatus.com tracks the GitBook App, Public Content and the Homepage as separate components, which distinguishes an authoring outage from one your readers can see. Public Content is the row that matters when customers report broken docs. If Git sync is affected, avoid forcing a re-sync during the incident, because conflicting writes are harder to unpick afterwards than a delay is.

Is it down for everyone, or just you?

If this page says GitBook is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

GitBook outage FAQ

My docs site is down but I can still edit. Which one is broken?

That split is expected, because GitBook tracks the App and Public Content as separate components. The editor working while published pages fail means authoring is healthy and delivery is not. Readers see the outage and you do not, so check the Public Content row rather than judging from the editor in front of you.

Will I lose edits made during an outage?

Edits that saved successfully are kept; the risk is work typed while the editor could not reach GitBook. Before closing the tab, copy anything substantial you wrote during the incident into a local file. Once the App component recovers, reopen the space and confirm your changes are present rather than assuming an autosave caught them.

Does a GitBook outage affect Git sync?

It can. Git sync moves content between GitBook and your repository, so an App outage can leave the two out of step until it clears. The usual outcome is a delay rather than lost content. Let it reconcile on its own once the incident ends instead of forcing a sync, which risks conflicting writes on both sides.

Can I still serve documentation while GitBook is down?

Only if you already keep a copy. Teams using the Git sync workflow have the Markdown in their own repository and can publish it elsewhere temporarily. Without that, published pages are unavailable until the Public Content component recovers. This is the practical argument for docs-as-code over editing only in the hosted editor.

How much downtime does GitBook actually have?

GitBook publishes rolling uptime per component. For the three months to August 2026 its status page showed 99.86 percent for the GitBook App, 99.98 percent for Public Content and 100 percent for the Homepage. Those figures put typical downtime in hours per quarter rather than days, and they show the App failing more often than the public pages readers see.

How we measure this

We request GitBook's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where GitBook publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of GitBook itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when GitBook goes down

We check GitBook every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required