Skip to main content
Square logo

Is Square Down?

No — Square is up
Square's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 204 ms

Right now

We could not read Square's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

squareup.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
204 ms
Checked

By region

  • Ashburn reachable, 233 ms
  • Chicago reachable, 234 ms
  • Frankfurt reachable, 120 ms
  • Johannesburg reachable, 375 ms
  • London reachable, 119 ms
  • Los Angeles reachable, 110 ms
  • São Paulo reachable, 274 ms
  • Tokyo reachable, 172 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Ashburn0 ms0 ms7 ms113 ms
Chicago0 ms1 ms6 ms113 ms
Frankfurt0 ms2 ms11 ms93 ms
Johannesburg0 ms1 ms16 ms345 ms
London0 ms3 ms9 ms84 ms
Los Angeles0 ms2 ms9 ms86 ms
São Paulo0 ms1 ms10 ms250 ms
Tokyo0 ms1 ms6 ms148 ms
We check that squareup.com loads, not every feature behind it. Test it yourself

History

Incidents Square reported

Since Oct 22, 16 days · from issquareup.com

Incidents
4
Major or critical
0
Median to resolve
57m
  1. Service Disruption

    minor ·

    lasted 4m
  2. Service Disruption

    minor ·

    lasted 1h 10m
  3. Service Disruption

    minor ·

    lasted 1h 25m
  4. Service Disruption

    minor ·

    lasted 44m

Square website availability

Measured by FlareWarden · squareup.com

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

Last 30 days

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

Measured by FlareWarden's own checks of squareup.com from multiple regions every 6 hours. Square's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Square itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Square goes down

We check Square every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required