- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 31of 100
What to do
Check whether you use Squarespace in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 55m it lasted.
Anything that failed between 2026-03-31 21:06 UTC and 2026-03-31 22:01 UTC may need a replay.Subscribe to Squarespace's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=squarespace works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Squarespace 7
- investigating
We're investigating errors while connecting to some Squarespace sites.
provider
- investigating
We're investigating errors while connecting to some Squarespace sites.
provider
- monitoring
We're investigating errors while connecting to some Squarespace sites.
provider
- monitoring
We're investigating errors while connecting to some Squarespace sites.
provider
- monitoring
Issue has been mitigated as of 5:36pm EDT. We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On Tuesday, March 31st, 2026, many Squarespace websites experienced unavailability for an aggregate of 53 minutes, between 4:43 PM and 5:36 PM EDT. During this incident, we failed to serve approximately 28% of customer requests. Site visitors saw slow loads or “Service Unavailable” errors impacting site loading, login, site editing, Campaigns, Domains, and our Commerce platform. At 4:43 PM EDT we performed a network configuration change in one of our points of presence \(PoP\). This change impacted critical networking equipment within that region. Our teams were notified immediately via automated alerts, internal reports, and additional customer reports. At 4:48 PM EDT our system automatically routed traffic off of this PoP. This action should have contained the impact. However, another region was already offline due to planned maintenance. As a result, the majority of our traffic was ultimately routed to a single PoP. In aggregate, this increased load overwhelmed our website lookup infrastructure in this region, severely impacting visitor requests. At 5:08 PM EDT, our teams resolved the original network configuration issue. We continued to see customer impact, so at 5:20 PM EDT we cleared the website lookup cache in the active region. This exacerbated the issue due to an additional misconfiguration within the lookup infrastructure. At 5:35 PM EDT we successfully routed traffic back onto the original PoP, which had fully recovered. By 5:36 PM EDT our systems were serving all customer requests normally. We deeply apologize for this incident. Ensuring Squarespace sites remain up and available is of the utmost importance to us. Our team has prioritized improvements to the mitigation of similar issues and scaling our edge capacity as necessary. Thank you for your patience.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-35413b6e44
Is Squarespace still down?
No, this incident was resolved 2026-03-31 22:01 UTC. For Squarespace's live state, see https://down.guide/squarespace.
How long did it last?
55m, from 2026-03-31 21:06 UTC to 2026-03-31 22:01 UTC, by the times Squarespace posted.
What was affected?
Squarespace named in us.
What caused it?
Squarespace hasn't published a root cause. If it does, it shows here.
Where does this come from?
Squarespace's official status page, https://status.squarespace.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.