Square had a service disruption starting at 04:37 UTC on 18 October 2026 that lasted 3 hours. The fault sat on Square's side, not yours, though the company never said which part of its stack was affected.
Started
04:37 UTC
Duration
Lasted 3h 0m
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 logged one incident on 18 October 2026, titled "Service Disruption", starting at 04:37 UTC. The only update posted was the opening one, at 04:37, saying Square was "experiencing a disruption that is impacting some Square services" and that engineering was "actively working on a fix". No component list was published alongside it, so there is no record of which specific service, payments, instant transfer, point of sale, or something else, was actually down. The incident closed out at 3 hours, but no update marked the resolution itself; the duration is simply the span the record shows. At 07:07 UTC, a user in Australia reported "Instant transfer not working", which lines up with the window the incident was open, though Square's own filing never named instant transfer specifically. That one update is the entire paper trail for this incident. No post-mortem has been published, and Square's status page does not say what caused the disruption. Over the past 90 days, Square has logged 20 incidents with a median duration of 1 hour 28 minutes, so this one ran longer than typical for the company. There is nothing in the record to suggest this incident was still open beyond the 3 hour window; it is marked as resolved, just without an update confirming it.
Learning
When a payments provider has an internal fault like this one, the breakage happens deep in their processing or transfer systems, places an external check pinging their public endpoints will not reach. UptimeRobot's own 30-day figures for Square show 8 incidents, all resolved, with a median duration of 4 hours 41 minutes, which is longer than what Square's own status page tends to report, a sign that outside monitoring and vendor self-reporting are measuring different things. Square's status page can show a short window because that is what the company chooses to publish, while a probe watching the service from outside can show a longer one because it is measuring actual availability rather than a company's own account of it. Neither reading is wrong, they are just looking at different halves of the same event. If instant transfer or another feature silently fails while the main site stays reachable, your own uptime checks on your product will stay green the whole time, because the problem isn't on your side at all. That is exactly the kind of gap this page exists to cover. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.