Damn, is it down?

All services / Cloud & developer

gitbook.com · Cloud & developer

Is GitBook down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Tests gitbook.com from your browser and compares it with our checks, the official status, and user reports.

Your browser → gitbook.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline

Press Run testNothing leaves your browser except a request to the site and to us.

Live outage map

No reports in the last 24 hours.

Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 38 ms · 1 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10149 ms13:4519:4501:4507:3013:30
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:0000.088 ms0
03:1500.059 ms0
03:3000.0100 ms0
03:4500.042 ms0
04:0000.098 ms0
04:1500.043 ms0
04:3000.083 ms0
04:4500.069 ms0
05:0000.097 ms0
05:1500.071 ms0
05:3000.0115 ms0
05:4500.060 ms0
06:0000.072 ms0
06:1500.062 ms0
06:3000.062 ms0
06:4500.092 ms0
07:0000.076 ms0
07:1500.0126 ms0
07:3000.0136 ms0
07:4500.026 ms0
08:0000.088 ms0
08:1500.072 ms0
08:3000.0134 ms0
08:4500.036 ms0
09:0000.043 ms0
09:1500.0114 ms0
09:3000.079 ms0
09:4500.068 ms0
10:0000.053 ms0
10:1500.090 ms0
10:3000.082 ms0
10:4500.075 ms0
11:0000.071 ms0
11:1500.058 ms0
11:3000.074 ms0
11:4500.075 ms0
12:0000.0107 ms0
12:1500.087 ms0
12:3000.056 ms0
12:4500.039 ms0
13:0000.058 ms0
13:1500.0149 ms0
13:3000.038 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

GitBook status badge Embed a live GitBook status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

GitBook status and 30-day uptime badge

Past outages

No outages on record for GitBook yet. Outages of 10 minutes or more get their own page here.

All GitBook outages · Every recent outage

Having trouble with GitBook?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is GitBook down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

GitBook not working for me but the status is fine. What now?

If GitBook is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on GitBook's side.

How does Damn is it down decide GitBook's status?

Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.

How often is GitBook checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.