Olo Outage History

Olo experienced a data pipeline issue that caused stale or missing data in Dashboard and reporting features for 2.4 hours. The problem affected scheduled reports and Dashboard displays, with customers seeing outdated information during the incident. The issue was identified and resolved through processing a reporting data backlog, restoring current data to all affected systems.

Olo experienced payment processing issues due to a problem identified by their payment partner Paytronix. The incident affected Payment Processing Partners components for 3.5 hours. Paytronix implemented a fix and the issue was resolved after monitoring confirmed the solution was working properly.

Olo's Switchboard service experienced errors generating SMS payment links for 6.8 hours, preventing users from completing SMS payments and affecting multiple components including ordering APIs, mobile apps, and point-of-sale systems. The issue was traced to their SMS link provider's system, and operators used email payments as a workaround during the outage. The incident was resolved after the provider fixed their system and Olo implemented monitoring.

Olo experienced a 5.7-hour ordering disruption caused by an AWS outage that affected the Ordering API, Dispatch API, desktop web ordering, and mobile app ordering capabilities. The company implemented a fix and monitored the results before fully resolving the incident. All ordering functionality was restored after the resolution.

Olo experienced elevated payment processing errors through their Paymentech payment provider, affecting ordering capabilities at locations using Paymentech for payment processing. The incident lasted 1.2 hours before Paymentech transactions returned to normal and the issue was resolved.

Olo experienced elevated payment processing errors through their NCR payment provider, affecting ordering capabilities at locations using NCR for payments. The incident impacted Payment Processing Partners and lasted 1.6 hours. NCR identified the root cause and implemented necessary changes, with Olo monitoring the fix before confirming full resolution.

Olo experienced a partial ordering disruption where a small percentage of order validation and submission attempts failed, preventing customers from completing orders to the point of sale. The issue affected mobile app ordering, desktop web ordering, the ordering API, and Switchboard services. The incident was resolved after 20 minutes with a fix implementation and monitoring period.

Olo experienced payment and loyalty processing issues for 24 minutes due to a problem identified by their partner Paytronix. The incident affected Payment Processing Partners and Loyalty Partners components. The issue was resolved after Paytronix transactions returned to normal operations.

Olo experienced a partial platform disruption lasting 42 minutes due to emergency maintenance that required taking the platform offline. The incident affected multiple critical components including ordering APIs, mobile and web ordering, point of sale systems, dashboard, reporting, and webhooks. The issue was resolved after implementing a fix and monitoring the results.

Olo experienced delays in processing Eighty Sixing requests, causing changes to menu item availability to not be immediately reflected in menus. The Eighty Sixing component was affected for 26 minutes before a fix was implemented and the incident was resolved.