Live / Restaurant365 / Incident
Restaurant365: Intermittent Slowness
Restaurant365 · restaurant365.comMinor incidentResolved2026-11-03 03:20 UTC
Public — what happened
Summary
Restaurant365 said that some of its customers were experiencing intermittent slowness, which it rated as minor, beginning at 17:35 UTC on 2026-11-02. The company reported that its engineering team investigated through several hourly updates without naming a cause. At 23:34 UTC it said a fix had been put in place and that most customers should see normal service while it monitored for stability. The incident was marked resolved at 03:20 UTC on 2026-11-03.
Affected
Customer Databases
Timeline
- Started — 2026-11-02 17:35 UTC
- Investigating — 2026-11-02 17:35 UTC (6 updates)
- Monitoring — 2026-11-02 23:34 UTC
- Resolved — 2026-11-03 03:20 UTC · 9h 45m 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 46, 2026, our weekly internet health report.