Olo logo

Is Olo Down?

FinTech & PaymentsLive status, outages, and incident history

Degraded. Olo is up but having problems.

Olo is reporting degraded performance as of November 9, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · every 60s1 active incident

Don't find out like this next time

You searched to find out Olo was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official Olo status page
How we know: the official Olo status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Olo Status Summary

As of 15:08 UTC on 9 November 2026, Olo is reporting degraded performance. PulsAPI checked Olo's official status page and found 52 of 53 components operational, with 1 active incident. Over the last 30 days PulsAPI measured 99.95% uptime for Olo, counting degraded performance as up. The latest incident, "Payment Processor Issues: Worldpay MercPay Webservices", started on Nov 8, 2026 and is still open.

Cite as: PulsAPI, “Olo status”, checked 9 November 2026, 15:08 UTC. https://www.pulsapi.com/services/olo

Olo Component Status

1 of 53 Olo components are impaired. Worst problems listed first.

1degraded52operational
Partners » Payment Processing Partners
Degraded
Checkout iFrame
Operational
Content Delivery Network
Operational

50 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Coupon API, Dashboard, Developer Platform » Developer Portal, Developer Platform » Sandbox, Developer Portal, Dispatch API, Eighty Sixing, Email Delivery, Expo, Menu Exports, Menu Services, Mobile App Ordering, and 38 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Olo Outages & Incidents

Incident history from the official Olo status page, including resolution updates.

Payment Processor Issues: Worldpay MercPay WebservicesStarted Nov 8, 2026Investigating

Errors have recovered and we are actively monitoring at this time. --- [2026-11-08T19:10:19.857725Z] (identified) Error rates from Worldpay MercPay Webservices' token service have increased, and more card payments are failing at locations using Worldpay MercPay Webservices as their payment provider. We're continuing to monitor and will post updates as the situation changes. --- [2026-11-08T18:37:35.916745Z] (identified) We've identified intermittent errors from Worldpay MercPay Webservices' token service that are causing some card payments to fail at locations using Worldpay MercPay Webservices as their payment provider. We're continuing to monitor.

Ordering DisruptionResolved Nov 5, 2026 · 32 minResolved

Impact to ordering has stabilized. --- [2026-11-05T15:26:22.954628Z] (monitoring) We are seeing ordering rate return to normal for Serve. We are continuing to monitor for impacts to ordering rate. --- [2026-11-05T15:16:18.283039Z] (investigating) We are investigating a disruption in ordering capabilities and will provide updates as they become available.

Payment Processor Issues: GivexResolved Nov 1, 2026 · 18h 20mResolved

Gift card balance checks and payments through our Givex integration are operating normally. This incident has been resolved. --- [2026-11-02T23:43:53.656245Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-11-02T23:43:53.656245Z] (monitoring) We are seeing Givex transactions return to normal and continue to monitor the situation to confirm full recovery. --- [2026-11-02T23:43:53.656245Z] (investigating) We're detecting elevated errors processing gift card balance checks and payments through Givex. Ordering may be affected at locations using Givex gift cards, and some guests may experience slow loading of payment options at checkout. Other payment methods are working normally.

Olo Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Olo incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 9 days with incidentsNov 9

Going further back: Olo uptime by month and every recorded Olo outage.

Live Olo Outage Reports

Problems reported by engineers using Olo. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Olo problems reported yet.

Are you seeing Olo problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Olo

Olo publishes a public status page at status.olo.com covering 39 components, including Ordering API, Point of Sale Partners and Ordering. PulsAPI tracks Olo outages, degraded performance and incident history in real time, alongside the rest of your payments and fintech stack.

Over the past 30 days, PulsAPI has measured Olo uptime at 99.95%. Response times, incident history, and SLA tracking for Olo are available on the PulsAPI dashboard.

Olo Status FAQ

Is Olo down right now?

The verdict at the top of this page comes from the latest poll of the official Olo status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Olo is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Olo recovers.

How do I check Olo uptime history?

PulsAPI tracks Olo uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.95%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Olo changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Olo outages?

PulsAPI reads the official Olo status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Olo components?

Yes. PulsAPI monitors 53 individual Olo components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Olo goes down?

Yes. Create a free account and subscribe to Olo: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Olo to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Olo problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Olo?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Olo plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Olo with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services