Live

Acuity Scheduling: Possible Emergency Maintenance

MaintenanceOfficial update

On Thursday, November 19th, security updates are expected to be released for PHP, a technology Acuity uses. To apply any necessary updates, we may need to perform urgent maintenance on Acuity Scheduling shortly after the release, starting around 14:00 UTC. Acuity Scheduling may be unavailable during this maintenance. We understand that any disruption to software your business relies on is significant, and we do not take this lightly. We are committed to protecting our customers and their data. We will share more information as it becomes available.

The latest update from Squarespace.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Squarespace

Scheduled

On Thursday, November 19th, security updates are expected to be released for PHP, a technology Acuity uses. To apply any necessary updates, we may need to perform urgent maintenance on Acuity Scheduling shortly after the release, starting around 14:00 UTC. Acuity Scheduling may be unavailable during this maintenance. We understand that any disruption to software your business relies on is significant, and we do not take this lightly. We are committed to protecting our customers and their data. We will share more information as it becomes available.

Affected components

1
Acuity Scheduling

Squarespace in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

7

Median duration

17 h 43 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 days
median 17 h 43 min
90 days agoToday

Other Squarespace incidents

All incidents

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=squarespace
Slack
/feed subscribe https://outages.live/feed.xml?providers=squarespace

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane