Skip to content

Outage tracker / Squarespace

Is Squarespace down?

I'm having a problem

Vendor reports no incidentWhat Squarespace reports

Squarespace reports no incident on its status page.

As of the last successful poll, 2026-10-22 21:48 UTC.

Squarespace'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 Squarespace pass from all 10 regions we check.

As of Oct 22, 2026, 9:50 PM UTC, RealUptime's checks of Squarespace passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Oct 22, 2026, 9:50 PM UTC
US-East1111 msChecks passing
US-West709 msChecks passing
Europe969 msChecks passing
Asia-Pacific2211 msChecks passing
US-Central616 msChecks passing
Canada851 msChecks passing
UK432 msChecks passing
Southeast Asia1590 msChecks passing
Australia3464 msChecks passing
South America2424 msChecks passing
their status pagetheir claim, not our reading

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

from Squarespace's own status page, checked Oct 22, 2026, 9:33 PM UTC
Squarespace's own status page shows no incident, and our checks of Squarespace pass right now.

Squarespace's own component breakdown, as they publish it

  • Site LoadingOperational
  • Site EditingOperational
  • CommerceOperational
  • DomainsOperational
  • Email CampaignsOperational
  • Acuity SchedulingOperational
  • Accounts & BillingOperational
  • AnalyticsOperational
  • Google WorkspaceOperational
  • Third Party ServicesOperational
  • Developer PlatformOperational
  • Squarespace HelpOperational
  • ForumOperational

These are Squarespace's components, named and scored by Squarespace. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Squarespace'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.

Squarespace response time, by region

