SiteSpect Outage History

SiteSpect is up right now

Pingoru has recorded 46 incidents for SiteSpect: 0 in the last 12 months and 0 in the last 90 days.

Source: status.sitespect.com

46incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012MayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct0%
Pingoru began tracking SiteSpect in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Major October 2, 2025 SiteSpect Cloud Alert - EU POPs Service Degradation 2h 9m LON I - London, United Kingdom, LON II - London, United Kingdom

Started Oct 02, 2025, 02:29 PM UTC· resolved Oct 02, 2025, 04:38 PM UTC

  1. investigating Oct 02, 2025, 02:29 PM UTC

    Starting at 14:01 UTC on 10/2/25,two SiteSpect Cloud points of presence in Europe became unavailable. Site traffic has been automatically routed away to the most optimal POP. If your SiteSpect configuration is set to restrict traffic only to European POPs, your site has been automatically bypassed. We are actively investigating and remediating this incident. You should expect an update within one hour. Please contact SiteSpect Help Desk at [email protected] if you have any questions.

  2. identified Oct 02, 2025, 02:31 PM UTC

    We have identified the issue and working to remediate. You should expect the next update within one hour.

  3. monitoring Oct 02, 2025, 03:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 02, 2025, 04:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 26, 2025 SiteSpect Cloud Alert - Automated bypass in effect 5h 26m AMS - Amsterdam, Netherlands, NYJ - Secaucus, NJ, United States, LON I - London, United Kingdom, ATL - Atlanta, GA, United States and 5 more

Started Feb 26, 2025, 07:14 PM UTC· resolved Feb 27, 2025, 12:40 AM UTC

  1. investigating Feb 26, 2025, 07:14 PM UTC

    Starting at 18:30 UTC on Feb 26th, multiple SiteSpect Cloud points of presence became unavailable. Your site has been automatically bypassed. We are actively investigating and remediating this incident. You should expect an update within one hour. Please contact SiteSpect Help Desk at [email protected] if you have any questions.

  2. identified Feb 26, 2025, 07:26 PM UTC

    We've identified the issue and have been restoring points of presence. Traffic is starting to route back through SiteSpect since 19:10 UTC.

  3. monitoring Feb 26, 2025, 07:56 PM UTC

    We continue to monitor after restoring all the points of presence.

  4. resolved Feb 27, 2025, 12:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 29, 2024 SiteSpect Cloud - reduced points of presence availability 1h 38m AMS - Amsterdam, Netherlands, NYJ - Secaucus, NJ, United States, LON I - London, United Kingdom, LON II - London, United Kingdom

Started Nov 29, 2024, 03:41 PM UTC· resolved Nov 29, 2024, 05:20 PM UTC

  1. investigating Nov 29, 2024, 03:41 PM UTC

    Starting at 14:31 UTC to 15:01 UTC on Nov 29th, several SiteSpect Cloud points of presence had elevated number of errors. Traffic has been automatically re-routed to the most optimal available POPs. Typically site visitor’s browsers react to this change within 1 to 30 seconds. Only visitors served by the affected POPs may have been impacted. There is no disruption to the Control Panel and all testing and optimization campaigns remain active. We are actively investigating and remediating the incident. You should expect an update within one hour. Please contact SiteSpect Help Desk at [email protected] if you have any questions.

  2. monitoring Nov 29, 2024, 04:12 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 29, 2024, 05:20 PM UTC

    This incident has been resolved.

Read the full incident report →