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 58 min ago. Last stored result reached it in 219 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 427 ms | 0 |
| Mon 23 | 0 | 0.0 | 232 ms | 0 |
| Tue 01 | 0 | 0.0 | 218 ms | 0 |
| Tue 03 | 0 | 0.0 | 242 ms | 0 |
| Tue 05 | 0 | 0.0 | 386 ms | 0 |
| Tue 07 | 0 | 0.0 | 305 ms | 0 |
| Tue 09 | 0 | 0.0 | 238 ms | 0 |
| Tue 12 | 0 | 0.0 | 347 ms | 0 |
| Tue 14 | 0 | 0.0 | 221 ms | 0 |
| Tue 16 | 0 | 0.0 | 266 ms | 0 |
| Tue 18 | 0 | 0.0 | 251 ms | 0 |
| Tue 21 | 0 | 0.0 | 345 ms | 0 |
| Tue 23 | 0 | 0.0 | 363 ms | 0 |
| Wed 01 | 0 | 0.0 | 205 ms | 0 |
| Wed 03 | 0 | 0.0 | 271 ms | 0 |
| Wed 06 | 0 | 0.0 | 298 ms | 0 |
| Wed 08 | 0 | 0.0 | 244 ms | 0 |
| Wed 10 | 0 | 0.0 | 404 ms | 0 |
| Wed 12 | 0 | 0.0 | 258 ms | 0 |
| Wed 14 | 0 | 0.0 | 355 ms | 0 |
| Wed 16 | 0 | 0.0 | 288 ms | 0 |
| Wed 19 | 0 | 0.0 | 274 ms | 0 |
| Wed 21 | 0 | 0.0 | 208 ms | 0 |
| Wed 23 | 0 | 0.0 | 339 ms | 0 |
| Thu 01 | 0 | 0.0 | 258 ms | 0 |
| Thu 03 | 0 | 0.0 | 155 ms | 0 |
| Thu 05 | 0 | 0.0 | 289 ms | 0 |
| Thu 07 | 0 | 0.0 | 381 ms | 0 |
| Thu 09 | 0 | 0.0 | 396 ms | 0 |
| Thu 11 | 0 | 0.0 | 265 ms | 0 |
| Thu 13 | 0 | 0.0 | 271 ms | 0 |
| Thu 16 | 0 | 0.0 | 355 ms | 0 |
| Thu 18 | 0 | 0.0 | 338 ms | 0 |
| Thu 20 | 0 | 0.0 | 283 ms | 0 |
| Thu 22 | 0 | 0.0 | 328 ms | 0 |
| Fri 00 | 0 | 0.0 | 189 ms | 0 |
| Fri 02 | 0 | 0.0 | 318 ms | 0 |
| Fri 04 | 0 | 0.0 | 223 ms | 0 |
| Fri 06 | 0 | 0.0 | 268 ms | 0 |
| Fri 08 | 0 | 0.0 | 178 ms | 0 |
| Fri 10 | 0 | 0.0 | 215 ms | 0 |
| Fri 11 | 0 | 0.0 | 267 ms | 0 |
| Fri 13 | 0 | 0.0 | 201 ms | 0 |
| Fri 15 | 0 | 0.0 | 231 ms | 0 |
| Fri 17 | 0 | 0.0 | 349 ms | 0 |
| Fri 19 | 0 | 0.0 | 254 ms | 0 |
| Fri 21 | 0 | 0.0 | 213 ms | 0 |
| Fri 23 | 0 | 0.0 | 219 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 8 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 246 ms average, 156–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 8 days ago.
From our own checks: 100% over 8 days of checks.
246 ms on average over the last 24 hours (156–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.