US-East
1.2sp95 · 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-09-23 UTC: p95 566ms2026-09-24 UTC: p95 612ms2026-09-25 UTC: p95 457ms2026-09-26 UTC: p95 495ms2026-09-27 UTC: p95 487ms2026-09-28 UTC: p95 479ms2026-09-29 UTC: p95 300ms2026-09-30 UTC: p95 380ms2026-10-01 UTC: p95 575ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 476ms2026-10-04 UTC: p95 453ms2026-10-05 UTC: p95 531ms2026-10-06 UTC: p95 526ms2026-10-07 UTC: p95 502ms2026-10-08 UTC: p95 455ms2026-10-09 UTC: p95 423ms2026-10-10 UTC: p95 454ms2026-10-11 UTC: p95 503ms2026-10-12 UTC: p95 457ms2026-10-13 UTC: p95 527ms2026-10-14 UTC: p95 573ms2026-10-15 UTC: p95 699ms2026-10-16 UTC: p95 546ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 898ms2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.2s
Sep 23Oct 7Oct 22
US-West
1.4sp95 · 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-23 UTC: p95 544ms2026-09-24 UTC: p95 658ms2026-09-25 UTC: p95 759ms2026-09-26 UTC: p95 625ms2026-09-27 UTC: p95 710ms2026-09-28 UTC: p95 677ms2026-09-29 UTC: p95 852ms2026-09-30 UTC: p95 697ms2026-10-01 UTC: p95 695ms2026-10-02 UTC: p95 612ms2026-10-03 UTC: p95 680ms2026-10-04 UTC: p95 816ms2026-10-05 UTC: p95 781ms2026-10-06 UTC: p95 829ms2026-10-07 UTC: p95 719ms2026-10-08 UTC: p95 637ms2026-10-09 UTC: p95 691ms2026-10-10 UTC: p95 699ms2026-10-11 UTC: p95 748ms2026-10-12 UTC: p95 712ms2026-10-13 UTC: p95 711ms2026-10-14 UTC: p95 805ms2026-10-15 UTC: p95 669ms2026-10-16 UTC: p95 662ms2026-10-17 UTC: p95 860ms2026-10-18 UTC: p95 902ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
Europe
1.4sp95 · 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-09-23 UTC: p95 556ms2026-09-24 UTC: p95 438ms2026-09-25 UTC: p95 566ms2026-09-26 UTC: p95 519ms2026-09-27 UTC: p95 541ms2026-09-28 UTC: p95 760ms2026-09-29 UTC: p95 920ms2026-09-30 UTC: p95 673ms2026-10-01 UTC: p95 695ms2026-10-02 UTC: p95 330ms2026-10-03 UTC: p95 657ms2026-10-04 UTC: p95 690ms2026-10-05 UTC: p95 604ms2026-10-06 UTC: p95 620ms2026-10-07 UTC: p95 693ms2026-10-08 UTC: p95 598ms2026-10-09 UTC: p95 485ms2026-10-10 UTC: p95 483ms2026-10-11 UTC: p95 657ms2026-10-12 UTC: p95 668ms2026-10-13 UTC: p95 488ms2026-10-14 UTC: p95 421ms2026-10-15 UTC: p95 453ms2026-10-16 UTC: p95 541ms2026-10-17 UTC: p95 677ms2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s
Sep 23Oct 7Oct 22
Asia-Pacific
2.5sp95 · 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-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.2s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.9s2026-09-29 UTC: p95 2.0s2026-09-30 UTC: p95 2.1s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.8s2026-10-06 UTC: p95 1.8s2026-10-07 UTC: p95 1.8s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.5s
Sep 23Oct 7Oct 22
US-Central
897msp95 · 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-09-23 UTC: p95 608ms2026-09-24 UTC: p95 396ms2026-09-25 UTC: p95 480ms2026-09-26 UTC: p95 564ms2026-09-27 UTC: p95 493ms2026-09-28 UTC: p95 613ms2026-09-29 UTC: p95 437ms2026-09-30 UTC: p95 439ms2026-10-01 UTC: p95 633ms2026-10-02 UTC: p95 599ms2026-10-03 UTC: p95 543ms2026-10-04 UTC: p95 604ms2026-10-05 UTC: p95 682ms2026-10-06 UTC: p95 634ms2026-10-07 UTC: p95 549ms2026-10-08 UTC: p95 585ms2026-10-09 UTC: p95 572ms2026-10-10 UTC: p95 718ms2026-10-11 UTC: p95 408ms2026-10-12 UTC: p95 612ms2026-10-13 UTC: p95 664ms2026-10-14 UTC: p95 606ms2026-10-15 UTC: p95 813ms2026-10-16 UTC: p95 501ms2026-10-17 UTC: p95 953ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 897ms
Sep 23Oct 7Oct 22
Canada
1.1sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 522ms2026-09-24 UTC: p95 547ms2026-09-25 UTC: p95 399ms2026-09-26 UTC: p95 532ms2026-09-27 UTC: p95 494ms2026-09-28 UTC: p95 509ms2026-09-29 UTC: p95 524ms2026-09-30 UTC: p95 569ms2026-10-01 UTC: p95 609ms2026-10-02 UTC: p95 789ms2026-10-03 UTC: p95 644ms2026-10-04 UTC: p95 665ms2026-10-05 UTC: p95 621ms2026-10-06 UTC: p95 745ms2026-10-07 UTC: p95 564ms2026-10-08 UTC: p95 556ms2026-10-09 UTC: p95 576ms2026-10-10 UTC: p95 431ms2026-10-11 UTC: p95 468ms2026-10-12 UTC: p95 593ms2026-10-13 UTC: p95 605ms2026-10-14 UTC: p95 629ms2026-10-15 UTC: p95 664ms2026-10-16 UTC: p95 608ms2026-10-17 UTC: p95 940ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
UK
1.1sp95 · 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-09-23 UTC: p95 556ms2026-09-24 UTC: p95 732ms2026-09-25 UTC: p95 652ms2026-09-26 UTC: p95 533ms2026-09-27 UTC: p95 562ms2026-09-28 UTC: p95 450ms2026-09-29 UTC: p95 547ms2026-09-30 UTC: p95 487ms2026-10-01 UTC: p95 368ms2026-10-02 UTC: p95 570ms2026-10-03 UTC: p95 476ms2026-10-04 UTC: p95 486ms2026-10-05 UTC: p95 464ms2026-10-06 UTC: p95 504ms2026-10-07 UTC: p95 434ms2026-10-08 UTC: p95 590ms2026-10-09 UTC: p95 522ms2026-10-10 UTC: p95 376ms2026-10-11 UTC: p95 275ms2026-10-12 UTC: p95 360ms2026-10-13 UTC: p95 436ms2026-10-14 UTC: p95 504ms2026-10-15 UTC: p95 584ms2026-10-16 UTC: p95 478ms2026-10-17 UTC: p95 704ms2026-10-18 UTC: p95 834ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 958ms2026-10-22 UTC: p95 1.1s
Sep 23Oct 7Oct 22
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-09-23 UTC: p95 955ms2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 906ms2026-10-07 UTC: p95 982ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 696ms2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.7s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.9s
Sep 23Oct 7Oct 22
Australia
3.6sp95 · 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-09-23 UTC: p95 2.1s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 2.2s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 2.0s2026-10-02 UTC: p95 2.0s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 2.4s2026-10-06 UTC: p95 2.6s2026-10-07 UTC: p95 2.6s2026-10-08 UTC: p95 2.5s2026-10-09 UTC: p95 2.4s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.3s2026-10-16 UTC: p95 2.4s2026-10-17 UTC: p95 3.4s2026-10-18 UTC: p95 4.1s2026-10-19 UTC: p95 4.4s2026-10-20 UTC: p95 4.1s2026-10-21 UTC: p95 4.1s2026-10-22 UTC: p95 3.6s
Sep 23Oct 7Oct 22
South America
3.5sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 2.4s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.8s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 1.8s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.8s2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 3.0s2026-10-21 UTC: p95 3.4s2026-10-22 UTC: p95 3.5s
Sep 23Oct 7Oct 22

