User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
jazzhr.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 255 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:00 | 0 | 0.0 | 267 ms | 0 |
| 13:15 | 0 | 0.0 | 201 ms | 0 |
| 15:15 | 0 | 0.0 | 231 ms | 0 |
| 17:15 | 0 | 0.0 | 376 ms | 0 |
| 17:30 | 0 | 0.0 | 221 ms | 0 |
| 17:45 | 0 | 0.0 | 349 ms | 0 |
| 19:15 | 0 | 0.0 | 224 ms | 0 |
| 19:30 | 0 | 0.0 | 284 ms | 0 |
| 21:15 | 0 | 0.0 | 213 ms | 0 |
| 23:00 | 0 | 0.0 | 219 ms | 0 |
| 01:00 | 0 | 0.0 | 196 ms | 0 |
| 03:00 | 0 | 0.0 | 288 ms | 0 |
| 05:15 | 0 | 0.0 | 221 ms | 0 |
| 06:00 | 0 | 0.0 | 314 ms | 0 |
| 06:30 | 0 | 0.0 | 192 ms | 0 |
| 08:30 | 0 | 0.0 | 255 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for JazzHR 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 JazzHR goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send JazzHR alerts to Slack, Discord or a webhook — free.
JazzHR, at jazzhr.com, is one of the Cloud & developer services we monitor. JazzHR is powerful, user-friendly, and affordable recruiting software built to help small to medium-sized businesses hire smarter and faster.
JazzHR publishes an official status page at status.jazzhr.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 255 ms average, 192–376 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public JazzHR incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
255 ms on average over the last 24 hours (192–376 ms).
Yes, at https://status.jazzhr.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report JazzHR here at once, the problem is on JazzHR's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with JazzHR. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.