Square's Point of Sale and Kitchen Display System broke down for 48 minutes late on 27 October 2026. Orders stopped syncing across devices, including to kitchen displays, and the fault sat with Square's own systems.
Started
23:43 UTC
Duration
Lasted 48m
Source
IsDown
Next time
Square is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Square logged one incident on this day, starting at 23:43 UTC and lasting 48 minutes. The first update said a disruption was impacting some Square services, with engineering already working on a fix. Two minutes later, at 23:45 UTC, Square was more specific: sellers would see delays in orders syncing across devices, including orders reaching kitchen displays. For anyone running a restaurant or retail counter off Square, that means tickets placed at the till were not arriving where food gets made or stock gets pulled. At 00:04 UTC, Square posted that a fix had been released for Point of Sale and Kitchen Display System, and that services were beginning to return to full functionality. That update closed the incident, 48 minutes after it opened. Square filed three updates in total, and no user reports were logged in this window. No components are listed as affected in Square's own breakdown, which means this incident lived inside the text updates rather than a formally flagged component. No post-mortem has been published, so the cause behind the sync delay is not on the record. Over the past 90 days Square has logged 19 incidents with a median duration of 1 hour 4 minutes, so this one resolved faster than Square's own recent average.
Learning
This incident shows a sync failure between Square's Point of Sale and Kitchen Display System, a breakdown between two parts of Square's own infrastructure rather than something that would show up as your endpoint going dark. If you only watch your own storefront or app for uptime, this kind of fault slips past you, because your product may have stayed reachable while the orders behind it stopped moving where they needed to go. Square's 30 day record shows 3 incidents, all resolved, with a median duration of 3 hours, longer than the 48 minutes this one took, which tells you how much variation sits inside what looks like one category of fault. The pattern to recognise in your own setup is simple: a request can succeed at the surface while the processing step behind it stalls, and no amount of pinging your own URL reveals that. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.