Square had two separate service disruptions on 24 September 2026, the first starting at 21:07 UTC and lasting 5h 25m. Both were on Square's side of the connection, affecting the ability to accept payments at point of sale.
Started
21:07 UTC
Duration
Lasted 5h 25m
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 two disruptions within nine minutes of each other on 24 September. The first began at 21:07 UTC and ran for 5h 25m before resolution. The second began at 21:16 UTC, titled the same way, "Service Disruption", and lasted 12m. Square's own status page lists only one update for each incident, both posted at the moment the incident opened, and neither update was followed by a further note confirming what caused the problem or when it was actually fixed behind the scenes. The first update said Square was "experiencing a disruption that is impacting some Square services" and that engineering was "actively working on a fix". The second was more specific, saying the disruption affected "payment processing at point of sale" and that the ability to accept payments was Square's "top priority". No components are listed as affected in Square's own breakdown, and no user reports were filed during this window. Square has not published a post-mortem for either incident, so the exact cause is not on the record for either one. Over the prior 90 days, Square logged 21 incidents with a median duration of 1 hour 9 minutes, so a 5h 25m incident sits well above what is typical for this provider.
Learning
Square's point of sale and payment processing sit behind its own infrastructure, so an outage there can stop you taking payments even if every system you control is running normally. Over the 30 days around this incident, UptimeRobot's own probes recorded 9 incidents against Square with a median duration of 1h 47m, all resolved. Your own uptime checks, pinging your storefront or app, would show green the entire time, because what failed was the payment processor's own pipeline, not anything on your side of the connection. That gap is exactly why a status page saying "resolved" doesn't always match what a customer experienced in the moment: Square's one-line updates don't tell you how long the actual fault lasted, only when it was first spotted. If you build your monitoring around your own endpoints only, you'll miss this kind of failure every time, because the layer that broke sits upstream of anything you can poll yourself. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
