User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 37 min ago. Last stored result reached it in 128 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 302 ms | 0 |
| Mon 20 | 0 | 0.0 | 304 ms | 0 |
| Mon 22 | 0 | 0.0 | 178 ms | 0 |
| Tue 00 | 0 | 0.0 | 117 ms | 0 |
| Tue 02 | 0 | 0.0 | 310 ms | 0 |
| Tue 04 | 0 | 0.0 | 59 ms | 0 |
| Tue 06 | 0 | 0.0 | 142 ms | 0 |
| Tue 08 | 0 | 0.0 | 100 ms | 0 |
| Tue 10 | 0 | 0.0 | 137 ms | 0 |
| Tue 12 | 0 | 0.0 | 224 ms | 0 |
| Tue 15 | 0 | 0.0 | 96 ms | 0 |
| Tue 17 | 0 | 0.0 | 222 ms | 0 |
| Tue 19 | 0 | 0.0 | 187 ms | 0 |
| Tue 21 | 0 | 0.0 | 152 ms | 0 |
| Wed 00 | 0 | 0.0 | 134 ms | 0 |
| Wed 02 | 0 | 0.0 | 107 ms | 0 |
| Wed 04 | 0 | 0.0 | 135 ms | 0 |
| Wed 06 | 0 | 0.0 | 119 ms | 0 |
| Wed 09 | 0 | 0.0 | 52 ms | 0 |
| Wed 11 | 0 | 0.0 | 79 ms | 0 |
| Wed 13 | 0 | 0.0 | 112 ms | 0 |
| Wed 15 | 0 | 0.0 | 153 ms | 0 |
| Wed 17 | 0 | 0.0 | 111 ms | 0 |
| Wed 20 | 0 | 0.0 | 105 ms | 0 |
| Wed 22 | 0 | 0.0 | 84 ms | 0 |
| Thu 00 | 0 | 0.0 | 128 ms | 0 |
| Thu 01 | 0 | 0.0 | 61 ms | 0 |
| Thu 03 | 0 | 0.0 | 86 ms | 0 |
| Thu 05 | 0 | 0.0 | 99 ms | 0 |
| Thu 07 | 0 | 0.0 | 104 ms | 0 |
| Thu 09 | 0 | 0.0 | 84 ms | 0 |
| Thu 11 | 0 | 0.0 | 123 ms | 0 |
| Thu 13 | 0 | 0.0 | 109 ms | 0 |
| Thu 15 | 0 | 0.0 | 385 ms | 0 |
| Thu 18 | 0 | 0.0 | 203 ms | 0 |
| Thu 20 | 0 | 0.0 | 74 ms | 0 |
| Thu 22 | 0 | 0.0 | 52 ms | 0 |
| Fri 00 | 0 | 0.0 | 107 ms | 0 |
| Fri 02 | 0 | 0.0 | 133 ms | 0 |
| Fri 04 | 0 | 0.0 | 120 ms | 0 |
| Fri 06 | 0 | 0.0 | 48 ms | 0 |
| Fri 08 | 0 | 0.0 | 250 ms | 0 |
| Fri 10 | 0 | 0.0 | 31 ms | 0 |
| Fri 11 | 0 | 0.0 | 140 ms | 0 |
| Fri 12 | 0 | 0.0 | 217 ms | 0 |
| Fri 14 | 0 | 0.0 | 231 ms | 0 |
| Fri 16 | 0 | 0.0 | 112 ms | 0 |
| Fri 18 | 0 | 0.0 | 128 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 hh2 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 hh2 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send hh2 alerts to Slack, Discord or a webhook — free.
hh2, at hh2.com, is one of the AI services we monitor. AI-powered construction HR, payroll, time tracking, and AP software built for contractors. Connect your field and office on one platform that syncs to your ERP.
hh2 publishes an official status page at status.hh2.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 120 ms average, 19–250 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public hh2 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
120 ms on average over the last 24 hours (19–250 ms).
Yes, at https://status.hh2.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report hh2 here at once, the problem is on hh2'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 hh2. 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.