Restaurant365 incident

Users experiencing "Request Failed" errors (HTTP 500) when creating or opening records

Minor Resolved View vendor source →

Restaurant365 experienced a minor incident on July 10, 2026 affecting Customer Databases and Classic and 1 more component, lasting 4h 5m. The incident has been resolved; the full update timeline is below.

Started
Jul 10, 2026, 04:11 PM UTC
Resolved
Jul 10, 2026, 08:16 PM UTC
Duration
4h 5m
Detected by Pingoru
Jul 10, 2026, 04:11 PM UTC

Affected components

Customer DatabasesClassicR365

Update timeline

  1. investigating Jul 10, 2026, 04:11 PM UTC

    We are currently investigating reports of "Request Failed" errors (HTTP 500) across several areas of the platform. Affected modules include Inventory, Invoices, Waste Logs, Purchase Orders, Till Management, and Commissary Orders. Users may encounter errors when creating new records, opening existing records, or saving and approving records. Impact varies by record type. Our team is actively investigating the root cause. We will provide an update as soon as more information is available.

  2. monitoring Jul 10, 2026, 04:31 PM UTC

    The issue causing "Request Failed" errors (HTTP 500) across Inventory, Invoices, Waste Logs, Purchase Orders, Till Management, and Commissary Orders has been resolved. We are continuing to monitor to confirm full stability. If you are still experiencing issues, please contact our support team.

  3. resolved Jul 10, 2026, 08:16 PM UTC

    This incident has been resolved.