HungerRush Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded HungerRush Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 18, 2026 | WorldPay OutageThis incident has been resolved. Payment processing in the POS has been restored. | 1h 36m | Resolved |
| Sep 7, 2026 | Cloudflare Connectivity Issue Affecting Payment ProcessingThe issue causing payment processing errors related to intermittent Cloudflare connectivity has been resolved. If you continue to experience payment processing issues, please contact support. | 1h 48m | Resolved |
| Aug 20, 2026 | Delivery Zone Configuration Loading IssueThis incident has been resolved. Customers can now access the Delivery Zones configuration page in RM/Hub normally. Thank you for your patience. | 7h 23m | Resolved |
| May 13, 2026 | Phone Support Service DisruptionThis incident has been resolved. | 1h 18m | Resolved |
| Mar 12, 2026 | Reporting Timeouts & ErrorsSystems have stabilized and Reporting is operating at normal levels. Dashboard data in RM has also recovered. If you continue to experience any issues, please reach out to support. Thank you for your patience. | 5h 15m | Resolved |
| Mar 3, 2026 | Worldpay Funding DelaysPlatform Affected: ACH Processing - Settlement/Funding Issue: There was a third-party issue which may have caused a delay in the delivery of funding for transactions processed on 02-Mar-2026. Status: Final Impact… | 6h 11m | Resolved |
| Nov 18, 2025 | Cloudflare OutageAll services have been fully restored. | 4h 29m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next HungerRush incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This HungerRush Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before HungerRush acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single HungerRush outage in this window ran 7h 23m, against a mean recovery of 4h. If you depend on HungerRush in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.