Skip to content

Outage tracker / Square

Is Square down?

I'm having a problem

Vendor reports no incidentWhat Square reports

Square reports no incident on its status page.

As of the last successful poll, 2026-10-14 04:30 UTC.

Square's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of Square pass from all 10 regions we check.

As of Oct 14, 2026, 4:32 AM UTC, RealUptime's checks of Square passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 14, 2026, 4:32 AM UTC
US-East152 msChecks passing
US-West162 msChecks passing
Europe213 msChecks passing
Asia-Pacific512 msChecks passing
US-Central317 msChecks passing
Canada204 msChecks passing
UK222 msChecks passing
Southeast Asia579 msChecks passing
Australia573 msChecks passing
South America1246 msChecks passing
their status pagetheir claim, not our reading

Square reports: All systems operational (“All Systems Operational”)

from Square's own status page, checked Oct 14, 2026, 4:19 AM UTC
Square's own status page shows no incident, and our checks of Square pass right now.

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
570msp95 · 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-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 411ms2026-09-24 UTC: p95 386ms2026-09-25 UTC: p95 407ms2026-09-26 UTC: p95 406ms2026-09-27 UTC: p95 501ms2026-09-28 UTC: p95 506ms2026-09-29 UTC: p95 514ms2026-09-30 UTC: p95 493ms2026-10-01 UTC: p95 524ms2026-10-02 UTC: p95 467ms2026-10-03 UTC: p95 507ms2026-10-04 UTC: p95 507ms2026-10-05 UTC: p95 546ms2026-10-06 UTC: p95 569ms2026-10-07 UTC: p95 487ms2026-10-08 UTC: p95 280ms2026-10-09 UTC: p95 239ms2026-10-10 UTC: p95 491ms2026-10-11 UTC: p95 539ms2026-10-12 UTC: p95 480ms2026-10-13 UTC: p95 601ms2026-10-14 UTC: p95 570ms
Sep 15Sep 29Oct 14
US-West
501msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 337ms2026-09-24 UTC: p95 298ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 871ms2026-09-27 UTC: p95 583ms2026-09-28 UTC: p95 599ms2026-09-29 UTC: p95 725ms2026-09-30 UTC: p95 620ms2026-10-01 UTC: p95 496ms2026-10-02 UTC: p95 498ms2026-10-03 UTC: p95 665ms2026-10-04 UTC: p95 591ms2026-10-05 UTC: p95 719ms2026-10-06 UTC: p95 616ms2026-10-07 UTC: p95 685ms2026-10-08 UTC: p95 258ms2026-10-09 UTC: p95 411ms2026-10-10 UTC: p95 363ms2026-10-11 UTC: p95 612ms2026-10-12 UTC: p95 586ms2026-10-13 UTC: p95 517ms2026-10-14 UTC: p95 501ms
Sep 15Sep 29Oct 14
Europe
546msp95 · 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-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 437ms2026-09-24 UTC: p95 390ms2026-09-25 UTC: p95 418ms2026-09-26 UTC: p95 474ms2026-09-27 UTC: p95 468ms2026-09-28 UTC: p95 505ms2026-09-29 UTC: p95 579ms2026-09-30 UTC: p95 680ms2026-10-01 UTC: p95 665ms2026-10-02 UTC: p95 608ms2026-10-03 UTC: p95 608ms2026-10-04 UTC: p95 604ms2026-10-05 UTC: p95 559ms2026-10-06 UTC: p95 536ms2026-10-07 UTC: p95 593ms2026-10-08 UTC: p95 482ms2026-10-09 UTC: p95 560ms2026-10-10 UTC: p95 424ms2026-10-11 UTC: p95 582ms2026-10-12 UTC: p95 508ms2026-10-13 UTC: p95 402ms2026-10-14 UTC: p95 546ms
Sep 15Sep 29Oct 14
Asia-Pacific
801msp95 · 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-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 684ms2026-09-24 UTC: p95 705ms2026-09-25 UTC: p95 940ms2026-09-26 UTC: p95 897ms2026-09-27 UTC: p95 694ms2026-09-28 UTC: p95 655ms2026-09-29 UTC: p95 755ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 727ms2026-10-03 UTC: p95 992ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 968ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 983ms2026-10-12 UTC: p95 998ms2026-10-13 UTC: p95 985ms2026-10-14 UTC: p95 801ms
Sep 15Sep 29Oct 14
US-Central
531msp95 · 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-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 603ms2026-09-24 UTC: p95 599ms2026-09-25 UTC: p95 345ms2026-09-26 UTC: p95 540ms2026-09-27 UTC: p95 461ms2026-09-28 UTC: p95 415ms2026-09-29 UTC: p95 291ms2026-09-30 UTC: p95 580ms2026-10-01 UTC: p95 462ms2026-10-02 UTC: p95 292ms2026-10-03 UTC: p95 478ms2026-10-04 UTC: p95 554ms2026-10-05 UTC: p95 609ms2026-10-06 UTC: p95 541ms2026-10-07 UTC: p95 508ms2026-10-08 UTC: p95 442ms2026-10-09 UTC: p95 255ms2026-10-10 UTC: p95 400ms2026-10-11 UTC: p95 471ms2026-10-12 UTC: p95 574ms2026-10-13 UTC: p95 518ms2026-10-14 UTC: p95 531ms
Sep 15Sep 29Oct 14
Canada
638msp95 · 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-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 605ms2026-09-24 UTC: p95 553ms2026-09-25 UTC: p95 342ms2026-09-26 UTC: p95 506ms2026-09-27 UTC: p95 465ms2026-09-28 UTC: p95 367ms2026-09-29 UTC: p95 419ms2026-09-30 UTC: p95 342ms2026-10-01 UTC: p95 328ms2026-10-02 UTC: p95 352ms2026-10-03 UTC: p95 371ms2026-10-04 UTC: p95 534ms2026-10-05 UTC: p95 444ms2026-10-06 UTC: p95 699ms2026-10-07 UTC: p95 643ms2026-10-08 UTC: p95 558ms2026-10-09 UTC: p95 413ms2026-10-10 UTC: p95 465ms2026-10-11 UTC: p95 424ms2026-10-12 UTC: p95 542ms2026-10-13 UTC: p95 506ms2026-10-14 UTC: p95 638ms
Sep 15Sep 29Oct 14
UK
331msp95 · 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-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 931ms2026-09-24 UTC: p95 917ms2026-09-25 UTC: p95 585ms2026-09-26 UTC: p95 602ms2026-09-27 UTC: p95 401ms2026-09-28 UTC: p95 711ms2026-09-29 UTC: p95 458ms2026-09-30 UTC: p95 529ms2026-10-01 UTC: p95 538ms2026-10-02 UTC: p95 482ms2026-10-03 UTC: p95 526ms2026-10-04 UTC: p95 455ms2026-10-05 UTC: p95 473ms2026-10-06 UTC: p95 445ms2026-10-07 UTC: p95 465ms2026-10-08 UTC: p95 436ms2026-10-09 UTC: p95 438ms2026-10-10 UTC: p95 379ms2026-10-11 UTC: p95 326ms2026-10-12 UTC: p95 409ms2026-10-13 UTC: p95 440ms2026-10-14 UTC: p95 331ms
Sep 15Sep 29Oct 14
Southeast Asia
1.0sp95 · 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-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.7s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.8s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 855ms2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 985ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s
Sep 15Sep 29Oct 14
Australia
1.0sp95 · 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-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 605ms2026-09-24 UTC: p95 460ms2026-09-25 UTC: p95 744ms2026-09-26 UTC: p95 869ms2026-09-27 UTC: p95 824ms2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 919ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 932ms2026-10-04 UTC: p95 998ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 829ms2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 604ms2026-10-12 UTC: p95 856ms2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.0s
Sep 15Sep 29Oct 14
South America
1.2sp95 · 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-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.2s2026-09-24 UTC: p95 940ms2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 834ms2026-09-29 UTC: p95 933ms2026-09-30 UTC: p95 952ms2026-10-01 UTC: p95 974ms2026-10-02 UTC: p95 797ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 908ms2026-10-09 UTC: p95 881ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14

