Restaurant365 experienced a notice incident on January 12, 2026 affecting Customer Databases and Ad Hoc and 1 more component, lasting 2d 18h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 12, 2026, 06:58 PM UTC
We are currently investigating reports of intermittent slowness within customer instances
- monitoring Jan 12, 2026, 07:43 PM UTC
A fix has been implemented and we are seeing recovery for both the reported slowness and delayed reporting. We will continue to monitor the fix implemented before fully resolving the incident.
- monitoring Jan 12, 2026, 07:52 PM UTC
While we continue to see reports of recovery, we will continue to monitor the fix implemented with databases being fully operational.
- monitoring Jan 12, 2026, 10:30 PM UTC
We are continuing to monitor the fix that was implemented and are seeing signs of recovery.
- monitoring Jan 13, 2026, 02:13 PM UTC
We are continuing our efforts to monitor the fix that was implemented and seeing signs of full recovery.
- monitoring Jan 13, 2026, 05:01 PM UTC
We are aware of additional reports of slowness and are continuing to investigate the root cause and assess impact.
- monitoring Jan 13, 2026, 05:02 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jan 13, 2026, 06:08 PM UTC
As part of our ongoing investigation, we will be temporarily pausing intraday polling. Customers should expect a delay in intraday polling for approximately 45 minutes
- monitoring Jan 13, 2026, 07:15 PM UTC
Intraday polling has resumed and is no longer paused. We are actively investigating reports of slowness and closely monitoring system performance to ensure stability.
- monitoring Jan 13, 2026, 10:49 PM UTC
We will continue to monitor the fixes that have been implemented and closely observe system performance. The status page will remain in a monitoring state through tomorrow while we ensure continued stability.
- monitoring Jan 14, 2026, 03:52 PM UTC
We are actively monitoring the implemented fix and continuing our investigation to ensure system stability.
- monitoring Jan 14, 2026, 11:36 PM UTC
We are actively monitoring the implemented fix and continuing our investigation to ensure system stability.
- resolved Jan 15, 2026, 01:54 PM UTC
Based on continued recovery reports, we can confirm the issue has been resolved.