User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Food
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 316 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 327 ms | 0 |
| Mon 22 | 0 | 0.0 | 154 ms | 0 |
| Tue 01 | 0 | 0.0 | 174 ms | 0 |
| Tue 03 | 0 | 0.0 | 286 ms | 0 |
| Tue 05 | 0 | 0.0 | 66 ms | 0 |
| Tue 07 | 0 | 0.0 | 160 ms | 0 |
| Tue 09 | 0 | 0.0 | 328 ms | 0 |
| Tue 11 | 0 | 0.0 | 180 ms | 0 |
| Tue 13 | 0 | 0.0 | 385 ms | 0 |
| Tue 16 | 0 | 0.0 | 318 ms | 0 |
| Tue 18 | 0 | 0.0 | 174 ms | 0 |
| Tue 20 | 0 | 0.0 | 291 ms | 0 |
| Tue 22 | 0 | 0.0 | 273 ms | 0 |
| Wed 01 | 0 | 0.0 | 155 ms | 0 |
| Wed 03 | 0 | 0.0 | 74 ms | 0 |
| Wed 05 | 0 | 0.0 | 154 ms | 0 |
| Wed 07 | 0 | 0.0 | 263 ms | 0 |
| Wed 10 | 0 | 0.0 | 379 ms | 0 |
| Wed 12 | 0 | 0.0 | 177 ms | 0 |
| Wed 14 | 0 | 0.0 | 276 ms | 0 |
| Wed 16 | 0 | 0.0 | 261 ms | 0 |
| Wed 18 | 0 | 0.0 | 93 ms | 0 |
| Wed 20 | 0 | 0.0 | 178 ms | 0 |
| Wed 23 | 0 | 0.0 | 204 ms | 0 |
| Thu 01 | 0 | 0.0 | 294 ms | 0 |
| Thu 03 | 0 | 0.0 | 308 ms | 0 |
| Thu 05 | 0 | 0.0 | 295 ms | 0 |
| Thu 07 | 0 | 0.0 | 144 ms | 0 |
| Thu 09 | 0 | 0.0 | 304 ms | 0 |
| Thu 11 | 0 | 0.0 | 136 ms | 0 |
| Thu 13 | 0 | 0.0 | 68 ms | 0 |
| Thu 15 | 0 | 0.0 | 277 ms | 0 |
| Thu 17 | 0 | 0.0 | 175 ms | 0 |
| Thu 19 | 0 | 0.0 | 113 ms | 0 |
| Thu 21 | 0 | 0.0 | 114 ms | 0 |
| Thu 23 | 0 | 0.0 | 200 ms | 0 |
| Fri 01 | 0 | 0.0 | 133 ms | 0 |
| Fri 03 | 0 | 0.0 | 289 ms | 0 |
| Fri 05 | 0 | 0.0 | 269 ms | 0 |
| Fri 07 | 0 | 0.0 | 151 ms | 0 |
| Fri 09 | 0 | 0.0 | 108 ms | 0 |
| Fri 11 | 0 | 0.0 | 275 ms | 0 |
| Fri 13 | 0 | 0.0 | 266 ms | 0 |
| Fri 15 | 0 | 0.0 | 290 ms | 0 |
| Fri 17 | 0 | 0.0 | 325 ms | 0 |
| Fri 19 | 0 | 0.0 | 330 ms | 0 |
| Fri 21 | 0 | 0.0 | 302 ms | 0 |
| Fri 23 | 0 | 0.0 | 316 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 HungerRush 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 HungerRush goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send HungerRush alerts to Slack, Discord or a webhook — free.
HungerRush, at hungerrush.com, is one of the Food services we monitor. The all-in-one restaurant platform built for pizza and delivery operators: POS, ordering, delivery, marketing, and reporting in one system.
HungerRush publishes an official status page at status.hungerrush.com; when we can read it, its incident level is folded into the status shown here.
Common problems for food services: ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times.
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: 255 ms average, 108–330 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public HungerRush incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
255 ms on average over the last 24 hours (108–330 ms).
Yes, at https://status.hungerrush.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For food services, watch for ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times. If many people report HungerRush here at once, the problem is on HungerRush'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 HungerRush. 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.