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 27 min ago. Last stored result reached it in 313 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 259 ms | 0 |
| Nov 7 | 0 | 0.0 | 271 ms | 0 |
| Nov 7 | 0 | 0.0 | 273 ms | 0 |
| Nov 7 | 0 | 0.0 | 276 ms | 0 |
| Nov 7 | 0 | 0.0 | 63 ms | 0 |
| Nov 8 | 0 | 0.0 | 211 ms | 0 |
| Nov 8 | 0 | 0.0 | 302 ms | 0 |
| Nov 8 | 0 | 0.0 | 207 ms | 0 |
| Nov 8 | 0 | 0.0 | 265 ms | 0 |
| Nov 9 | 0 | 0.0 | 284 ms | 0 |
| Nov 9 | 0 | 0.0 | 272 ms | 0 |
| Nov 9 | 0 | 0.0 | 76 ms | 0 |
| Nov 9 | 0 | 0.0 | 154 ms | 0 |
| Nov 10 | 0 | 0.0 | 174 ms | 0 |
| Nov 10 | 0 | 0.0 | 225 ms | 0 |
| Nov 10 | 0 | 0.0 | 352 ms | 0 |
| Nov 10 | 0 | 0.0 | 267 ms | 0 |
| Nov 11 | 0 | 0.0 | 154 ms | 0 |
| Nov 11 | 0 | 0.0 | 321 ms | 0 |
| Nov 11 | 0 | 0.0 | 261 ms | 0 |
| Nov 11 | 0 | 0.0 | 155 ms | 0 |
| Nov 12 | 0 | 0.0 | 295 ms | 0 |
| Nov 12 | 0 | 0.0 | 144 ms | 0 |
| Nov 12 | 0 | 0.0 | 175 ms | 0 |
| Nov 12 | 0 | 0.0 | 114 ms | 0 |
| Nov 13 | 0 | 0.0 | 269 ms | 0 |
| Nov 13 | 0 | 0.0 | 151 ms | 0 |
| Nov 13 | 0 | 0.0 | 290 ms | 0 |
| Nov 13 | 0 | 0.0 | 316 ms | 0 |
| Nov 14 | 0 | 0.0 | 313 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 9 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 270 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 9 days ago.
From our own checks: 100% over 9 days of checks.
270 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.