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-11-05 15:38 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 1 minute ago

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

As of Nov 5, 2026, 3:41 PM 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 Nov 5, 2026, 3:41 PM UTC
US-East1155 msChecks passing
US-West1429 msChecks passing
Europe791 msChecks passing
Asia-Pacific2214 msChecks passing
US-Central615 msChecks passing
Canada189 msChecks passing
UK469 msChecks passing
Southeast Asia1420 msChecks passing
Australia2539 msChecks passing
South America1297 msChecks passing
their status pagetheir claim, not our reading

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

from Square's own status page, checked Nov 5, 2026, 3:33 PM 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
1.6sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 596ms2026-10-15 UTC: p95 738ms2026-10-16 UTC: p95 549ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 855ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 513ms2026-10-29 UTC: p95 987ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
US-West
1.9sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 672ms2026-10-15 UTC: p95 645ms2026-10-16 UTC: p95 588ms2026-10-17 UTC: p95 682ms2026-10-18 UTC: p95 871ms2026-10-19 UTC: p95 816ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Europe
1.9sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 507ms2026-10-15 UTC: p95 697ms2026-10-16 UTC: p95 563ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 566ms2026-10-29 UTC: p95 703ms2026-10-30 UTC: p95 796ms2026-10-31 UTC: p95 683ms2026-11-01 UTC: p95 761ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Asia-Pacific
2.9sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 955ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 4.8s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 449ms2026-10-15 UTC: p95 471ms2026-10-16 UTC: p95 514ms2026-10-17 UTC: p95 968ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.0s2026-10-23 UTC: p95 964ms2026-10-24 UTC: p95 995ms2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 885ms2026-10-31 UTC: p95 885ms2026-11-01 UTC: p95 898ms2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Canada
758msp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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 612ms2026-10-15 UTC: p95 576ms2026-10-16 UTC: p95 539ms2026-10-17 UTC: p95 899ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.2s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 758ms
Oct 7Oct 21Nov 5
UK
824msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 427ms2026-10-15 UTC: p95 411ms2026-10-16 UTC: p95 434ms2026-10-17 UTC: p95 724ms2026-10-18 UTC: p95 869ms2026-10-19 UTC: p95 965ms2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.1s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 825ms2026-11-01 UTC: p95 870ms2026-11-02 UTC: p95 958ms2026-11-03 UTC: p95 817ms2026-11-04 UTC: p95 492ms2026-11-05 UTC: p95 824ms
Oct 7Oct 21Nov 5
Southeast Asia
2.9sp95 · 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-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.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.3s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.7s2026-11-01 UTC: p95 3.2s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.9s
Oct 7Oct 21Nov 5
Australia
3.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.3s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 2.7s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 2.7s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.9s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 3.4s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
South America
2.8sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.9s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 3.1s2026-10-22 UTC: p95 3.4s2026-10-23 UTC: p95 8.9s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.9s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 3s2026-11-01 UTC: p95 3.1s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5

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: 1155msstatus code: 401checked: Nov 5, 2026, 3:39 PM 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: 1429msstatus code: 401checked: Nov 5, 2026, 3:28 PM 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: 615msstatus code: 401checked: Nov 5, 2026, 3:33 PM 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: 189msstatus code: 401checked: Nov 5, 2026, 3:36 PM 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: 1297msstatus code: 401checked: Nov 5, 2026, 3:39 PM 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: 791msstatus code: 401checked: Nov 5, 2026, 3:36 PM 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: 469msstatus code: 401checked: Nov 5, 2026, 3:35 PM 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: 2214msstatus code: 401checked: Nov 5, 2026, 3:29 PM 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: 1420msstatus code: 401checked: Nov 5, 2026, 3:39 PM 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: 2539msstatus code: 401checked: Nov 5, 2026, 3:41 PM 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, 1h 11mdeclared on their status page2026-11-04
Service Disruption, 1h 26mdeclared on their status page2026-11-04
Service Disruption, 45mdeclared on their status page2026-10-27
Service Disruption, 2h 58mdeclared on their status page2026-10-18
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

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

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" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

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.