User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 1 hr ago. Last stored result reached it in 166 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 160 ms | 0 |
| Nov 7 | 0 | 0.0 | 216 ms | 0 |
| Nov 8 | 0 | 0.0 | 131 ms | 0 |
| Nov 8 | 0 | 0.0 | 139 ms | 0 |
| Nov 8 | 0 | 0.0 | 151 ms | 0 |
| Nov 8 | 0 | 0.0 | 166 ms | 0 |
| Nov 9 | 0 | 0.0 | 161 ms | 0 |
| Nov 9 | 0 | 0.0 | 144 ms | 0 |
| Nov 9 | 0 | 0.0 | 156 ms | 0 |
| Nov 9 | 0 | 0.0 | 171 ms | 0 |
| Nov 10 | 0 | 0.0 | 176 ms | 0 |
| Nov 10 | 0 | 0.0 | 158 ms | 0 |
| Nov 10 | 0 | 0.0 | 139 ms | 0 |
| Nov 10 | 0 | 0.0 | 186 ms | 0 |
| Nov 11 | 0 | 0.0 | 159 ms | 0 |
| Nov 11 | 0 | 0.0 | 207 ms | 0 |
| Nov 11 | 0 | 0.0 | 201 ms | 0 |
| Nov 11 | 0 | 0.0 | 161 ms | 0 |
| Nov 12 | 0 | 0.0 | 188 ms | 0 |
| Nov 12 | 0 | 0.0 | 149 ms | 0 |
| Nov 12 | 0 | 0.0 | 196 ms | 0 |
| Nov 12 | 0 | 0.0 | 135 ms | 0 |
| Nov 13 | 0 | 0.0 | 174 ms | 0 |
| Nov 13 | 0 | 0.0 | 167 ms | 0 |
| Nov 13 | 0 | 0.0 | 128 ms | 0 |
| Nov 13 | 0 | 0.0 | 166 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Hunt 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 Hunt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Hunt alerts to Slack, Discord or a webhook — free.
Hunt is listed in our Cloud & developer category and checked at hunt.io. Explore the leading Threat Hunting Platform, discover active C2 servers, perform proactive infrastructure hunting and more.
Hunt publishes an official status page at status.hunt.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 148 ms average, 67–183 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 Hunt incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
148 ms on average over the last 24 hours (67–183 ms).
Yes, at https://status.hunt.io.
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 Hunt here at once, the problem is on Hunt'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 Hunt. 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.