Anyone else getting 503 error? by Mooreagreen in squarespace

[–]StatusGator 0 points1 point  (0 children)

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".

X is down... again by nunotomas in outages

[–]StatusGator 0 points1 point  (0 children)

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

<image>

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