> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/archived-release-notes/2026/2026-10-release-notes.md).

# Release Notes: October 2026

## 2026-10-30

### Manual Geolocation Configuration for Enterprise Agents

Enterprise Agents now support automatic and manual override of their geolocation setting. With automatic geolocation, ThousandEyes determines the agent's location from its public IP address. With manual override, you can select a location from the available cities, and ThousandEyes preserves it across agent check-ins, restarts, upgrades, and public IP changes. Other network details, including public IP address, ASN, and network prefix, continue to update automatically in either mode.

Existing agents use automatic geolocation by default. Switch an agent to manual override to keep a manually selected location.

Change the mode for an individual agent in its settings or update multiple agents with the bulk update option. The setting is available only in the ThousandEyes UI; you can't edit geolocation through the API. Agent clusters don't support automatic geolocation updates.

When you switch an agent from manual override to automatic geolocation, the geolocation lookup runs at the next agent check-in. The updated location is reflected in API results, path visualization, dashboards, and downstream services.

### New Agent Selector for Target Agent

Agent-to-agent tests now allow you to select a network interface for the target agent. This is useful when agents have multiple interfaces connected to separate networks, VRFs, or SD-WAN paths and the default interface is not the path you need to test. When you select **Target to Source** mode, the selected target agent interface is used as the source interface for that direction.

{% hint style="info" %}
The test continues to use the destination agent’s `Target for Tests` IP address as the target address, regardless of the selected interface.
{% endhint %}

