Squarespace: Acuity Scheduling: Emergency Maintenance
Affected components: Acuity Scheduling
Timeline of updates
- scheduled
Acuity Scheduling will be undergoing maintenance during this time.
- in progressEdited
Emergency maintenance is currently in progress. We will provide updates as necessary.
- in progress
To protect your data, we've taken Acuity offline while we address PHP2SHELL, a critical security vulnerability rated 9.2 out of 10 for severity. It affects popular web software, including tools Acuity relies on, and by some estimates up to 70% of websites are exposed.
We're moving as fast as we can. Part of the fix comes from the makers of that software, so as their patches are released, we deploy them, test them and confirm they've actually closed the gap. We'll bring Acuity back once that's done.
We know how much you depend on us, and we're sorry for the disruption.
- verifying
Verification is currently underway for the maintenance items.
Changes Rewindex caught on this incident
- Incident updated: Acuity Scheduling: scheduled maintenance
- Incident silently edited: Acuity Scheduling: Emergency Maintenance
- Incident updated: Acuity Scheduling: Emergency Maintenance
- Incident updated: Acuity Scheduling: Emergency Maintenance
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e3a0ca533fae79ab…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).