Skip to content

Outage tracker / Square

Is Square down?

I'm having a problem

Operationalchecked moments ago

We reached Square from all 10 regions we check.

As of Sep 23, 2026, 9:09 AM UTC, Square answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Square (since Aug 8, 2026).

Square reports an active incident: "Service Disruption" (minor incident, since Sep 21, 2026, 7:40 PM UTC). That is their claim, not our measurement: our probes are currently reaching Square, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 23, 2026, 9:09 AM UTC
US-East141 msOperational
US-West166 msOperational
Europe312 msOperational
Asia-Pacific322 msOperational
US-Central610 msOperational
Canada489 msOperational
UK511 msOperational
Southeast Asia1467 msOperational
Australia197 msOperational
South America179 msOperational
their status pagetheir claim, not our reading

Square reports: Minor incident (“Partial System Degradation”)

from Square's own status page, checked Sep 23, 2026, 8:47 AM UTC

Square reports an active incident: Service Disruption (minor incident, since Sep 21, 2026, 7:40 PM UTC)

Square's status page reports Partial System Degradation. Our probes are currently reaching Square successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

This is Square's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Square response time, by region

US-East
404msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 689ms2026-08-26 UTC: p95 935ms2026-08-27 UTC: p95 971ms2026-08-28 UTC: p95 527ms2026-08-29 UTC: p95 427ms2026-08-30 UTC: p95 499ms2026-08-31 UTC: p95 603ms2026-09-01 UTC: p95 767ms2026-09-02 UTC: p95 934ms2026-09-03 UTC: p95 885ms2026-09-04 UTC: p95 548ms2026-09-05 UTC: p95 693ms2026-09-06 UTC: p95 541ms2026-09-07 UTC: p95 453ms2026-09-08 UTC: p95 420ms2026-09-09 UTC: p95 392ms2026-09-10 UTC: p95 241ms2026-09-11 UTC: p95 375ms2026-09-12 UTC: p95 339ms2026-09-13 UTC: p95 358ms2026-09-14 UTC: p95 386ms2026-09-15 UTC: p95 420ms2026-09-16 UTC: p95 373ms2026-09-17 UTC: p95 512ms2026-09-18 UTC: p95 500ms2026-09-19 UTC: p95 337ms2026-09-20 UTC: p95 391ms2026-09-21 UTC: p95 517ms2026-09-22 UTC: p95 393ms2026-09-23 UTC: p95 404ms
Aug 25Sep 8Sep 23
US-West
302msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 443ms2026-08-26 UTC: p95 322ms2026-08-27 UTC: p95 620ms2026-08-28 UTC: p95 503ms2026-08-29 UTC: p95 697ms2026-08-30 UTC: p95 652ms2026-08-31 UTC: p95 694ms2026-09-01 UTC: p95 402ms2026-09-02 UTC: p95 444ms2026-09-03 UTC: p95 638ms2026-09-04 UTC: p95 350ms2026-09-05 UTC: p95 482ms2026-09-06 UTC: p95 501ms2026-09-07 UTC: p95 333ms2026-09-08 UTC: p95 413ms2026-09-09 UTC: p95 284ms2026-09-10 UTC: p95 286ms2026-09-11 UTC: p95 284ms2026-09-12 UTC: p95 141ms2026-09-13 UTC: p95 226ms2026-09-14 UTC: p95 321ms2026-09-15 UTC: p95 448ms2026-09-16 UTC: p95 430ms2026-09-17 UTC: p95 379ms2026-09-18 UTC: p95 579ms2026-09-19 UTC: p95 702ms2026-09-20 UTC: p95 578ms2026-09-21 UTC: p95 720ms2026-09-22 UTC: p95 434ms2026-09-23 UTC: p95 302ms
Aug 25Sep 8Sep 23
Europe
385msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 514ms2026-08-26 UTC: p95 498ms2026-08-27 UTC: p95 573ms2026-08-28 UTC: p95 500ms2026-08-29 UTC: p95 417ms2026-08-30 UTC: p95 497ms2026-08-31 UTC: p95 421ms2026-09-01 UTC: p95 487ms2026-09-02 UTC: p95 540ms2026-09-03 UTC: p95 540ms2026-09-04 UTC: p95 568ms2026-09-05 UTC: p95 771ms2026-09-06 UTC: p95 629ms2026-09-07 UTC: p95 740ms2026-09-08 UTC: p95 719ms2026-09-09 UTC: p95 655ms2026-09-10 UTC: p95 482ms2026-09-11 UTC: p95 306ms2026-09-12 UTC: p95 316ms2026-09-13 UTC: p95 352ms2026-09-14 UTC: p95 402ms2026-09-15 UTC: p95 456ms2026-09-16 UTC: p95 440ms2026-09-17 UTC: p95 529ms2026-09-18 UTC: p95 290ms2026-09-19 UTC: p95 286ms2026-09-20 UTC: p95 291ms2026-09-21 UTC: p95 419ms2026-09-22 UTC: p95 461ms2026-09-23 UTC: p95 385ms
Aug 25Sep 8Sep 23
Asia-Pacific
625msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 863ms2026-08-26 UTC: p95 757ms2026-08-27 UTC: p95 856ms2026-08-28 UTC: p95 840ms2026-08-29 UTC: p95 896ms2026-08-30 UTC: p95 893ms2026-08-31 UTC: p95 853ms2026-09-01 UTC: p95 798ms2026-09-02 UTC: p95 948ms2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 943ms2026-09-05 UTC: p95 960ms2026-09-06 UTC: p95 983ms2026-09-07 UTC: p95 878ms2026-09-08 UTC: p95 999ms2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 824ms2026-09-12 UTC: p95 700ms2026-09-13 UTC: p95 994ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 954ms2026-09-17 UTC: p95 727ms2026-09-18 UTC: p95 815ms2026-09-19 UTC: p95 670ms2026-09-20 UTC: p95 716ms2026-09-21 UTC: p95 687ms2026-09-22 UTC: p95 785ms2026-09-23 UTC: p95 625ms
Aug 25Sep 8Sep 23
US-Central
615msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 700ms2026-09-04 UTC: p95 940ms2026-09-05 UTC: p95 614ms2026-09-06 UTC: p95 555ms2026-09-07 UTC: p95 623ms2026-09-08 UTC: p95 740ms2026-09-09 UTC: p95 807ms2026-09-10 UTC: p95 454ms2026-09-11 UTC: p95 577ms2026-09-12 UTC: p95 504ms2026-09-13 UTC: p95 587ms2026-09-14 UTC: p95 657ms2026-09-15 UTC: p95 466ms2026-09-16 UTC: p95 425ms2026-09-17 UTC: p95 397ms2026-09-18 UTC: p95 422ms2026-09-19 UTC: p95 476ms2026-09-20 UTC: p95 551ms2026-09-21 UTC: p95 559ms2026-09-22 UTC: p95 393ms2026-09-23 UTC: p95 615ms
Aug 25Sep 8Sep 23
Canada
605msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 616ms2026-09-04 UTC: p95 519ms2026-09-05 UTC: p95 589ms2026-09-06 UTC: p95 621ms2026-09-07 UTC: p95 501ms2026-09-08 UTC: p95 585ms2026-09-09 UTC: p95 619ms2026-09-10 UTC: p95 365ms2026-09-11 UTC: p95 253ms2026-09-12 UTC: p95 383ms2026-09-13 UTC: p95 495ms2026-09-14 UTC: p95 531ms2026-09-15 UTC: p95 292ms2026-09-16 UTC: p95 466ms2026-09-17 UTC: p95 629ms2026-09-18 UTC: p95 418ms2026-09-19 UTC: p95 256ms2026-09-20 UTC: p95 256ms2026-09-21 UTC: p95 404ms2026-09-22 UTC: p95 561ms2026-09-23 UTC: p95 605ms
Aug 25Sep 8Sep 23
UK
858msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 376ms2026-09-04 UTC: p95 491ms2026-09-05 UTC: p95 380ms2026-09-06 UTC: p95 387ms2026-09-07 UTC: p95 371ms2026-09-08 UTC: p95 327ms2026-09-09 UTC: p95 391ms2026-09-10 UTC: p95 502ms2026-09-11 UTC: p95 281ms2026-09-12 UTC: p95 243ms2026-09-13 UTC: p95 254ms2026-09-14 UTC: p95 269ms2026-09-15 UTC: p95 258ms2026-09-16 UTC: p95 328ms2026-09-17 UTC: p95 317ms2026-09-18 UTC: p95 334ms2026-09-19 UTC: p95 304ms2026-09-20 UTC: p95 324ms2026-09-21 UTC: p95 629ms2026-09-22 UTC: p95 837ms2026-09-23 UTC: p95 858ms
Aug 25Sep 8Sep 23
Southeast Asia
2.5sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 2.9s2026-09-23 UTC: p95 2.5s
Aug 25Sep 8Sep 23
Australia
628msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 920ms2026-09-06 UTC: p95 885ms2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 600ms2026-09-11 UTC: p95 616ms2026-09-12 UTC: p95 473ms2026-09-13 UTC: p95 470ms2026-09-14 UTC: p95 464ms2026-09-15 UTC: p95 458ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 735ms2026-09-18 UTC: p95 684ms2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 964ms2026-09-22 UTC: p95 600ms2026-09-23 UTC: p95 628ms
Aug 25Sep 8Sep 23
South America
1.4sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 752ms2026-09-12 UTC: p95 850ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 864ms2026-09-16 UTC: p95 916ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 990ms2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 968ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.4s
Aug 25Sep 8Sep 23