For more information, see [Selecting a Target Agent Interface](https://docs.thousandeyes.com/product-documentation/tests/network-tests/agent-to-agent-test-overview#selecting-a-target-agent-interface).

### Jumbo Frame Support for Agent-to-Server and Agent-to-Agent Tests

ThousandEyes network tests provide deep network analysis through path MTU (PMTU) and TCP MSS measurements. This information can help troubleshoot enterprise network performance issues related to VPNs, IPv6, and tunneling. As more networks adopt IPv6 and jumbo-capable Ethernet, operators need to verify that larger frames can traverse the path. PMTU visibility can also help identify links with an incorrect MTU.

To address this need, Enterprise Agent network tests now support jumbo frames:

* For ping payload, agent-to-agent UDP tests accept configurable packet payloads from 30 to 9,188 bytes, while agent-to-server TCP/ICMP tests accept payloads from 1 to 9,188 bytes.
* For MSS, agent-to-agent TCP tests accept values from 30 to 9,176 bytes.

You can send jumbo frames from an Enterprise Agent if the host interface supports the configured frame size to examine the network path and identify where frames are dropped.

For more information, see [Testing Jumbo Frames with Enterprise Agents](https://docs.thousandeyes.com/product-documentation/tests/network-tests#testing-jumbo-frames-with-enterprise-agents).

## 2026-10-29

### Cisco Application Hosting Framework (CAF) Version 5.2.2

CAF version 5.2.2 has now been released. This release includes the latest `ca-certificates` and `ca-certificates-bundle` packages to address the eMudhra CA Key Compromise vulnerability. It also includes `te-agent` version 1.247.3.

For upgrade instructions, see [Upgrading Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/managing/upgrading-enterprise-agents#cisco-application-hosting).

For details about the vulnerability, see the [Cisco Security Advisory](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-emudhra-info-ScS22A1r).

### Advance Notice: Post-Quantum Cryptography Support

ThousandEyes is adopting post-quantum cryptography (PQC) to help protect customer telemetry and control channels against future quantum threats, including the risk that encrypted data collected today could be decrypted in the future. As part of Cisco’s QuantumSafe program, we are adopting NIST-standardized PQC and targeting general availability across in-scope services and agents by June 1, 2027.

We will begin enabling PQC cipher suites in production in January 2027. The rollout will use hybrid cryptographic methods that combine classical and quantum-safe algorithms and is designed to maintain compatibility and uninterrupted service during the transition.

The planned scope includes:

* **Web and API endpoints:** PQC-enabled TLS connections to public-facing endpoints.
* **ThousandEyes Agents:** PQC support on eligible operating systems for secure connections to the ThousandEyes platform and outbound connections to external services.
* **OpenTelemetry:** Updated cryptographic libraries supporting PQC algorithms.
* **Agents hosted on Cisco hardware:** Post-quantum-safe image signature validation aligned with Cisco’s validation pipeline.

Support resources, including knowledge base articles, will be available to help customers assess compatibility and prepare for the changes. For details, see the [Cisco ThousandEyes Post-Quantum Cryptography (PQC) Readiness Statement](https://trustportal.cisco.com/c/r/ctp/trust-portal.html?docclassification=bundle#/19680865172848810).

### Shape Monitoring Around What Matters with Test Scheduler

**Test Scheduler** gives you greater control over when supported Cloud Agent and Enterprise Agent tests run. Schedule tests by day and time, automatically enable and disable them within defined windows, and set expiration dates for temporary tests.

Align monitoring and unit use with your business and operational needs — whether you are covering retail hours, maintenance windows, project testing, or off-hour operations. With scheduling built into Test Settings, you can reduce manual lifecycle management and focus coverage where it creates the most value.

For adaptive coverage, **Interval Boost** automatically increases test frequency when ThousandEyes detects a higher probability of an issue, giving you more granular visibility when it matters. Because Interval Boost and recurring schedules cannot be active on the same test, choose the approach that best fits your monitoring goal.

Test expiration is not available in ThousandEyes for Government.

For details, see [Test Scheduler](https://docs.thousandeyes.com/product-documentation/tests/test-scheduler).

### Removal of Legacy OpenTelemetry Connection Type Attribute

Effective October 29, 2026, ThousandEyes for OpenTelemetry no longer emits the deprecated `thousandeyes.source.agent.connection.type` attribute for Endpoint Experience Local Network metrics in Data Model v2 on the commercial ThousandEyes platform. The attribute was [deprecated on July 7, 2026](https://docs.thousandeyes.com/release-notes/2026/2026-07-release-notes#id-2026-07-07).

If your dashboards, alerts, or telemetry processing use the legacy attribute, update them to use `network.connection.type`. Update filters that match legacy values: `Wireless` becomes `wifi`, `Ethernet` becomes `wired`, and `Modem` or `Cellular` becomes `cell`. Unrecognized connection types are reported as `unknown`. No action is required if you already use `network.connection.type`.

For more information, see [Endpoint Experience Local Network](https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/data-model/data-model-v2/metrics#endpoint-experience-local-network).

### Improved Calculator Design and Cost Estimates

We’ve refreshed the unit calculator’s visual design and added usability improvements to help customers estimate projected costs with greater ease and clarity.

* **Refreshed design:** The calculator now shares the visual style of the rest of the ThousandEyes platform and supports dark mode.
* **Clearer estimation guidance:** The calculator starts with a copy of your current test configuration for the selected account group, so you don’t need to build it from scratch. It estimates consumption over one full billing period, assuming the configuration stays unchanged throughout that period. The estimate excludes consumption to date in your current billing period.
* **Improved visibility:** The calculator makes your estimated unit consumption and the number of units in your plan more prominent.
* **Easier configuration:** Improved the Enterprise Agent selector for Legacy metered plans and removed the deprecated HTTP server interval option for page load tests.
* **Consistent calculations:** The calculator continues to calculate consumption for each test type as before, with no major changes to the underlying calculations.

![Calculator estimate and configuration in light mode](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-29caf13fccac0379493e3698075bb08c0800b619%2Fcalculator-light.png?alt=media)

![Calculator estimate and configuration in dark mode](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-44f7c3eaf4a8524f634a209a51bec714cc7735c6%2Fcalculator-dark.png?alt=media)

## 2026-10-28

### HTTP Server Test in Splunk Synthetic Monitoring — Generally Available

The Splunk Synthetic Monitoring integration is now generally available, helping ThousandEyes customers bring network and application teams together to troubleshoot performance issues.

With this integration, you can:

* **Create and import tests in Splunk.** Create and manage ThousandEyes HTTP Server tests, or import existing tests, directly in Splunk Observability Cloud.
* **Investigate application and network performance together.** View application results alongside ThousandEyes network measurements, and use the results in Splunk dashboards and detectors.
* **Continue your investigation in ThousandEyes.** Open the test in ThousandEyes for detailed network path analysis.

A Splunk Synthetic Monitoring subscription is required. For setup instructions and requirements, see [Splunk Synthetic Monitoring Integration](https://docs.thousandeyes.com/product-documentation/integration-guides/splunk-synthetic-monitoring-integration).

### Wireless Active Testing Dashboard Template

We have introduced the **Wireless Active Testing Dashboard** template. This dashboard helps you detect Wi-Fi issues by surfacing Wireless Active Testing results for selected agents or tags. Results include wireless connectivity, pre-connection testing, and network performance. For deployment instructions, see [Using the Dashboard Templates](https://docs.thousandeyes.com/product-documentation/dashboards/dashboard-templates).

### Private BGP Monitoring with Enterprise Agents

Local collection through Enterprise Agents is now generally available for private BGP monitoring. The new **BGP Route Collector** module extends the existing workflow to routes within your enterprise network, including routes with private AS numbers, private IP prefixes, or both.

ThousandEyes already supports private BGP monitoring through direct eBGP peering between your router and a ThousandEyes-hosted route collector, giving you your router's view of routes to internet destinations without an Enterprise Agent. This release adds the option to collect routes locally on an Enterprise Agent and send the telemetry to ThousandEyes over HTTPS. Both collection methods remain available.

* **Collect routing updates locally.** Peer your routers with an Enterprise Agent inside your security perimeter through local eBGP sessions. The agent sends routing telemetry to ThousandEyes over its existing secure, authenticated HTTPS connection.
* **Investigate routing changes.** Use BGP Route Visualization, historical analysis, Looking Glass, and alerts to review the routes received by the collector and compare routing events with network and application measurements.
* **Validate planned changes and recovery.** Review routing behavior during failovers, migrations, and maintenance, and confirm recovery after an incident.

For a comparison of both collection methods, see [Private BGP Monitoring](https://docs.thousandeyes.com/product-documentation/tests/bgp-tests/private-bgp-monitoring#choosing-a-collection-method). For local setup instructions, see [Configuring Private BGP Monitoring with Enterprise Agents](https://docs.thousandeyes.com/product-documentation/tests/bgp-tests/private-bgp-monitoring/configuring-an-enterprise-agent-with-bgp-route-collector).

### Endpoint Agent Health Is Generally Available

Endpoint Agent Health, previously known as Explainability Logging, is now generally available. For details, see the [Endpoint Agent Health documentation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/endpoint-agents/managing/endpoint-agent-health); for background, see the [Explainability Logging Open Beta announcement](https://docs.thousandeyes.com/release-notes/2026/2026-10-release-notes#id-2026-10-02).

### Stable Tag Selection for OpenTelemetry Streams

OpenTelemetry streams now follow selected tags by their stable IDs. Editing a selected tag's key or value preserves the test selection, so you do not need to update or recreate the integration. Updated tag metadata appears in exported telemetry after propagation.

For new API requests, use `tagId` in `tagMatch`. The legacy key/value selector format remains available for compatibility.

For more information, see [Tags and OpenTelemetry Streams](https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/tags-and-opentelemetry-streams).

## 2026-10-27

### Alert Optimizations Is Now Generally Available

Introduced [as a public beta in July](https://docs.thousandeyes.com/release-notes/2026/2026-07-release-notes#id-2026-07-16), [Alert Optimizations](https://docs.thousandeyes.com/product-documentation/alerts/alert-optimizations) is now generally available. With support for the ThousandEyes API v7, ThousandEyes MCP Server, and AI Assistant, you have more ways to find and understand recommendations that can reduce repeated alert noise.

Use [API v7](https://developer.cisco.com/docs/thousandeyes/v7/rules/) and the [ThousandEyes MCP Server](https://docs.thousandeyes.com/product-documentation/integration-guides/thousandeyes-mcp-server) to find alert rules with active optimizations and retrieve recommendation details. The AI Assistant can also find and explain recommendations, helping you bring alert optimization insights into your existing workflows.

These workflows provide read-only access. Apply, dismiss, or reject recommendations in the ThousandEyes platform.

Alert optimization filtering and details for the List Alert Rules and Get Alert Rule tools are not available in the ThousandEyes for Government instance. The AI Assistant is also not available in ThousandEyes for Government.

### Explore Dashboard Chart Data with Tooltips and Drill-Down

You can inspect data in Stacked Bar, Grouped Bar, and Pie dashboard widgets using tooltips and drill-down. Hover over a bar, stacked segment, or pie slice to inspect its values. Left-click to open the drill-down panel, or right-click to access **Drilldown** and supported **Filter by** actions. For details, see [Chart interactions and context menu](https://docs.thousandeyes.com/product-documentation/dashboards/troubleshooting-with-drill-down#chart-interactions-and-context-menu).

## 2026-10-23

### Migrating Your SSO Configuration

Organizations that use Single Sign-On (SSO) must migrate their identity provider (IdP) configuration and authentication routing rules to the Cisco Identity admin portal by November 6, 2026, to maintain access. An **Organization Admin** or a user with the *Edit security & authentication settings* permission can migrate.

Managed service providers are currently exempt and don’t need to migrate by November 6, 2026. ThousandEyes will share their migration instructions and timelines later.

#### What's Changing

Effective immediately, you can no longer configure SSO in the **Set Up Single Sign-On (SSO) Authentication** section in ThousandEyes under **Manage > Account Settings > Organization Settings**. The section remains visible and links to the Cisco Identity admin portal, where you can configure multiple IdPs, set authentication routing rules, and renew certificates. The **SCIM Settings** and **Just-In-Time Settings** sections remain configurable in ThousandEyes.

#### Before You Configure Your IdP

* **Provide a verified, stable user identifier.** Your IdP must send a verified email address or another stable, unique identifier, such as an immutable user ID. See [How SSO Works](https://docs.thousandeyes.com/product-documentation/user-management/authentication/configure-sso-with-cisco-account#how-it-works).
* **For SAML IdP-initiated logins, configure the RelayState URL.** Set it to `https://app.thousandeyes.com/login/cui/idp`. You can add a `fwd` parameter to direct users to a specific ThousandEyes page after login. See [Authentication redirects](https://docs.thousandeyes.com/product-documentation/user-management/authentication/configure-sso-with-cisco-account#authentication-redirects).
* **Review just-in-time (JIT) provisioning requirements.** See [Configure JIT Provisioning with Cisco Account](https://docs.thousandeyes.com/product-documentation/user-management/authentication/configure-sso-with-cisco-account/configure-jit-with-cisco-account).

#### Migrating Your SSO Configuration

{% hint style="warning" %}
Adding a break glass rule makes the migration effective and routes authentication for all users through the Cisco Identity admin portal. It doesn’t activate SSO.

Configure and test an IdP, then activate SSO. Without a usable IdP, users might be locked out.
{% endhint %}

Before you begin, prepare your IdP, gather the admins who manage your IdP and authentication routing rules, and schedule a maintenance window. Plan to complete setup in one session.

1. Log in to ThousandEyes with an account that has either the **Organization Admin** role or the *Edit security & authentication settings* permission.
2. Go to **Manage > Account Settings > Organization Settings**.
3. Select **Go to admin portal**.
4. Create and test a [break glass routing rule](https://docs.thousandeyes.com/product-documentation/user-management/authentication/configure-sso-with-cisco-account/configure-routing-rules#add-a-break-glass-routing-rule-dedicated-local-authentication-only) first. Make it the first matching rule for designated admins, and verify that they can sign in with local Cisco credentials. Users routed to an external IdP don’t automatically fall back to local authentication if that IdP is unavailable or misconfigured.
5. Follow the [SSO configuration guide](https://docs.thousandeyes.com/product-documentation/user-management/authentication/configure-sso-with-cisco-account) to configure your IdP and routing rules, then test your setup.

Try the [interactive walkthrough](https://demo.thousandeyes.com/s/Mx4AZQ) to preview the configuration process. For help, see [Contacting ThousandEyes Support](https://docs.thousandeyes.com/product-documentation/getting-started/getting-support-from-thousandeyes#contacting-support).

### Alert Optimizations in the ThousandEyes MCP Server

The ThousandEyes MCP server now gives your AI assistant access to [Alert Optimizations](https://docs.thousandeyes.com/product-documentation/alerts/alert-optimizations):

* `list_alert_rules` — Filter the list to alert rules that have, or do not have, an active alert optimization.
* `get_alert_rule` — If the alert rule has an active alert optimization, the response includes the recommendation and a link to review it in the ThousandEyes platform.

For example, you can ask your assistant "Which alert rules have alert optimizations?" and then ask it to explain the recommended change for a specific rule.

{% hint style="info" %}
The MCP server provides read-only access to alert optimizations. To apply, reject, or dismiss an alert optimization, use the ThousandEyes platform.
{% endhint %}

Alert optimization filtering and details are not available in the ThousandEyes for Government instance. For more information, see [ThousandEyes MCP Server](https://docs.thousandeyes.com/product-documentation/integration-guides/thousandeyes-mcp-server).

## 2026-10-22

### Advance Notice: Enterprise Agent Certificate Revocation Checks

Starting with the January 2027 Enterprise Agent release, Enterprise Agents will check server certificates for connections to the ThousandEyes platform against certificate revocation lists (CRLs) published by certificate authorities (CAs). This change does not affect connections to monitored test targets.

**What's Changing** ​

* **January 2027**: The revocation check policy will default to *fail-open*. If an Enterprise Agent cannot determine a certificate's revocation status because none of the certificate's CRL Distribution Points are reachable, the connection will proceed.
* **April 2027**: The default will change to *fail-closed*. In the same situation, the Enterprise Agent will reject the connection.

To help with this transition, a configurable setting in `te-agent.cfg` and the ThousandEyes platform will let you choose fail-open or fail-closed behavior starting with the January 2027 release. We will share configuration details in a future changelog notice.

{% hint style="info" %}
Fail-open applies only when revocation status cannot be determined. Certificates confirmed as revoked are always rejected, and fail-open does not bypass standard TLS certificate validation.
{% endhint %}

For more information about Cisco's security initiatives, see the [Cisco Blog](https://blogs.cisco.com/security/strengthening-the-foundation-a-predictable-customer-focused-response-to-ai-accelerated-vulnerability-discovery).

**Preparing for this update**

Before April 2027, we recommend that you:

* ​Review the TLS certificates used by network proxies and mirrored repositories. Verify that Enterprise Agents can reach the CRL distribution points of the issuing CAs.
* Ensure that Enterprise Agents can access `http://validation.identrust.com/crl/hydrantidcao1.crl` over HTTP (port 80). This is the CRL distribution point currently referenced by the ThousandEyes platform certificate. For firewall requirements, see [Firewall Configuration for Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/configuring/firewall-configuration-for-enterprise-agents).

For questions, contact ThousandEyes Support.

### Endpoint Agent Client Version 2.60.5

The following enhancements have been made to the Endpoint Agent client:

#### Catalyst Access Points

* Updated the system certificate trust store to reject affected eMudhra certificate chains.

### Cloud Insights Adds Network and Security Views to Azure

Cloud Insights now extends to your Azure integration the **Network and Security** view in the **Cloud** layer of **Network & App Synthetics > Views**. Click any shield icon in the **Topology** tab to view Azure network components including subnets, network security groups, interfaces, and virtual hub routing rules. These network details help you identify whether an Azure network configuration change contributed to a degraded synthetic test metric and narrow down the root cause.

See [Network and Security View](https://docs.thousandeyes.com/product-documentation/cloud-insights/views#network-and-security-view) for more information.

### Background Module Installation During CAF Container Reactivation or Upgrade

When you reactivate or upgrade a Cisco Application Hosting Framework (CAF) container and Docker container, agent modules such as BrowserBot might install in the background while the agent continues operating. Until installation completes, tests that depend on the module, such as BrowserBot page load and transaction tests, might fail.

Before reactivating or upgrading a CAF container, configure an [alert suppression window](https://docs.thousandeyes.com/product-documentation/alerts/alert-clearing/alert-suppression-windows) that covers the expected installation period so you are not alerted on false positives while installation completes.

### OpenTelemetry (OTel) Integrations for ThousandEyes for Government

The following OTel-based integrations are now available in the ThousandEyes for Government instance:

* Splunk Cloud Platform HEC
* Splunk Enterprise HEC
* Splunk Observability APM
* Dynatrace Observability APM

For integration details, see [ThousandEyes for OpenTelemetry](https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry). For Government-specific availability and limitations, see [ThousandEyes for Government](https://docs.thousandeyes.com/product-documentation/thousandeyes-for-government).

### Alert Optimizations in the ThousandEyes MCP Server

The ThousandEyes MCP server now gives your AI assistant access to [Alert Optimizations](https://docs.thousandeyes.com/product-documentation/alerts/alert-optimizations):

* `list_alert_rules` — Filter the list to alert rules that have, or do not have, an active alert optimization.
* `get_alert_rule` — If the alert rule has an active alert optimization, the response includes the recommendation and a link to review it in the ThousandEyes platform.

For example, you can ask your assistant "Which alert rules have alert optimizations?" and then ask it to explain the recommended change for a specific rule.

{% hint style="info" %}
The MCP server provides read-only access to alert optimizations. To apply, reject, or dismiss an alert optimization, use the ThousandEyes platform.
{% endhint %}

Alert optimization filtering and details are not available in the ThousandEyes for Government instance. For more information, see [ThousandEyes MCP Server](https://docs.thousandeyes.com/product-documentation/integration-guides/thousandeyes-mcp-server).

## 2026-10-21

### Updated Endpoint PII Handling in Dashboards

Endpoint data in dashboards, including device and network identifiers, locations, domains, and visited sites, is protected according to your Endpoint PII permissions. If you don't have permission to view a field, its value is masked or hashed. You also can't save dashboard or filter changes that include restricted PII.

Existing embedded widgets with **Anonymize PII data** enabled display protected Endpoint values as hashes instead of actual values. Snapshots configured to anonymize PII also display protected values as hashes.

To include actual values in an embedded widget, a user with the relevant Endpoint PII permissions must edit or recreate the embed and turn off **Anonymize PII data**. Anyone with access to the embed can then view the included PII, even if they don't have Endpoint PII permissions.

### Connected Devices: Generic Agent for Broadband Routers Generally Available

Instead of ISPs requiring different Agent builds per device model and custom integration steps, your account manager can provide a Generic Agent for broadband routers, now generally available.

* **Integrate once:** the same package across matching architectures.
* **Compatible with all major platforms:** Use TAR archives or OpenWrt IPK packages with OpenWrt, RDK-B, generic embedded Linux, and OpenSync configurations. The agent automatically selects the best available measurement backend, including supported Broadcom and Qualcomm hardware acceleration.
* **Fast validation:** self-test mode helps you validate an integration before rollout

For deployment planning, production integration, system requirements, speed troubleshooting, and on-net testing, see

* [Getting Started with Device Agent Deployment](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/deployment/getting-started)
* [Production Integration Guides](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/deployment/production-integration-guides)
* [System Requirements](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/deployment/getting-started/system-requirements)
* [Speed Quick Wins](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/deployment/validation-and-troubleshooting/speed-quick-wins)
* [On-Net Test Server Installation](https://docs.thousandeyes.com/product-documentation/connected-devices/device-agents/deployment/on-net-test-server-installation).

## 2026-10-20

### Wireless Active Testing SCEP Support

Wireless Active Testing now supports SCEP-based certificate provisioning for EAP-TLS SSIDs. When integrated with a customer-managed SCEP server, Wireless Active Testing can automatically enroll and renew client certificates, reducing the need for manual certificate provisioning. For setup instructions, see [Configuring Wireless Active Testing with ThousandEyes](https://docs.thousandeyes.com/product-documentation/global-vantage-points/endpoint-agents/wireless-active-testing#ssid-configuration).

## 2026-10-19

### Mobile Endpoint Agent Android Version 1.8.4

The Mobile Endpoint Agent includes the following enhancements:

* Fixed an issue where Android Mobile Endpoint Agent results could cause scheduled HTTP tests to display incorrect agent counts.
* Added cellular identifiers to Android Mobile Endpoint Agent measurements to help pinpoint performance issues to specific cells or base stations.

## 2026-10-15

### Enterprise Agent Support for Red Hat Enterprise Linux 10, AlmaLinux 10, and Rocky Linux 10

ThousandEyes now supports installing Enterprise Agents on Red Hat Enterprise Linux 10, Rocky Linux 10, and AlmaLinux 10.

For support dates, see [Enterprise Agent Support Lifecycle](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/enterprise-agent-support-lifecycle).

## 2026-10-14

### Introducing AI-Assisted Agent Views and In-Home Visibility for Connected Devices

Agent Views for Connected Devices is now generally available. As the next generation of ConstantCare, it gives telecom care agents a dedicated view of a single home so they can review results, identify the likely cause of an issue, and decide what to do next during a customer call.

The redesigned experience includes:

* Summary cards that surface key information at a glance, with more detail available when you need it.
* **Normal** and **Warning** labels that help you spot anomalous results.
* App and game experience results displayed upfront, without requiring you to add charts.
* A map that shows the agent's approximate location when location metadata is available.

Agent Views also includes:

* Cisco AI Assistant integration that summarizes the Agent View context to support diagnosis and remediation decisions.
* Live in-home visibility into signal strength and usage for devices connected to the router. This feature is available with Device Agent 7.16 and requires **nl80211** support in the router firmware. We plan to transition ConstantCare to Agent Views over time. Both experiences remain available during the transition, so teams can adapt their workflows and share feedback as we continue to improve Agent Views.

To open an Agent View, go to **Connected Devices > Agent Search** and select an agent. For more information, see [Agent Views for Connected Devices](https://docs.thousandeyes.com/product-documentation/connected-devices/usage-guides/cdev-agent-views).

## 2026-10-13

### Sunsetting of the Classic ThousandEyes Design

As [previously announced](https://docs.thousandeyes.com/release-notes/2026/2026-08-release-notes#id-2026-08-25), ThousandEyes has introduced an updated design to provide a more consistent experience with [Cisco Cloud Control](https://www.cisco.com/c/en/us/td/docs/ai/cisco-cloud-control/collections/cisco-cloud-control-documentation.html).

As we complete the migration, the "classic" design is being sunsetted, and the updated design will become the standard experience on supported pages.

Previously, customers using the new design saw blue to indicate positive and available states, while customers using the "classic" design saw green. With this update, you can choose either blue or green for these states on supported pages. Green is the default setting unless you select blue.

This setting applies to the user's account, not their organization, and persists across sessions and devices.

#### Dark Mode

**Light**, **Dark**, and **System** remain available as separate display modes. Deprecating the "classic" design does not remove these options, and your green/blue status-color preference is independent of them.

#### Setting Your UI Preferences

To set your preferred theme and status color, go to your account in the top-right of the ThousandEyes platform. In that dropdown menu, click your preferences for **Theme** and **Positive status color**.

![Setting theme and color preferences in the account dropdown menu](https://1112912342-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4QARF6s57qxMrOHDTZ%2Fuploads%2Fgit-blob-b7b209df9ef0cf411ed84536e267594f9e51ca3a%2Fset-ui-theme-prefs_halfmoon_blurred.png?alt=media)

#### Exceptions

Embedded dashboard widgets use light mode by default, with green for positive and available states. They do not follow an individual viewer's color preference. You might also notice updated styling and different shades of green, yellow, and red.

{% hint style="info" %}
The green/blue status-color preference affects chart colors, but it does not change every indicator on a dashboard. For example, a healthy-status icon in a Test Table widget or a favorable trend arrow in a Table widget might still appear blue when the user's preferences are set to **Green**; whereas a Number Card widget showing the same metric uses green. The arrow still accurately shows whether the value increased or decreased. We’re reviewing the table and list indicators separately and will address the color inconsistency in a future update.
{% endhint %}

The following pages will continue to use the **Classic** design for now:

* **Internet Insights >** [**Views**](https://app.thousandeyes.com/internet-insights/views)
* [**Unit Calculator**](https://app.thousandeyes.com/calculator/)
* **Manage > Sharing >** [**Private Snapshots**](https://app.thousandeyes.com/manage/sharing/private-snapshots) and **Manage > Sharing >** [**Public Snapshots**](https://app.thousandeyes.com/manage/sharing/public-snapshots)

No action is required in order to use the default settings. The updated design will become the standard ThousandEyes experience for all other supported pages.

### Cisco Application Hosting Framework (CAF) version 5.2.1

CAF version 5.2.1 has now been released. This release includes the new DNSSEC key and is intended to replace the 5.2.0 image on all supported Cisco devices. For upgrade instructions, see [Upgrading Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/managing/upgrading-enterprise-agents#cisco-application-hosting).

**New Features**

* The new DNSSEC key is used for DNSSEC tests and for agent connections when using FIPS-enabled mode.

**Image Verification**

ThousandEyes recommends validating the checksum of downloaded packages. The SHA256 checksums for the CAF version 5.2.1 images are provided in the UI platform next to the agent image download option.

## 2026-10-07

### Enterprise Agent Update Required for rsyslog-Based Logging

For Enterprise Agents, we’re moving toward `rsyslog-based` logging to manage log size, retention, and disk usage consistently across the services that Enterprise Agent installs. Enterprise Agent version 1.247.0 begins this transition by adding the system package dependencies listed below. This release installs the supporting infrastructure but does not switch the agent’s logging mode.

* All supported platforms: **rsyslog** and **logrotate**
* RPM-based distributions: **shadow-utils**
* Ubuntu/Debian distributions: **passwd**

{% hint style="info" %}
Alpine Linux uses the user- and group-management utilities included in its base system.
{% endhint %}

If the required system package is not already installed on the agent host, it will be automatically retrieved from the required operating system package repositories. Please ensure that your Enterprise Agents have access to these repositories.

We have observed that some Enterprise Agents are unable to complete automatic updates because they cannot reach the required operating system package repositories due to firewall or network restrictions. We recommend reviewing any Enterprise Agents running an out-of-date agent version and resolving any repository connectivity issues to ensure that the agent can be updated to the latest 1.247.0 version.

For information about configuring repository access, see [Firewall Configuration for Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/configuring/firewall-configuration-for-enterprise-agents#linux-packages).

### Endpoint Agent Client Version 2.60.1

The following enhancements have been made to the Endpoint Agent client:

#### All Platforms

* Improved the robustness of DHCP measurements with noncompliant DHCP servers.

#### macOS

* Fixed an issue on macOS that could prevent user-space services from running when the user-space agent failed to register with or check in with the Endpoint Agent.

## 2026-10-06

### NTLM Authentication Options Hidden for Accounts Not Using NTLM

Starting October 6, 2026, ThousandEyes hides the NTLM authentication option when you create a test or Enterprise Agent proxy configuration for an account that does not already use NTLM in proxy or test settings. Accounts that currently use NTLM in either test or proxy configurations will not be affected by this change and can continue using NTLM.

If you use NTLM, review your configurations and plan to move to a supported authentication method before January 2027, when ThousandEyes plans to end NTLM support. For details, see [Advance Notice: End of Support for NTLM Authentication](https://docs.thousandeyes.com/release-notes/2026/2026-09-release-notes#id-2026-09-02).

## 2026-10-05

### Ubuntu 22.04 LTS (“Jammy”) Lifecycle and Appliance Upgrade Path

Ubuntu 22.04 LTS (“Jammy”) will reach End of Installation Support on January 31, 2027, End of Support on April 30, 2027, and End of Life on June 30, 2027. After the End of Life date, Enterprise Agents that remain on Ubuntu 22.04 LTS will no longer be able to communicate with the ThousandEyes platform.

These lifecycle dates affect package-based installations and the following image-based installations:

* The ThousandEyes Virtual Appliance (TEVA) for VirtualBox, VMware ESXi, Hyper-V, and Nutanix AHV.
* The ThousandEyes Physical Appliance (TEPA) for Intel/ASUS NUC and Raspberry Pi.

An in-place operating system upgrade path from Ubuntu 22.04 LTS to Ubuntu 24.04 LTS (“Noble”) is now available for TEVA and TEPA. You can start the upgrade for a single appliance or multiple appliances from the ThousandEyes platform, or use the local TEVA web interface for appliances behind a proxy.

Before starting an upgrade, back up the Enterprise Agent configuration. For requirements, instructions, and troubleshooting guidance, see [Upgrading Ubuntu 22.04 Jammy-Based ThousandEyes Appliances](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/managing/upgrade-ubuntu-22.04-jammy-based-thousandeyes-appliances).

For additional lifecycle information, see [Enterprise Agent Support Lifecycle](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/enterprise-agent-support-lifecycle#ubuntu-linux).

### ThousandEyes Support & Lifecycle Updates: October 2026

#### Alpine Linux 3.21 End of Support Reminder

Alpine Linux 3.21 will reach End of Support on November 1, 2026. After this date, ThousandEyes will no longer provide technical support or guarantee software updates for Enterprise Agents running on this version of the operating system. The End of Life date is January 4, 2027. We recommend planning your operating system upgrades in advance of these dates to ensure continuous service.

{% hint style="info" %}
This applies to ThousandEyes Enterprise Agents deployed as Docker containers or using the Cisco Application Hosting Framework (CAF).

ThousandEyes does not support the native installation of ThousandEyes Enterprise Agents on Alpine Linux.
{% endhint %}

For upgrade instructions, see [Upgrading Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/managing/upgrading-enterprise-agents).

#### Rocky Linux 9.8 End of Installation Support and End of Support Reminder

Rocky Linux 9.8 will reach End of Installation Support and End of Support on November 30, 2026. Following this, it will reach End of Life on January 29, 2027. We recommend planning your operating system upgrades in advance of these dates to ensure continuous service.

#### Ubuntu Linux 22.04 LTS End of Installation Support Reminder

Ubuntu Linux 22.04 LTS ("Jammy") will reach End of Installation Support on January 31, 2027. After this date, ThousandEyes will no longer permit new Enterprise Agent installations on this version of the operating system. Existing agents will continue to function and receive support until the End of Support phase begins on April 30, 2027. The End of Life date is June 30, 2027. We recommend planning your operating system upgrades in advance of these dates to ensure continuous service.

### New Cloud Agents

New Cloud Agents have been added in the locations listed below. For a full list of Cloud Agents, see [ThousandEyes Cloud Agent Locations](https://www.thousandeyes.com/product/cloud-agents).

* Mumbai, India (TATA)
* Mumbai, India (TATA) (IPv6)

## 2026-10-02

### Endpoint Agent Explainability Logging - Open Beta

The ThousandEyes Endpoint Agent now explains its own health. Previously, an agent could report as running without showing whether it could run tests or collect telemetry. Explainability Logging provides a structured state, reason, impact, and recommended action for each agent. You can view this information in the ThousandEyes platform and export it for support.

**Key features include**:

* **State, reason, impact, and recommended action.** Each agent reports a health state with a stable reason code, the resulting impact, and a recommended remediation in plain language.
* **Blocker attribution.** Explainability Logging identifies blockers such as missing permissions, missing OEMConfig, blocked background execution, or a throttled or terminated service. Service terminations include attribution to the operating system, device manufacturer, application, or mobile device management (MDM) system when available.
* **Onboarding health history.** A per-agent history records health-state changes so you can identify when an issue started.
* **API access.** External APIs expose the same fields for downstream systems and Model Context Protocol (MCP) integrations.

**Prerequisites**:

* **Supported platforms.** Endpoint Agents on Android, Windows, and macOS.
* **Agent version.** Endpoint Agent 2.57.0 or later, and Mobile Endpoint Agent 1.8.3 or later.
* **Account and permissions.** A ThousandEyes account with the admin permissions required to view Endpoint Agent settings and generate support bundles.

Deployment and enrollment details are not available for Endpoint Agents on Windows and macOS.

For more information, see [Endpoint Agent Health](https://docs.thousandeyes.com/product-documentation/global-vantage-points/endpoint-agents/managing/endpoint-agent-health).

## 2026-10-01

### Modernized Endpoint Views Experience

The redesigned **Endpoint Experience > Views** provides a modern, intuitive experience that aligns with **Network & App Synthetics** for a more consistent experience across the ThousandEyes platform.

The new experience makes endpoint performance investigations faster and smoother, with more responsive interactions and a clearer path from high-level trends to detailed metrics. The update also includes **Snapshot** improvements, bug fixes, and wording updates across the product and documentation.

This update preserves existing capabilities and adds selectable themes, including light and dark modes.

### Expanded Wi-Fi Metrics for Endpoint Agents

ThousandEyes now provides deeper visibility into wireless performance with two additional metrics: **Signal-to-Noise Ratio (SNR)** and **Noise**.

These metrics are available for Endpoint Agents on desktop and laptop devices, RoomOS devices, and Cisco wireless devices. They complement existing Wi-Fi metrics, including **Signal Quality**, **RSSI**, **Throughput**, **Retransmission Rate**, **Channel Swap Events**, **Transmit Rate**, and **Roaming Events**. Together, these metrics help you distinguish signal strength issues from wireless interference and troubleshoot connectivity problems with greater confidence.

### Mobile Endpoint Agent Android Version 1.8.3

The Mobile Endpoint Agent includes the following enhancements:

* Android agents now report TCP test support correctly, eliminating the misleading “Npcap not installed” status.
* Fixed an issue that incorrectly showed healthy ChromeOS agents as Degraded when the app was in the background or closed.
* Fixed a crash on some Android devices when opening location settings.
* Updated the Android agent's target SDK to align with Google Play's target SDK requirements.
* Fixed a crash on some Android devices when opening battery optimization settings.
