Live / Olo / Incident
Olo: Scheduled Orders are Firing Late
Olo · olo.comMajor incidentResolved2026-10-10 17:59 UTC
Public — what happened
Summary
Olo reported a major issue on October 10, 2026, starting at 16:46 UTC, in which orders placed for a later time were reaching restaurants' Point of Sale systems behind schedule. The company investigated for roughly an hour and did not publicly name a cause. At 17:37 UTC Olo said it had put a fix in place and that scheduled orders were going through again, and it marked the incident resolved at 17:59 UTC.
Affected
Scheduler
Timeline
- Started — 2026-10-10 16:46 UTC
- Investigating — 2026-10-10 16:46 UTC (2 updates)
- Monitoring — 2026-10-10 17:37 UTC
- Resolved — 2026-10-10 17:59 UTC · 1h 13m 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 Olo 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 Olo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Olo report →
More from Olo
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.