Is it Square, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Square -- it cannot diagnose Square's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 141msstatus code: 401checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Square normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 166msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Square normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 610msstatus code: 401checked: Sep 23, 2026, 8:50 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Square normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 489msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Square normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 179msstatus code: 401checked: Sep 23, 2026, 9:08 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Square normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 312msstatus code: 401checked: Sep 23, 2026, 8:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Square normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 511msstatus code: 401checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Square normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 322msstatus code: 401checked: Sep 23, 2026, 9:08 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Square normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1467msstatus code: 401checked: Sep 23, 2026, 9:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Square normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 197msstatus code: 401checked: Sep 23, 2026, 9:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Square normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Square, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Square yet, which is not evidence that nothing is wrong.

Recent outages

Service Disruptiondeclared on their status page2026-09-21
Service Disruption, 3h 54mdeclared on their status page2026-09-18
Transfers Disruption, 15h 7mdeclared on their status page2026-09-18
Service Disruption, 34mdeclared on their status page2026-09-16
Service Disruption, 1h 1mdeclared on their status page2026-09-14
Payments Disruption, 17mdeclared on their status page2026-09-10
Service Disruption, 17mdeclared on their status page2026-08-24
Chat Support Outage , 2h 3mdeclared on their status page2026-08-18

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Square since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Square covering any window you pick, with our measurements and Square's own claim at the time, side by side.

Full availability history for Square: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Square, and again when they can reach it again. That is our own measurement from ten regions, not Square's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Square uptime measured by RealUptimeLive, from this page's own readings.
[![Square uptime measured by RealUptime](https://realuptime.io/outages/square/badge.svg?days=30)](https://realuptime.io/outages/square)
<a href="https://realuptime.io/outages/square"><img src="https://realuptime.io/outages/square/badge.svg?days=30" alt="Square uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Square's SLA implies, from our measurement

At or above your target

We measured none of downtime for Square over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Square's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://connect.squareup.com/v2/locations
secondary
https://www.issquareup.com/
RealUptime is not affiliated with Square; the name identifies what we measured, and nothing here speaks for Square's own team. We send a single web request to Square from 10 regions on our own schedule and time the response. We do not see inside Square's systems, do not use an account or real transaction, and are not the same signal Square's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Square is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.