Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Olo Outage History

Every past Olo outage tracked by IsDown, with detection times, duration, and resolution details.

There were 652 Olo outages since October 2020. The 66 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 21, 2026

April 2026: Payment Processor Issues: NCR

Detected Apr 21, 2026 3:01 PM EDT · Resolved Apr 21, 2026 4:39 PM EDT · Duration about 2 hours

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.

Minor April 9, 2026

April 2026: Partial Ordering Disruption

Detected Apr 9, 2026 12:56 PM EDT · Resolved Apr 9, 2026 1:16 PM EDT · Duration 20 minutes

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.

Minor March 20, 2026

March 2026: Payment and LoyaltyProcessor Issues: Paytronix

Detected Mar 20, 2026 11:53 AM EDT · Resolved Mar 20, 2026 12:17 PM EDT · Duration 24 minutes

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.

Minor March 19, 2026

March 2026: Partial Platform Disruption

Detected Mar 19, 2026 6:36 PM EDT · Resolved Mar 19, 2026 7:18 PM EDT · Duration 42 minutes

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.

Minor March 19, 2026

March 2026: Eighty Sixing Processing Delays

Detected Mar 19, 2026 9:01 AM EDT · Resolved Mar 19, 2026 9:27 AM EDT · Duration 26 minutes

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.

Minor March 11, 2026

March 2026: Payment Gateway Issues: FreedomPay

Detected Mar 11, 2026 12:15 PM EDT · Resolved Mar 11, 2026 12:44 PM EDT · Duration 28 minutes

Olo experienced elevated payment processing errors through the FreedomPay gateway, affecting ordering and POS payments at locations using FreedomPay. The payment processing issues were resolved after 28 minutes of service disruption.

Major March 5, 2026

March 2026: Payment Processor Issues: Olo Pay (Stripe)

Detected Mar 5, 2026 5:11 PM EST · Resolved Mar 5, 2026 5:41 PM EST · Duration 30 minutes

Olo experienced elevated payment processing errors through Olo Pay (Stripe) that affected ordering at locations using this payment provider. The issue was identified as originating from Stripe's end and was resolved after 30 minutes of service disruption.

Major March 3, 2026

March 2026: Ordering Disruption

Detected Mar 3, 2026 8:11 AM EST · Resolved Mar 3, 2026 8:30 AM EST · Duration 19 minutes

Olo experienced a major disruption in ordering capabilities that affected the Ordering API, Desktop Web Ordering, and Mobile App Ordering systems for 19 minutes. The company implemented a fix that restored ordering rates and continued monitoring the systems. The incident was fully resolved after confirming stable operations.