# Squarespace: Major incident: Connectivity issues

**Summary:** Squarespace reported a major connectivity outage from 2026-03-31 21:06 UTC to 2026-03-31 22:01 UTC (55 min), now resolved. Approximately 28% of customer requests failed; visitors experienced slow loads or “Service Unavailable” errors affecting site loading, login, site editing, Campaigns, Domains, and Commerce. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-03-31 21:06 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/67y6zdv24lq2](https://stspg.io/67y6zdv24lq2)
- [Company: Squarespace](https://rewindex.com/company/squarespace.md)
- Versions: before (none: first archived) → after incident\_version:260/sdy4jchg1mb3@e0d0d7adb038
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Connectivity issues
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ postmortem
```

**4. Added: Start time**

```diff
+ 2026-03-31 21:06 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-03-31 22:01 UTC
```

**6. Added: Update** (investigating) · 2026-03-31 21:06 UTC

```diff
+ We're investigating errors while connecting to some Squarespace sites.
```

**7. Added: Update** (investigating) · 2026-03-31 21:26 UTC

```diff
+ We're investigating errors while connecting to some Squarespace sites.
```

**8. Added: Update** (monitoring) · 2026-03-31 21:44 UTC

```diff
+ We're investigating errors while connecting to some Squarespace sites.
```

**9. Added: Update** (monitoring) · 2026-03-31 21:45 UTC

```diff
+ We're investigating errors while connecting to some Squarespace sites.
```

**10. Added: Update** (monitoring) · 2026-03-31 21:49 UTC

```diff
+ Issue has been mitigated as of 5:36pm EDT. We are continuing to monitor for any further issues.
```

**11. Added: Update** (resolved) · 2026-03-31 22:01 UTC

```diff
+ This incident has been resolved.
```

**12. Added: Update** (postmortem) · 2026-04-07 17:41 UTC

```diff
+ 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-03-31 21:06 UTC | Major incident: Connectivity issues (this change) | outage |

All Squarespace changes: [timeline](https://rewindex.com/company/squarespace/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i93b2979d2255be · Markdown: https://rewindex.com/change/i93b2979d2255be.md · JSON: https://rewindex.com/api/v1/changes/i93b2979d2255be · Generated 2026-10-18T02:54:48.475Z