Square logged a service disruption on 5 November 2026 that lasted 5 minutes. The fault sat on Square's side, not yours, though the brief window and a single update make it hard to say exactly what it touched.
Started
17:21 UTC
Duration
Lasted 5m
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's status page opened an incident called "Service Disruption" at 17:21 UTC. The one update posted says Square was "currently experiencing a disruption that is impacting some Square services" and that its engineering team was "actively working on a fix". No component list accompanies this entry, so there is no breakdown of which specific service, payments, point of sale, or something else, was affected. The incident closed 5 minutes after it opened, and Square filed nothing further: no identification of cause, no confirmation of resolution beyond the timeline implied by the closing, and no follow-up post. That single filing is all that exists on the record for this day. No user reports came in during the window, so there is nothing from outside Square to compare against its own account. Over the past 90 days Square has logged 21 incidents with a median duration of 1 hour 4 minutes, which makes this 5 minute incident markedly shorter than Square's own recent pattern. Whatever broke, it was resolved quickly enough that it may not have registered for anyone actually using Square's services at the time. No post-mortem has been published, and the cause is not on the record.
Learning
UptimeRobot's own 30 day data on Square shows 6 incidents, all resolved, with a median duration of 1h 20m, a different shape to this one. That gap is expected: external checks watch whether Square's endpoints respond from outside, while Square's own status page reflects internal fault reports that may never surface as a reachability failure your monitor would catch, or may resolve faster than a probe cycle can register. A 5 minute disruption with no component detail and no user reports is exactly the kind of event that can pass through external monitoring untouched while still being real on the vendor's side. If your product relies on Square for payments or checkout, this is a reminder that your own uptime checks only confirm your side is up, not that every upstream call to Square is landing cleanly. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.