Service comparison
Clojars vs. Gitbook
Clojars vs. Gitbook — reliability, API availability, and incident frequency head-to-head.
Last 90 days · 4 incidents total · Data via Pulsetic monitoring
Service comparison
Clojars vs. Gitbook — reliability, API availability, and incident frequency head-to-head.
Last 90 days · 4 incidents total · Data via Pulsetic monitoring
Head-to-head
Clojars
clojars.org
90-day uptime
100.00%
Incidents (90d)
0
0 major · 0 minor
Median resolution
—
Longest outage
—
Gitbook
gitbookstatus.com
90-day uptime
99.53%
Incidents (90d)
4
3 major · 1 minor
Median resolution
1h 24m
Longest outage
7h 18m
Uptime over time
| Window | Clojars | Gitbook | Δ |
|---|---|---|---|
| Last 24 hours |
|
|
0.00 pp |
| Last 7 days |
|
|
0.00 pp |
| Last 30 days |
|
|
+0.01 pp |
| Last 90 days |
|
|
+0.47 pp |
Δ is percentage-point difference (Clojars minus Gitbook). Higher is better.
Incidents 90-day
Clojars
0 total
Median resolution
—
Longest outage
—
Gitbook
4 total
Median resolution
1h 24m
Longest outage
7h 18m
Recent activity
Clojars
Major outage caused by DDoS at Linode Atlanta
3d 5h 55m
Upstream network outage at Linode
2h 3m
Clojars unavailable
23m
Linode network outages
3h 7m
Upstream network maintenance
5m
Gitbook
App and published docs unavailable
4m
GitHub outage affecting Git Sync
7h 18m
GitBook webapp is returning 500
1h 33m
Sites are failing intermittently with 500 Internal Server Error
1h 16m
Increased API error rate
1h 28m
Bottom line
Clojars winsClojars posted 100.00% vs. 99.53% for Gitbook (Δ +0.47 pp). Incidents: 0 vs. 4 (-4).
Pulsetic is website uptime monitoring. Every number on this page came from its checks. Aim one at a website you run and build a 90-day record.
10 monitors free, email alerts on failure and recovery. No credit card.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.