Check your own site while you wait on Square

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.

Email me when Square reports an incident on its status page, and again when it reports it resolved.

Get an email when Square reports an incident

Email me when Square reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Square's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 152msstatus code: 401checked: Oct 14, 2026, 4:24 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
      Checks passinglatency: 162msstatus code: 401checked: Oct 14, 2026, 4:27 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
      Checks passinglatency: 317msstatus code: 401checked: Oct 14, 2026, 4:30 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
      Checks passinglatency: 204msstatus code: 401checked: Oct 14, 2026, 4:12 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
    Checks passinglatency: 1246msstatus code: 401checked: Oct 14, 2026, 4:32 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 213msstatus code: 401checked: Oct 14, 2026, 4:28 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
      Checks passinglatency: 222msstatus code: 401checked: Oct 14, 2026, 4:32 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 512msstatus code: 401checked: Oct 14, 2026, 4:25 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
      Checks passinglatency: 579msstatus code: 401checked: Oct 14, 2026, 4:15 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
      Checks passinglatency: 573msstatus code: 401checked: Oct 14, 2026, 4:14 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 probe events

Service Disruption, 5h 32mdeclared on their status page2026-10-07
Service Disruption, 1h 47mdeclared on their status page2026-09-27
Service Disruption, 12mdeclared on their status page2026-09-24
Service Disruptiondeclared on their status page2026-09-24
Service Disruption, 52h 45mdeclared 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

check 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 check readings and Square's own claim at the time, side by side.

Full check history for Square: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Square uptime by RealUptime's checksLive, from this page's own readings.
[![Square uptime by RealUptime's checks](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 by RealUptime's checks"></a>

The badge shows the share of our checks that passed 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Square down?", https://realuptime.io/outages/square. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://connect.squareup.com/v2/locations
secondary
https://www.issquareup.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: connect.squareup.com

RealUptime is not affiliated with Square; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.