Live  /  Restaurant365  /  Incident

Restaurant365: Intermittent Slowness

Restaurant365 · restaurant365.comMinor incidentResolved2026-11-04 22:38 UTC
Public — what happened

Summary

Restaurant365 reported an incident it called intermittent slowness, which it rated as minor and which affected certain customers. The company said it identified the slowness at 20:58 UTC on November 4, 2026 and began putting a solution in place. By 21:24 UTC it said a fix was in place and it was monitoring, adding that most customers should see normal service and that anyone still affected should contact Support. The incident was marked resolved at 22:38 UTC.

Affected

Customer Databases

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 46, 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.