User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
hypernode.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests hypernode.com 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 1193 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 1444 ms | 0 |
| 03:15 | 0 | 0.0 | 484 ms | 0 |
| 03:30 | 0 | 0.0 | 1208 ms | 0 |
| 03:45 | 0 | 0.0 | 823 ms | 0 |
| 04:00 | 0 | 0.0 | 646 ms | 0 |
| 04:15 | 0 | 0.0 | 2276 ms | 0 |
| 04:30 | 0 | 0.0 | 1749 ms | 0 |
| 04:45 | 0 | 0.0 | 712 ms | 0 |
| 05:00 | 0 | 0.0 | 951 ms | 0 |
| 05:15 | 0 | 0.0 | 808 ms | 0 |
| 05:30 | 0 | 0.0 | 1420 ms | 0 |
| 05:45 | 0 | 0.0 | 1412 ms | 0 |
| 06:00 | 0 | 0.0 | 1584 ms | 0 |
| 06:15 | 0 | 0.0 | 498 ms | 0 |
| 06:30 | 0 | 0.0 | 951 ms | 0 |
| 06:45 | 0 | 0.0 | 1060 ms | 0 |
| 07:00 | 0 | 0.0 | 685 ms | 0 |
| 07:15 | 0 | 0.0 | 674 ms | 0 |
| 07:30 | 0 | 0.0 | 1267 ms | 0 |
| 07:45 | 0 | 0.0 | 543 ms | 0 |
| 08:00 | 0 | 0.0 | 1482 ms | 0 |
| 08:15 | 0 | 0.0 | 847 ms | 0 |
| 08:30 | 0 | 0.0 | 1527 ms | 0 |
| 08:45 | 0 | 0.0 | 2063 ms | 0 |
| 09:00 | 0 | 0.0 | 720 ms | 0 |
| 09:15 | 0 | 0.0 | 1388 ms | 0 |
| 09:30 | 0 | 0.0 | 945 ms | 0 |
| 09:45 | 0 | 0.0 | 1235 ms | 0 |
| 10:00 | 0 | 0.0 | 556 ms | 0 |
| 10:15 | 0 | 0.0 | 1049 ms | 0 |
| 10:30 | 0 | 0.0 | 987 ms | 0 |
| 10:45 | 0 | 0.0 | 1132 ms | 0 |
| 11:00 | 0 | 0.0 | 908 ms | 0 |
| 11:15 | 0 | 0.0 | 607 ms | 0 |
| 11:30 | 0 | 0.0 | 509 ms | 0 |
| 11:45 | 0 | 0.0 | 1645 ms | 0 |
| 12:00 | 0 | 0.0 | 1432 ms | 0 |
| 12:15 | 0 | 0.0 | 1193 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 Hypernode 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 Hypernode goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Hypernode 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 Hypernode 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 Hypernode'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.