Check your own site while you wait on Squarespace

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 Squarespace. It cannot diagnose Squarespace's own systems.

What we measured, function by function

Squarespace answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

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

Get an email when Squarespace reports an incident

Email me when Squarespace 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 Squarespace'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: 1111msstatus code: 401checked: Oct 22, 2026, 9:45 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Squarespace normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 709msstatus code: 401checked: Oct 22, 2026, 9:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Squarespace normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 616msstatus code: 401checked: Oct 22, 2026, 9:39 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Squarespace normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 851msstatus code: 401checked: Oct 22, 2026, 9:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Squarespace normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2424msstatus code: 401checked: Oct 22, 2026, 9:35 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Squarespace 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: 969msstatus code: 401checked: Oct 22, 2026, 9:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Squarespace normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 432msstatus code: 401checked: Oct 22, 2026, 9:41 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Squarespace 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: 2211msstatus code: 401checked: Oct 22, 2026, 9:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Squarespace normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1590msstatus code: 401checked: Oct 22, 2026, 9:43 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Squarespace normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 3464msstatus code: 401checked: Oct 22, 2026, 9:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Squarespace 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 Squarespace, 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 Squarespace yet, which is not evidence that nothing is wrong.

Recent probe events

Acuity Scheduling / Service temporarily unavailable, 1mdeclared on their status page2026-10-21
Squarespace loading and editing Issues, 48mdeclared on their status page2026-09-28
Acuity Scheduling Admin Mobile app crashing unexpectedly after iOS 27 update, 94h 49mdeclared on their status page2026-09-18
Acuity Scheduling / Client Scheduling Page showing "SORRY" error, 1mdeclared on their status page2026-09-08
Acuity Scheduling - Unable to Connect to Meta, 17h 43mdeclared on their status page2026-08-20
Acuity Scheduling / Delayed Google calendar sync, 2h 4mdeclared on their status page2026-08-20
Acuity Scheduling Service Disruption, 17mdeclared on their status page2026-08-12
Connectivity Issues, 1h 27mdeclared on their status page2026-07-29

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

We have been measuring Squarespace since August 22, 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 Squarespace covering any window you pick, with our check readings and Squarespace's own claim at the time, side by side.

Full check history for Squarespace: 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

Squarespace uptime by RealUptime's checksLive, from this page's own readings.
[![Squarespace uptime by RealUptime's checks](https://realuptime.io/outages/squarespace/badge.svg?days=30)](https://realuptime.io/outages/squarespace)
<a href="https://realuptime.io/outages/squarespace"><img src="https://realuptime.io/outages/squarespace/badge.svg?days=30" alt="Squarespace uptime by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 Squarespace down?", https://realuptime.io/outages/squarespace. 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: live API
https://api.squarespace.com/1.0/authorization/website
secondary
https://www.squarespace.com/
secondary
https://status.squarespace.com/api/v2/status.json

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: api.squarespace.com

RealUptime is not affiliated with Squarespace; the name identifies what we checked, and nothing here speaks for Squarespace's own team. We send a single web request to Squarespace from 10 regions on our own schedule and time the response. We do not see inside Squarespace's systems, do not use an account or real transaction, and are not the same signal Squarespace's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Squarespace 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.