pingoru pingoru HungerRush had 17 outages in the last 2 years totaling 118h 33m of downtime, averaging 0.7 incidents per month.
There were 17 HungerRush outages since December 11, 2024 totaling 118h 33m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We are currently investigating an issue with credit card processing payments on WorldPay.
This incident has been resolved. Payment processing in the POS has been restored.
We have identified an issue related to intermittent Cloudflare connectivity that is causing payment processing errors for some customers attempting to run credit card payments. We are monitoring the situation and will provide updates as more information becomes available.
We have identified an issue related to intermittent Cloudflare connectivity that is causing payment processing errors for some customers attempting to run credit card payments. We are monitoring the situation and will provide updates as more information becomes available.
We are continuing to work on a fix for this issue.
The issue causing payment processing errors related to intermittent Cloudflare connectivity has been mostly resolved. We are continuing to monitor the situation and will provide updates as needed.
The issue causing payment processing errors related to intermittent Cloudflare connectivity has been resolved. If you continue to experience payment processing issues, please contact support.
We are aware of an issue preventing customers from accessing the Delivery Zones configuration page in RM/Hub. Affected pages may become stuck on a loading screen and fail to load. Our engineering team has identified the root cause and a fix is currently in review. We expect this to be resolved today and will update this page once deployed. We apologize for the inconvenience and appreciate your patience.
A fix has been implemented and we are monitoring the situation.
This incident has been resolved. Customers can now access the Delivery Zones configuration page in RM/Hub normally. Thank you for your patience.
We are currently experiencing an issue impacting our phone support system through Zendesk Talk. Customers may experience difficulty reaching Support by phone, longer hold times, or disconnected calls. Zendesk has confirmed an outage affecting our service pod, and their engineering teams are actively working toward resolution. We apologize for the inconvenience and will provide updates as more information becomes available.
We are currently experiencing an issue impacting our phone support system through Zendesk Talk. Customers may experience difficulty reaching Support by phone, longer hold times, or disconnected calls. Zendesk has confirmed an outage affecting our service pod, and their engineering teams are actively working toward resolution. We apologize for the inconvenience and will provide updates as more information becomes available.
This incident has been resolved.
We are actively monitoring an issue with Reports experiencing timeouts and errors. This is not isolated to a single report. Dashboard data in RM is also impacted. A 3rd party partner has acknowledged the service degradation and is actively remediating. We are seeing intermittent recovery with some regression. We will continue to monitor and provide updates as the situation develops.
Systems 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.
Platform Affected: ACH Processing - Settlement/Funding Issue: Worldpay is aware of an issue at the Federal Reserve that is delaying the expected delivery of funds for some merchants. Worldpay's technical teams are engaged with the Federal Reserve and are working to understand next steps. Status: Initial Impact: There is a potential for delayed funding. Actions Taken to Restore Service: Worldpay technical teams are continuing to reach out to the Federal Reserve for updates. All Worldpay systems are operating normally.
Platform 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: The Federal Reserve has confirmed that all outstanding files have been processed. Funding may be received at different times depending on the specific banking partner's processing schedule. Actions Taken to Restore Service: The Federal Reserve has resolved an internal issue to restore service and have processed all delayed files. All files were successfully submitted by Worldpay before their cutoff times. Worldpay will continue to monitor the environment for stability. Incident Resolved: 2026-03-03 19:42:00 UTC | 2026-03-03 14:42:00 EST
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are currently experiencing service disruptions due to an ongoing outage at Cloudflare, a leading provider of global infrastructure and security services that powers roughly 20% of the internet. This outage is impacting many organizations including ours. As a result, some of our services may be unavailable or degraded. We are actively monitoring the situation and will provide updates as Cloudflare works to resolve the issue.
Cloudflare has begun restoration and we are seeing some services begin to be operational. However, we expect some intermittent disruptions and will continue to monitor.
Service has been restored, although we do still see elevated error rates. We will continue to monitor until service is fully restored.
All services have been fully restored.
The AWS Outage affected one of our 3rd party providers whom while working on their own recovery caused an outage in our integrations rails. We deployed a hotfix to mitigate this 3rd party's outage.
We are currently investigating reports of credit card readers not processing transactions. This may prevent some customers from completing payments at the point of sale. Initial findings indicate that restarting the card reader resolves the issue in many cases, though some locations may require additional troubleshooting. Our teams are actively investigating the cause and working to ensure a full and stable resolution.
We are currently investigating reports of credit card readers not processing transactions. This may prevent some customers from completing payments at the point of sale. Initial findings indicate that restarting the card reader resolves the issue in many cases, though some locations may require additional troubleshooting. Our teams are actively investigating the cause and working to ensure a full and stable resolution.
We have confirmed an issue affecting Verifone credit card readers following a recent Windows update. Some locations may see errors such as “Datacap Configuration Not Found or Incorrect” or “Transaction Not Complete - NAK error from PIN Pad.” Our teams are working closely with partners to restore normal processing. In many cases, restarting the reader may provide a fix. If your card readers remain offline or display errors, please contact HungerRush Support for assistance. We will continue to provide updates as more information becomes available.
The issue affecting some Verifone credit card readers has been resolved. Datacap has confirmed the issue was caused by a recent Windows update that affected Verifone device drivers. Some systems displayed errors such as “Datacap Configuration Not Found or Incorrect” or “Transaction Not Complete - NAK error from PIN Pad.” Functionality has been restored, and no further incidents have been reported. All systems are operating normally, and this incident is now considered resolved.
We are currently experiencing an outage impacting our phone system due to an ongoing service disruption with our providers. While the IVR is operational, callers may hear a message indicating that no agents are available or experience long call queue times. Customers can continue to reach Support through ticket submission via the Support Portal at Support.HungerRush.com We will provide updates here as soon as more information is available.
Phone services are beginning to recover, and inbound calls are connecting successfully. We are continuing to monitor system stability as our providers complete recovery efforts. Thank you for your patience while we confirm full restoration. Customers can continue to reach Support through ticket submission via the Support Portal at Support.HungerRush.com
Phone Support Services are currently operational, and calls are connecting successfully. We continue to monitor system performance as stability improves following earlier disruptions related to our upstream provider. Customers may continue to reach Support through phone or the Support Portal at Support.HungerRush.com.
Phone services have been fully restored and are operating normally. Agents are able to assist, and calls are routing successfully. No further impact has been observed, and the issue is now considered resolved. We appreciate your patience while we worked through this disruption.
We have identified an issue with the HungerRush POS crashing on the CallerID Screen when an inbound call is received. This is related to updates to our loyalty system. A fix has been introduced and the issue should no longer be occurring. The fix should be rolled out automatically to all affected customers but if you are noticing issues please reach out to our Support Team.
The fix for the HungerRush POS crashing has been successfully implemented. If you are still having any issues, please reach out to our customer support team at 281-971-2500
Impact: During this period, some orders from DoorDash were not processed successfully. DoorDash temporarily deactivated HungerRush-connected stores in 15-minute intervals as a safeguard, which meant stores were unable to receive new DoorDash orders while deactivated. Root Cause: A HungerRush infrastructure change caused HungerRush to rate limit too aggressively under high order volume which in turn caused DoorDash to suspend order flow temporarily. Resolution: Engineering identified the mismatch and corrected the configuration in less than 90 minutes. Additional safeguards and monitoring have been implemented to prevent this type of issue from recurring.
DoorDash has detected an issue with Order Creation and Fulfillment. DoorDash has identified the issue and are working on mitigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have confirmed an issue with our telephony provider causing calls to drop. We are working with that provider and will post further information soon. In the meantime, please submit a ticket via our webform (https://support.menufy.com/hc/en-us/requests/new?ticket_form_id=15593323234189).
We are happy to report that the impact to the telephony product has been resolved working with our partner provider and all calls should be connecting as expcted at this time. Thank you for your patience during our investigation.
We are currently investigating this issue
This incident has been resolved.
We are currently investigating a Runtime Error appearing on the Admin screen of online ordering portal for some users.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of an issue that affected HungerRush services including 3rd party integrations, Honeycomb Loyalty, Reporting Data Sync, and Restaurant Management. The issue has been identified and should be resolved. If you are still encountering any issues, please reach out to our customer support team at 281–971-2500.