Squarespace incident

Delayed delivery of email messages from Squarespace.

Minor Resolved View vendor source →

Squarespace experienced a minor incident on May 19, 2025 affecting Accounts & Billing, lasting 4h 35m. The incident has been resolved; the full update timeline is below.

Started
May 19, 2025, 12:47 PM UTC
Resolved
May 19, 2025, 05:23 PM UTC
Duration
4h 35m
Detected by Pingoru
May 19, 2025, 12:47 PM UTC

Affected components

Accounts & Billing

Update timeline

  1. investigating May 18, 2025, 06:25 PM UTC

    We are currently investigating an issue where users are experiencing delays in receiving email messages from Squarespace.

  2. investigating May 18, 2025, 06:43 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 18, 2025, 07:01 PM UTC

    We are continuing to investigate this issue.

  4. investigating May 18, 2025, 07:15 PM UTC

    We are continuing to investigate this issue.

  5. investigating May 18, 2025, 07:30 PM UTC

    We are continuing to investigate this issue.

  6. investigating May 18, 2025, 07:46 PM UTC

    We are continuing to investigate this issue.

  7. investigating May 18, 2025, 08:01 PM UTC

    We are continuing to investigate this issue.

  8. investigating May 18, 2025, 08:17 PM UTC

    We are continuing to investigate this issue.

  9. investigating May 18, 2025, 08:32 PM UTC

    We are continuing to investigate this issue.

  10. investigating May 18, 2025, 08:51 PM UTC

    We are continuing to investigate this issue.

  11. investigating May 18, 2025, 11:14 PM UTC

    We are continuing to investigate this issue.

  12. investigating May 18, 2025, 11:34 PM UTC

    We are continuing to investigate this issue.

  13. investigating May 18, 2025, 11:53 PM UTC

    We are continuing to investigate this issue.

  14. investigating May 19, 2025, 12:10 AM UTC

    We are continuing to investigate this issue.

  15. investigating May 19, 2025, 12:31 AM UTC

    We are continuing to investigate this issue.

  16. investigating May 19, 2025, 01:10 AM UTC

    We are continuing to investigate this issue.

  17. investigating May 19, 2025, 01:31 AM UTC

    We are continuing to investigate this issue.

  18. investigating May 19, 2025, 01:53 AM UTC

    We are continuing to investigate this issue.

  19. investigating May 19, 2025, 02:15 AM UTC

    We are continuing to investigate this issue.

  20. investigating May 19, 2025, 02:50 AM UTC

    We are continuing to investigate this issue.

  21. investigating May 19, 2025, 03:11 AM UTC

    We are continuing to investigate this issue.

  22. investigating May 19, 2025, 03:39 AM UTC

    We are continuing to investigate this issue.

  23. investigating May 19, 2025, 04:05 AM UTC

    We are continuing to investigate this issue.

  24. investigating May 19, 2025, 04:24 AM UTC

    We are continuing to investigate this issue.

  25. investigating May 19, 2025, 04:41 AM UTC

    We are continuing to investigate this issue.

  26. investigating May 19, 2025, 05:21 AM UTC

    We are continuing to investigate this issue.

  27. investigating May 19, 2025, 05:36 AM UTC

    We are continuing to investigate this issue.

  28. investigating May 19, 2025, 05:51 AM UTC

    We are continuing to investigate this issue.

  29. investigating May 19, 2025, 06:09 AM UTC

    We are continuing to investigate this issue.

  30. investigating May 19, 2025, 06:25 AM UTC

    We are continuing to investigate this issue.

  31. investigating May 19, 2025, 06:46 AM UTC

    We are continuing to investigate this issue.

  32. investigating May 19, 2025, 07:03 AM UTC

    We are continuing to investigate this issue.

  33. monitoring May 19, 2025, 12:47 PM UTC

    This issue has been mitigated. We are continuing to monitor for any further issues.

  34. monitoring May 19, 2025, 01:36 PM UTC

    This issue has been mitigated. We are continuing to monitor for any further issues.

  35. monitoring May 19, 2025, 03:00 PM UTC

    This issue has been mitigated. We are continuing to monitor for any further issues.

  36. resolved May 19, 2025, 05:23 PM UTC

    This incident has been resolved.