User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
clojars.org · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests clojars.org from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 356 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 407 ms | 0 |
| 03:15 | 0 | 0.0 | 317 ms | 0 |
| 03:30 | 0 | 0.0 | 883 ms | 0 |
| 03:45 | 0 | 0.0 | 401 ms | 0 |
| 04:00 | 0 | 0.0 | 626 ms | 0 |
| 04:15 | 0 | 0.0 | 541 ms | 0 |
| 04:30 | 0 | 0.0 | 286 ms | 0 |
| 04:45 | 0 | 0.0 | 619 ms | 0 |
| 05:00 | 0 | 0.0 | 1039 ms | 0 |
| 05:15 | 0 | 0.0 | 334 ms | 0 |
| 05:30 | 0 | 0.0 | 424 ms | 0 |
| 05:45 | 0 | 0.0 | 317 ms | 0 |
| 06:00 | 0 | 0.0 | 746 ms | 0 |
| 06:15 | 0 | 0.0 | 372 ms | 0 |
| 06:30 | 0 | 0.0 | 293 ms | 0 |
| 06:45 | 0 | 0.0 | 389 ms | 0 |
| 07:00 | 0 | 0.0 | 731 ms | 0 |
| 07:15 | 0 | 0.0 | 340 ms | 0 |
| 07:30 | 0 | 0.0 | 412 ms | 0 |
| 07:45 | 0 | 0.0 | 375 ms | 0 |
| 08:00 | 0 | 0.0 | 384 ms | 0 |
| 08:15 | 0 | 0.0 | 620 ms | 0 |
| 08:30 | 0 | 0.0 | 559 ms | 0 |
| 08:45 | 0 | 0.0 | 1016 ms | 0 |
| 09:00 | 0 | 0.0 | 760 ms | 0 |
| 09:15 | 0 | 0.0 | 436 ms | 0 |
| 09:30 | 0 | 0.0 | 274 ms | 0 |
| 09:45 | 0 | 0.0 | 495 ms | 0 |
| 10:00 | 0 | 0.0 | 328 ms | 0 |
| 10:15 | 0 | 0.0 | 332 ms | 0 |
| 10:30 | 0 | 0.0 | 560 ms | 0 |
| 10:45 | 0 | 0.0 | 383 ms | 0 |
| 11:00 | 0 | 0.0 | 539 ms | 0 |
| 11:15 | 0 | 0.0 | 295 ms | 0 |
| 11:30 | 0 | 0.0 | 316 ms | 0 |
| 11:45 | 0 | 0.0 | 220 ms | 0 |
| 12:00 | 0 | 0.0 | 579 ms | 0 |
| 12:15 | 0 | 0.0 | 352 ms | 0 |
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.
No outages on record for Clojars yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Clojars goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clojars alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Clojars 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 Clojars's side.
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.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.