Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Sitespect outage history

    46 recorded Sitespect incidents since August 2017, with official updates, affected components, duration and resolution information.

    Back to current status

    SiteSpect Cloud Alert - EU POPs Service Degradation

    Started October 2, 2025 at 2:29 PM UTC · 2h 9m

    OutageMajor incident
    Affected components
    LON I - London, United KingdomLON II - London, United Kingdom
    1. October 2, 2025 at 2:29 PM UTCinvestigating

      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. October 2, 2025 at 2:31 PM UTCidentified

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

    3. October 2, 2025 at 3:16 PM UTCmonitoring

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

    4. October 2, 2025 at 4:38 PM UTCresolved

      This incident has been resolved.

    SiteSpect Cloud Alert - Automated bypass in effect

    Started February 26, 2025 at 7:14 PM UTC · 5h 27m

    Pending
    Affected components
    ATL - Atlanta, GA, United StatesDAL - Dallas, TX, United StatesCHG - Chicago, IL, United StatesLON I - London, United KingdomLAX - Los Angeles, CA, United StatesSJE - San Jose, CA, United StatesAMS - Amsterdam, NetherlandsNYJ - Secaucus, NJ, United StatesLON II - London, United Kingdom
    1. February 26, 2025 at 7:14 PM UTCinvestigating

      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. February 26, 2025 at 7:26 PM UTCidentified

      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. February 26, 2025 at 7:56 PM UTCmonitoring

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

    4. February 27, 2025 at 12:40 AM UTCresolved

      This incident has been resolved.

    SiteSpect Cloud - reduced points of presence availability

    Started November 29, 2024 at 3:41 PM UTC · 1h 39m

    Pending
    Affected components
    LON I - London, United KingdomAMS - Amsterdam, NetherlandsNYJ - Secaucus, NJ, United StatesLON II - London, United Kingdom
    1. November 29, 2024 at 3:41 PM UTCinvestigating

      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. November 29, 2024 at 4:12 PM UTCmonitoring

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

    3. November 29, 2024 at 5:20 PM UTCresolved

      This incident has been resolved.

    Traffic rerouted from Amsterdam POP

    Started September 25, 2024 at 12:36 PM UTC · 1h 45m

    Pending
    Affected components
    AMS - Amsterdam, Netherlands
    1. September 25, 2024 at 12:36 PM UTCmonitoring

      On Sep 25th between 11:31 UTC to 11:45 UTC and between 12:02 UTC and 12:08 UTC, Amsterdam POP experienced degraded performance. The issue has been mitigated and we are actively investigating this incident. Site traffic has been automatically routed away to the most optimal POP. Typically site visitor’s browsers react to this change within 1 to 30 seconds. During this time period, end users may have experienced extended page load times. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active. Please expect next update within one hour. Reach out to our SiteSpect Help Desk at [email protected] if you have any questions.

    2. September 25, 2024 at 2:21 PM UTCresolved

      This incident has been resolved.

    Traffic rerouted from NYJ POP

    Started April 2, 2024 at 6:47 PM UTC · 1h 0m

    Pending
    Affected components
    NYJ - Secaucus, NJ, United States
    1. April 2, 2024 at 6:47 PM UTCmonitoring

      Between 15:12 UTC and 15:16 UTC on April 2nd, NYJ POP experienced degraded performance. The issue has been mitigated and we are actively investigating this incident. Site traffic has been automatically routed away to the most optimal POP. Typically site visitor’s browsers react to this change within 1 to 30 seconds. During this time period, end users may have experienced extended page load times. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active. Please expect next update within one hour. Reach out to our SiteSpect Help Desk at [email protected] if you have any questions.

    2. April 2, 2024 at 6:48 PM UTCmonitoring

      Starting at 16:37 UTC, traffic has been restored to NYJ POP. We will continue to monitor before closing out this incident.

    3. April 2, 2024 at 7:47 PM UTCresolved

      This incident has been resolved.

    Traffic rerouted from CHG POP

    Started January 15, 2024 at 12:29 PM UTC · 1d 7h

    IssuesMinor incident
    Affected components
    CHG - Chicago, IL, United States
    1. January 15, 2024 at 12:29 PM UTCinvestigating

      CHG POP experienced degraded performance between Jan 14th 17:52 GMT and Jan 14th 17:56 GMT. During this time, Site traffic has been automatically routed away to the most optimal POP. Typically site visitor’s browsers react to this change within 1 to 30 seconds. During this time period, end users may have experienced extended page load times. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    2. January 15, 2024 at 12:29 PM UTCidentified

      The issue has been identified and we are working with our data center provider to resolve. Traffic continues to route around this POP.

    3. January 15, 2024 at 9:54 PM UTCidentified

      We continue to work with our data center provider on the issue. Traffic continues to automatically route around this POP. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    4. January 16, 2024 at 12:14 PM UTCidentified

      The issue has been resolved. We are reviewing the health of the POP before sending live traffic back to it. Traffic continues to automatically route around this POP. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    5. January 16, 2024 at 7:07 PM UTCmonitoring

      Traffic has been restored to CHG POP. We will continue to monitor before closing out this incident.

    6. January 16, 2024 at 8:05 PM UTCresolved

      This incident has been resolved.

    Traffic rerouted from NYJ POP

    Started July 10, 2023 at 11:40 PM UTC · 7d 12h

    IssuesMinor incident
    Affected components
    NYJ - Secaucus, NJ, United States
    1. July 10, 2023 at 11:40 PM UTCinvestigating

      On Mon Jul 10th between 21:49 2023 UTC & 21:59 UTC and 22:33 UTC & 22:40 UTC, NYJ POP experienced degraded performance. We are actively investigating this incident to make sure it does not reoccur. Site traffic has been automatically routed away to the most optimal POP. Typically site visitor’s browsers react to this change within 1 to 30 seconds. During this time period, end users may have experienced extended page load times. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active. Please expect next update within one hour. Reach out to our SiteSpect Help Desk at [email protected] if you have any questions.

    2. July 11, 2023 at 12:51 AM UTCidentified

      The issue has been identified and we are working with our data center provider to resolve. Traffic continues to route around this POP.

    3. July 11, 2023 at 1:14 PM UTCidentified

      We continue to work with our data center provider on the issue. Traffic continues to automatically route around this POP. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    4. July 11, 2023 at 6:44 PM UTCidentified

      We have a path forward and we plan to restore this POP tomorrow morning (ET time). Thank you for your patience. Traffic continues to automatically route around this POP. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    5. July 11, 2023 at 8:34 PM UTCidentified

      The date of the restore has been postponed. When we have a firm date / time, we will update. Traffic continues to automatically route around this POP. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    6. July 17, 2023 at 3:55 PM UTCmonitoring

      Traffic has been restored to NYJ POP. We will continue to monitor before closing out this incident.

    7. July 18, 2023 at 12:03 PM UTCresolved

      This incident has been resolved.

    Issue with reporting

    Started October 6, 2022 at 12:17 PM UTC · 3h 9m

    IssuesMinor incident
    Affected components
    Control Panel
    1. October 6, 2022 at 12:17 PM UTCinvestigating

      SiteSpect is aware of an issue that is causing some reports to not load. This has no impact to campaigns, live traffic or data. SiteSpect engineers are actively working on a fix. If you have any questions please reach out to [email protected].

    2. October 6, 2022 at 1:56 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. October 6, 2022 at 2:08 PM UTCmonitoring

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

    4. October 6, 2022 at 3:27 PM UTCresolved

      This incident has been resolved.

    Control Panel slowness

    Started December 27, 2021 at 3:12 PM UTC · 4h 48m

    OutageMajor incident
    Affected components
    Control Panel
    1. December 27, 2021 at 3:12 PM UTCidentified

      SiteSpect is aware of an issue that is causing the control panel to be intermittently slow. This has no impact to campaigns, live traffic or data. SiteSpect engineers are actively working on a fix. If you have any questions please reach out to [email protected].

    2. December 27, 2021 at 6:54 PM UTCmonitoring

      SiteSpect engineers have applied a fix and we will monitor.

    3. December 27, 2021 at 8:00 PM UTCresolved

      This incident has been resolved.

    Log4Shell Vulnerability

    Started December 13, 2021 at 12:42 AM UTC · 0m

    Pending
    Affected components
    Forte Cloud
    1. December 13, 2021 at 12:42 AM UTCresolved

      SiteSpect application is not impacted by the recent Log4Shell vulnerabilities (CVE-2021-44228, CVE-2021-45046, and CVE-2021-45105) because it does not utilize the Log4j project. If you have any questions, please reach out to us at [email protected] .

    Reporting Delay

    Started November 2, 2021 at 8:13 PM UTC · 1h 36m

    Pending
    Affected components
    Reporting Data
    1. November 2, 2021 at 8:13 PM UTCinvestigating

      Starting at approximately 12:38 Eastern Time, SiteSpect Cloud started experiencing a reporting delay. SiteSpect engineers have identified the issue and are actively working on resolving the incident. While reporting data may be delayed, there is no loss of reporting data, nor disruption to Control Panel access, and all testing and optimization campaigns remain active. Please reach out to our SiteSpect Help Desk at [email protected] if you have any questions.

    2. November 2, 2021 at 9:16 PM UTCmonitoring

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

    3. November 2, 2021 at 9:49 PM UTCresolved

      This incident has been resolved.

    Widespread Global Internet Outage

    Started July 22, 2021 at 4:26 PM UTC · 54m

    Pending
    Affected components
    Forte Cloud
    1. July 22, 2021 at 4:26 PM UTCinvestigating

      A widespread global internet outage began at approximately 11:37 am eastern time. It is affecting a number of large websites around the world, both SiteSpect clients and non-SiteSpect clients. We are watching the issue and will update this with any news and updates.

    2. July 22, 2021 at 5:20 PM UTCresolved

      The issue has been identified by Akamai as affecting their Edge DNS customers. A fix has been implemented by Akamai at approximately 12:45pm eastern time and service is resuming normal operations.

    Reporting delay

    Started May 18, 2021 at 2:55 PM UTC · 1h 4m

    IssuesMinor incident
    Affected components
    Reporting Data
    1. May 18, 2021 at 2:55 PM UTCinvestigating

      Starting at approximately 13:55 UTC, SiteSpect Cloud started experiencing a reporting delay. SiteSpect engineers have identified the issue and are actively working on resolving the incident. While reporting data may be delayed, there is no loss of reporting data, nor disruption to Control Panel access, and all testing and optimization campaigns remain active. Please expect an update within the next two hours. Reach out to our SiteSpect Help Desk at [email protected] if you have any questions.

    2. May 18, 2021 at 3:03 PM UTCmonitoring

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

    3. May 18, 2021 at 3:59 PM UTCresolved

      This incident has been resolved.

    SiteSpect Helpdesk Email Support Issue

    Started December 2, 2020 at 6:11 PM UTC · 1h 8m

    OutageMajor incident
    Affected components
    Forte Helpdesk System
    1. December 2, 2020 at 6:11 PM UTCinvestigating

      We are currently experiencing an issue accessing Helpdesk support tickets submitted via email. We are working with our CRM provider on a resolution. If you have a support need, please call the SiteSpect Helpdesk at 1-844-859-1900. Thank you!

    2. December 2, 2020 at 7:19 PM UTCresolved

      This incident has been resolved.

    SiteSpect Initiating Bypass

    Started March 25, 2020 at 4:39 PM UTC · 2h 39m

    IssuesMinor incident
    Affected components
    Forte Cloud
    1. March 25, 2020 at 4:39 PM UTCinvestigating

      At approximately 16:15 UTC, the SiteSpect Engineering team was alerted to a potential issue and promptly started an investigation. In effort to prevent any service degradation, we are initiating bypass for all clients. We will update the status page as our investigation progresses.

    2. March 25, 2020 at 6:07 PM UTCidentified

      The SiteSpect Engineering team has identified the issue and are currently working on a solution. We will continue to keep you updated.

    3. March 25, 2020 at 7:18 PM UTCresolved

      SiteSpect has implemented the solution. Service was restored at approximately 18:30 UTC.

    4. March 25, 2020 at 9:14 PM UTCpostmortem

      **SiteSpect Cloud Incident RCA: 25 March 2020** At 16:07 UTC, SiteSpect Engineering was alerted to an issue involving our DNS service. At approximately 16:40 UTC, SiteSpect decided to initiate a cloud wide bypass to mitigate any potential service degradation. At 18:00 UTC, SiteSpect implemented a solution in our staging environments. At approximately 18:30 UTC, the solution was implemented in production and SiteSpect service was restored for all SiteSpect Cloud customers. The investigation uncovered that the third party service used by DNS "bind" software \([dlv.isc.org](http://dlv.isc.org)\) had inadvertently removed their own DNS A record, which prevented the SiteSpect platform from resolving origin hostnames. Besides SiteSpect, this impacted many other organizations worldwide. SiteSpect implemented a workaround to resolve the issue specifically for SiteSpect Cloud. The SiteSpect solution was implemented prior to ISC issuing a correction for the issue around 21:30 UTC. Despite the issue being fixed by ISC, SiteSpect has decided to discontinue use of the affected feature set. This will not affect the service level or how Customers are able to use the platform.

    Helpdesk Email Issue

    Started February 24, 2020 at 11:47 AM UTC · 52m

    IssuesMinor incident
    Affected components
    Forte Helpdesk System
    1. February 24, 2020 at 11:47 AM UTCinvestigating

      Due to an issue with our helpdesk provider, emails to [email protected] are not working. For now, please call us instead: * US: +1 (800) 683-9832 * UK: +44 (0) 20 3239 8591 * NL: +31 20 82 020 82 * DE: +49 893 803 8076 * ES: +34 911 239 221

    2. February 24, 2020 at 12:38 PM UTCinvestigating

      We are continuing to investigate this issue.

    3. February 24, 2020 at 12:39 PM UTCresolved

      This incident has been resolved.

    Issue with logging into control panel

    Started January 2, 2020 at 3:06 PM UTC · 0m

    Pending
    Affected components
    Control Panel
    1. January 2, 2020 at 3:06 PM UTCresolved

      At approximately 3:15 AM Eastern time, SiteSpect’s engineering team was alerted to an issue that affected some users trying to log in to the platform. Investigation was promptly initiated and a fix determined and deployed at approximately 5:40 AM Eastern time. The issue only affected login capability and had no effect on campaigns, data or other platform functions. This issue is now resolved. If you have any questions please reach out to [email protected].

    UK Phone Number problem

    Started December 20, 2019 at 1:00 PM UTC · 2h 5m

    IssuesMinor incident
    Affected components
    Forte Phone system
    1. December 20, 2019 at 2:57 PM UTCinvestigating

      Our UK telephone number (+442032398591) is currently not working, and we are investigating the problem. Customers needing support are, for the time being, requested to dial our US number +1 6178591900 or email [email protected] whilst we work to resolve the problem. We apologize for the inconvenience.

    2. December 20, 2019 at 3:05 PM UTCresolved

      This issue has been resolved, and all phone contacts are working correctly.

    Traffic re-routed from LON2 POP

    Started October 24, 2019 at 4:16 PM UTC · 2h 30m

    IssuesMinor incident
    Affected components
    LON II - London, United KingdomForte Cloud
    1. October 24, 2019 at 4:16 PM UTCinvestigating

      Between 15:20 UTC and 15:45 UTC, the Lon2 POP experienced degraded performance. The issue was mitigated by SiteSpect engineers and we are actively investigating this incident. Site traffic has been automatically routed away to the most optimal POP. Typically site visitor’s browsers react to this change within 30 to 60 seconds. During this time period, end users may have experienced extended page load times. There is no disruption to Control Panel access, and all testing and optimization campaigns remain active.

    2. October 24, 2019 at 4:29 PM UTCmonitoring

      The LON2 POP has been stabilized. SiteSpect engineers continue to monitor before restoring traffic.

    3. October 24, 2019 at 6:15 PM UTCmonitoring

      Traffic has been restored and SiteSpect engineers continue to monitor.

    4. October 24, 2019 at 6:45 PM UTCresolved

      This incident has been resolved.

    Problem with Single Sign On (SSO) to SiteSpect Cloud

    Started October 24, 2019 at 2:00 PM UTC · 4h 44m

    IssuesMinor incident
    Affected components
    Control Panel
    1. October 24, 2019 at 2:00 PM UTCinvestigating

      Single Sign On (SSO) to SiteSpect Cloud is currently experiencing problems, and users who use this authentication method may not be able to login. We are actively investigating this issue with our 3rd party SSO provider and expect to post an update shortly. We apologize for the inconvenience.

    2. October 24, 2019 at 2:52 PM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. October 24, 2019 at 6:44 PM UTCresolved

      This incident has been resolved.