Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Sitespect

    46 incidentes de Sitespect registrados desde agosto de 2017, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    SiteSpect Cloud Alert - EU POPs Service Degradation

    Comenzó 2 de octubre de 2025 a las 14:29 UTC · 2h 9m

    OutageIncidente mayor
    Componentes afectados
    LON I - London, United KingdomLON II - London, United Kingdom
    1. 2 de octubre de 2025 a las 14:29 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. 2 de octubre de 2025 a las 14:31 UTCidentified

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

    3. 2 de octubre de 2025 a las 15:16 UTCmonitoring

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

    4. 2 de octubre de 2025 a las 16:38 UTCresolved

      This incident has been resolved.

    SiteSpect Cloud Alert - Automated bypass in effect

    Comenzó 26 de febrero de 2025 a las 19:14 UTC · 5h 27m

    Pending
    Componentes afectados
    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. 26 de febrero de 2025 a las 19:14 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. 26 de febrero de 2025 a las 19:26 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. 26 de febrero de 2025 a las 19:56 UTCmonitoring

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

    4. 27 de febrero de 2025 a las 0:40 UTCresolved

      This incident has been resolved.

    SiteSpect Cloud - reduced points of presence availability

    Comenzó 29 de noviembre de 2024 a las 15:41 UTC · 1h 39m

    Pending
    Componentes afectados
    LON I - London, United KingdomAMS - Amsterdam, NetherlandsNYJ - Secaucus, NJ, United StatesLON II - London, United Kingdom
    1. 29 de noviembre de 2024 a las 15:41 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. 29 de noviembre de 2024 a las 16:12 UTCmonitoring

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

    3. 29 de noviembre de 2024 a las 17:20 UTCresolved

      This incident has been resolved.

    Traffic rerouted from Amsterdam POP

    Comenzó 25 de septiembre de 2024 a las 12:36 UTC · 1h 45m

    Pending
    Componentes afectados
    AMS - Amsterdam, Netherlands
    1. 25 de septiembre de 2024 a las 12:36 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. 25 de septiembre de 2024 a las 14:21 UTCresolved

      This incident has been resolved.

    Traffic rerouted from NYJ POP

    Comenzó 2 de abril de 2024 a las 18:47 UTC · 1h 0m

    Pending
    Componentes afectados
    NYJ - Secaucus, NJ, United States
    1. 2 de abril de 2024 a las 18:47 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. 2 de abril de 2024 a las 18:48 UTCmonitoring

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

    3. 2 de abril de 2024 a las 19:47 UTCresolved

      This incident has been resolved.

    Traffic rerouted from CHG POP

    Comenzó 15 de enero de 2024 a las 12:29 UTC · 1d 7h

    IssuesIncidente menor
    Componentes afectados
    CHG - Chicago, IL, United States
    1. 15 de enero de 2024 a las 12:29 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. 15 de enero de 2024 a las 12:29 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. 15 de enero de 2024 a las 21:54 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. 16 de enero de 2024 a las 12:14 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. 16 de enero de 2024 a las 19:07 UTCmonitoring

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

    6. 16 de enero de 2024 a las 20:05 UTCresolved

      This incident has been resolved.

    Traffic rerouted from NYJ POP

    Comenzó 10 de julio de 2023 a las 23:40 UTC · 7d 12h

    IssuesIncidente menor
    Componentes afectados
    NYJ - Secaucus, NJ, United States
    1. 10 de julio de 2023 a las 23:40 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. 11 de julio de 2023 a las 0:51 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. 11 de julio de 2023 a las 13:14 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. 11 de julio de 2023 a las 18:44 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. 11 de julio de 2023 a las 20:34 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. 17 de julio de 2023 a las 15:55 UTCmonitoring

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

    7. 18 de julio de 2023 a las 12:03 UTCresolved

      This incident has been resolved.

    Issue with reporting

    Comenzó 6 de octubre de 2022 a las 12:17 UTC · 3h 9m

    IssuesIncidente menor
    Componentes afectados
    Control Panel
    1. 6 de octubre de 2022 a las 12:17 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. 6 de octubre de 2022 a las 13:56 UTCidentified

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

    3. 6 de octubre de 2022 a las 14:08 UTCmonitoring

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

    4. 6 de octubre de 2022 a las 15:27 UTCresolved

      This incident has been resolved.

    Control Panel slowness

    Comenzó 27 de diciembre de 2021 a las 15:12 UTC · 4h 48m

    OutageIncidente mayor
    Componentes afectados
    Control Panel
    1. 27 de diciembre de 2021 a las 15:12 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. 27 de diciembre de 2021 a las 18:54 UTCmonitoring

      SiteSpect engineers have applied a fix and we will monitor.

    3. 27 de diciembre de 2021 a las 20:00 UTCresolved

      This incident has been resolved.

    Log4Shell Vulnerability

    Comenzó 13 de diciembre de 2021 a las 0:42 UTC · 0m

    Pending
    Componentes afectados
    Forte Cloud
    1. 13 de diciembre de 2021 a las 0:42 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

    Comenzó 2 de noviembre de 2021 a las 20:13 UTC · 1h 36m

    Pending
    Componentes afectados
    Reporting Data
    1. 2 de noviembre de 2021 a las 20:13 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. 2 de noviembre de 2021 a las 21:16 UTCmonitoring

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

    3. 2 de noviembre de 2021 a las 21:49 UTCresolved

      This incident has been resolved.

    Widespread Global Internet Outage

    Comenzó 22 de julio de 2021 a las 16:26 UTC · 54m

    Pending
    Componentes afectados
    Forte Cloud
    1. 22 de julio de 2021 a las 16:26 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. 22 de julio de 2021 a las 17:20 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

    Comenzó 18 de mayo de 2021 a las 14:55 UTC · 1h 4m

    IssuesIncidente menor
    Componentes afectados
    Reporting Data
    1. 18 de mayo de 2021 a las 14:55 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. 18 de mayo de 2021 a las 15:03 UTCmonitoring

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

    3. 18 de mayo de 2021 a las 15:59 UTCresolved

      This incident has been resolved.

    SiteSpect Helpdesk Email Support Issue

    Comenzó 2 de diciembre de 2020 a las 18:11 UTC · 1h 8m

    OutageIncidente mayor
    Componentes afectados
    Forte Helpdesk System
    1. 2 de diciembre de 2020 a las 18:11 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. 2 de diciembre de 2020 a las 19:19 UTCresolved

      This incident has been resolved.

    SiteSpect Initiating Bypass

    Comenzó 25 de marzo de 2020 a las 16:39 UTC · 2h 39m

    IssuesIncidente menor
    Componentes afectados
    Forte Cloud
    1. 25 de marzo de 2020 a las 16:39 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. 25 de marzo de 2020 a las 18:07 UTCidentified

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

    3. 25 de marzo de 2020 a las 19:18 UTCresolved

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

    4. 25 de marzo de 2020 a las 21:14 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

    Comenzó 24 de febrero de 2020 a las 11:47 UTC · 52m

    IssuesIncidente menor
    Componentes afectados
    Forte Helpdesk System
    1. 24 de febrero de 2020 a las 11:47 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. 24 de febrero de 2020 a las 12:38 UTCinvestigating

      We are continuing to investigate this issue.

    3. 24 de febrero de 2020 a las 12:39 UTCresolved

      This incident has been resolved.

    Issue with logging into control panel

    Comenzó 2 de enero de 2020 a las 15:06 UTC · 0m

    Pending
    Componentes afectados
    Control Panel
    1. 2 de enero de 2020 a las 15:06 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

    Comenzó 20 de diciembre de 2019 a las 13:00 UTC · 2h 5m

    IssuesIncidente menor
    Componentes afectados
    Forte Phone system
    1. 20 de diciembre de 2019 a las 14:57 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. 20 de diciembre de 2019 a las 15:05 UTCresolved

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

    Traffic re-routed from LON2 POP

    Comenzó 24 de octubre de 2019 a las 16:16 UTC · 2h 30m

    IssuesIncidente menor
    Componentes afectados
    LON II - London, United KingdomForte Cloud
    1. 24 de octubre de 2019 a las 16:16 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. 24 de octubre de 2019 a las 16:29 UTCmonitoring

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

    3. 24 de octubre de 2019 a las 18:15 UTCmonitoring

      Traffic has been restored and SiteSpect engineers continue to monitor.

    4. 24 de octubre de 2019 a las 18:45 UTCresolved

      This incident has been resolved.

    Problem with Single Sign On (SSO) to SiteSpect Cloud

    Comenzó 24 de octubre de 2019 a las 14:00 UTC · 4h 44m

    IssuesIncidente menor
    Componentes afectados
    Control Panel
    1. 24 de octubre de 2019 a las 14:00 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. 24 de octubre de 2019 a las 14:52 UTCidentified

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

    3. 24 de octubre de 2019 a las 18:44 UTCresolved

      This incident has been resolved.