Acuity Scheduling Service Disruption
This incident has been resolved.
The latest update from Squarespace.
State
Resolved
Started
81 d ago
2026-08-12 22:55 UTC
Lasted
17 min
until 2026-08-12 23:12 UTC
Worst impact
Major outage
Timeline
2 updatesIdentified
17 min 100%
Updates
Times in UTCAs posted by Squarespace
This incident has been resolved.
We are currently experiencing a service disruption. Our Engineering team has identified the issue and is working to implement a solution. All users and services may be affected. We will provide an update as soon as possible.
Affected components
1Squarespace in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
9
Median duration
2 h 4 min
This incident
86% shorter than the median
Other Squarespace incidents
All incidentsSquarespace·Squarespace loading and editing Issues
This incident has been resolved.
Squarespace·Acuity Scheduling Admin Mobile app crashing unexpectedly after iOS 27 update
Access to the Acuity Scheduling app has been restored for users on iOS 27. Users can update to Acuity Scheduling version 98.0.0 via the Apple App Store to install the fix.
Squarespace·Acuity Scheduling - Unable to Connect to Meta
After reviewing the impact, we’ve confirmed that this issue is limited in scope and does not affect core functionality. We’re closing this Statuspage update. Customers who continue to experience the issue should contact Support.
Squarespace·Acuity Scheduling / Delayed Google calendar sync
The issue has been resolved.
Follow Squarespace
Your coding agent knows when Squarespace is down, and tells you when a failure is theirs, not yours. You can also get Squarespace incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "squarespace" and tell me if Squarespace has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=squarespace/feed subscribe https://outages.cc/feed.xml?providers=squarespaceFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane