Restaurant365 incident

Reports of Slowness

Notice Resolved View vendor source →
Started
Apr 20, 2026, 04:02 PM UTC
Resolved
Apr 21, 2026, 12:10 PM UTC
Duration
20h 7m
Detected by Pingoru
Apr 20, 2026, 04:02 PM UTC

Affected components

Customer Databases

Update timeline

  1. investigating Apr 20, 2026, 04:02 PM UTC

    We are currently investigating reports of system slowness

  2. identified Apr 20, 2026, 05:32 PM UTC

    The root cause of the issue has been identified, and we are currently implementing a fix.

  3. monitoring Apr 20, 2026, 06:05 PM UTC

    A fix has been implemented and we will continue to monitor the results.

  4. monitoring Apr 20, 2026, 09:58 PM UTC

    We are continuing to actively monitor the results of the implemented fix.

  5. monitoring Apr 21, 2026, 01:58 AM UTC

    We are continuing to actively monitor the results of the implemented fix.

  6. resolved Apr 21, 2026, 12:10 PM UTC

    We are now marking this incident resolved with continued reports of recovery

Looking to track Restaurant365 downtime and outages?

Pingoru polls Restaurant365's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Restaurant365 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Restaurant365 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Restaurant365 for free

5 free monitors · No credit card required