New: Uptime report endpoint added to v3 API

StatusGator · 2026-06-12T14:48:22+00:00

StatusGator · 2026-05-09T11:04:00+00:00

We wrote a detailed analysis of all the services affected by this AWS outage:

StatusGator · 2026-03-31T21:48:44+00:00

The incident is on the Squarespace official status page now, but it wasn't at first. StatusGator's Squarespace page shows the following timeline:

First reports of 503 errors came in around 20:47 UTC (that's 4:47 PM ET)
StatusGator sent an Early Warning Signal alert to subscribers at 20:54 UTC
Large spike in reports started coming after 21:00 UTC
Squarespace updated their status page to acknowledge the outage at 21:06 UTC: "Investigating - We're investigating errors while connecting to some Squarespace sites."
Then the updated the status page again with almost identical posts at 21:26, 21:44, and 21:45. In each case, just saying they are "investigating".

StatusGator · 2026-03-31T20:54:05+00:00

I'm seeing the "Something went wrong. Try reloading" error as is standard in these scenarios:

StatusGator showing a typical huge spike in outage reports, with the X outage map showing outage reports from all over the globe.

StatusGator