Skip to main content
Square logo

Is Square Down?

No — Square is up

Reachable from all 8 checked regions

Average response time: 98ms

Last checked · checks run every 6 hours

Official status page: https://www.issquareup.com

Square uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
100ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 32 checks
Jul 29: 100.00% uptime, 28 checks
Jul 30: 100.00% uptime, 31 checks
Jul 31: 100.00% uptime, 39 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 24 checks
Aug 3: 100.00% uptime, 40 checks
Aug 4: 100.00% uptime, 32 checks
Aug 5: 100.00% uptime, 38 checks
Aug 6: 100.00% uptime, 40 checks
Aug 7: 100.00% uptime, 24 checks
Aug 8: 100.00% uptime, 40 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
247ms
DNS 1ms TCP 2ms TLS 9ms TTFB 66ms
iad
76ms
DNS 0ms TCP 1ms TLS 7ms TTFB 49ms
jnb
75ms
DNS 0ms TCP 0ms TLS 8ms TTFB 52ms
lax
100ms
DNS 0ms TCP 1ms TLS 13ms TTFB 62ms
lhr
110ms
DNS 0ms TCP 1ms TLS 9ms TTFB 72ms
nrt
93ms
DNS 0ms TCP 2ms TLS 11ms TTFB 56ms
ord
127ms
DNS 3ms TCP 1ms TLS 8ms TTFB 88ms
sin
137ms
DNS 0ms TCP 1ms TLS 9ms TTFB 105ms
sjc
67ms
DNS 0ms TCP 1ms TLS 4ms TTFB 40ms

What Square does

Square provides payment processing along with point-of-sale hardware and software for small businesses. It handles card payments in person and online, plus invoicing and a seller dashboard. Many independent retailers and restaurants run every transaction through it, so an outage stops trade rather than merely inconveniencing it.

What an outage looks like

During a Square outage card payments are declined or hang at the terminal, the point-of-sale app shows a processing spinner that never resolves, and the seller dashboard is unreachable. Invoices and payment links can fail to load for customers. Staff often see the terminal appear online while transactions still fail to authorise.

What to do about it

Check issquareup.com, which reports point of sale, online payments, the dashboard and hardware separately. Square's offline mode can accept cards during an incident, but those payments are only authorised once connectivity returns and some will decline, so understand that exposure before relying on it. Payments authorised before the incident settle normally.

Is it down for everyone, or just you?

If this page says Square is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Square outage FAQ

Can I still take payments while Square is down?
Sometimes, using offline mode, which stores card payments and submits them when connectivity returns. The catch is that they are not authorised at the time of sale, so a card that has since been declined or has insufficient funds fails after the customer has left. Know your limit before depending on it.
Are payments already taken affected by an outage?
Payments authorised before the incident began settle normally. What is at risk is anything in flight when the outage started and anything accepted offline afterwards. Reconciling the day's takings against the dashboard once service returns is the reliable way to find transactions that did not complete.
Does a Square outage affect the hardware or just the app?
Both are reported separately. A terminal can be perfectly healthy while the payment network behind it is not, which is why the reader often looks online while transactions fail. issquareup.com reports hardware, point of sale and online payments as distinct components, so it identifies which layer is actually failing.
How long do Square outages usually last?
Most incidents are resolved within a couple of hours, though payment incidents attract attention quickly because they stop trade immediately. Subscribing to updates on issquareup.com is more reliable than refreshing the terminal, since the status page is updated as the incident progresses rather than only at resolution.

How we measure this

  • We request Square's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Square publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Square goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required