Live / Restaurant365 / Incident
Restaurant365: Login Troubles for Certain Users
Restaurant365 · restaurant365.comMinor incidentResolved2026-10-05 16:28 UTC
Public — what happened
Summary
Restaurant365 reported a minor incident on October 5, 2026, starting at 13:41 UTC, in which some customers ran into errors while trying to sign in. By 14:08 UTC the company said it had found the underlying cause, though it did not describe it, and was rolling out a fix. Restaurant365 said the fix was in place by 14:57 UTC, and after a period of monitoring the incident was marked resolved at 16:28.
Affected
Customer Databases
Timeline
- Started — 2026-10-05 13:41 UTC
- Investigating — 2026-10-05 13:41 UTC
- Identified — 2026-10-05 14:08 UTC
- Monitoring — 2026-10-05 14:57 UTC
- Resolved — 2026-10-05 16:28 UTC · 2h 47m 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.