Live / Restaurant365 / Incident
Restaurant365: Delayed DSS Imports
Restaurant365 · restaurant365.comMinor incidentResolved2026-10-05 16:29 UTC
Public — what happened
Summary
Restaurant365 reported delays affecting some DSS imports beginning at 13:08 UTC on October 5, 2026, and rated the issue as minor. By 14:05 UTC, the company said it had found the underlying cause and rolled out a fix, after which the delayed imports were expected to start coming through. Restaurant365 then watched for remaining problems as service recovered, and marked the incident resolved at 16:29 the same day.
Affected
POS Integrations (DSS Polling)
Timeline
- Started — 2026-10-05 13:08 UTC
- Investigating — 2026-10-05 13:08 UTC
- Identified — 2026-10-05 14:05 UTC
- Monitoring — 2026-10-05 14:57 UTC
- Resolved — 2026-10-05 16:29 UTC · 3h 21m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Restaurant365 against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Restaurant365: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Restaurant365 report →
More from Restaurant365
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.