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)

As listed on Restaurant365’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Restaurant365 status & history page.

Related: Restaurant365 status & history. SquidGrid is not affiliated with Restaurant365.