Looking for an update now? Check the current status, or follow AlertSite for future changes.
78.4%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
80%
30
6
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
May 2026
Chrome 120 Now Live for Selenium Monitors on Public Locations
A fix has been implemented and we are monitoring the results.
investigating
We’re pleased to inform you that Chrome 120 is now live for Selenium monitors across all public locations. To start using Chrome 120, your team will need to upgrade both new and existing scripts to Java v11 and Selenium 3.x or 4.x. This update ensures improved stability, enhanced performance, and alignment with the latest browser standards.
Chrome 120 for Selenium monitors will also be made available on Private Nodes soon.
If you experience any issues or have questions, please reach out to our support team.
April 2026
Chrome 135 Now Live for DejaClick Monitors on Public Locations
We regret to inform you that, due to issues identified with Chrome version 135, we are temporarily disabling support for Chrome 135 until further notice. Please note that all lower browser versions will continue to remain available for use.
Our team is actively investigating the issue with the highest priority and working towards a resolution. We will share an update once the fix has been validated and support for Chrome 135 is restored.
We appreciate your understanding and patience.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We’re pleased to inform you that Chrome 135 is now live for DejaClick monitors across all public locations. You can now start using Chrome 135 without any additional action required. This update ensures improved stability, performance, and alignment with the latest browser standards.
Chrome 135 will also be made available on Private Nodes soon.
If you experience any issues or have questions, please reach out to our support team.
Legacy Incident Archive
22 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
March 2026
DejaClick Compatibility Issue with Latest Chrome Version
Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently experiencing an issue with the DejaClick extension on Google Chrome version 146.
DejaClick is not functioning as expected on Chrome version 146 . Users may encounter errors while loading scripts or interacting with the extension.
To ensure proper functionality, please use:
Chrome version 145 or earlier (≤145)
Our team is actively investigating the issue and working on a fix to support the latest Chrome versions. We will provide an update once a fix is available or additio...
November 2025
ReadyAPI v3.59 and TestEngine v1.32.0 Released – Compatibility & Upgrade Advisory
Source not attested
Last archived state: resolved
View archived record details
investigating
We're excited to announce the release of ReadyAPI v3.59 and TestEngine v1.32.0, now available on both Public and Private locations (v3.5.3) in AlertSite. Action Required: To take full advantage of these updates, please upgrade your Private Nodes to version 3.5.3. Important Notes: Some older ReadyAPI scripts that worked with ReadyAPI v1.9 may not function properly with ReadyAPI v3.59. However, most of these scripts have been observed to run successfully with TestEngine v1.32.0. If you encounte...
