> 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-09-release-notes.md).

# Release Notes: September 2026

## 2026-09-29

### API Keys Generally Available

API Keys are now generally available. The keys provide organization-level credentials for applications, scripts, and integrations that need to access the ThousandEyes API without relying on an individual user's credentials.

Each API Key can be named and configured with its own permissions and account group scope, so organizations can limit the data and API operations available to an integration. API Keys use the standard bearer authentication scheme:

```
Authorization: Bearer <API_KEY>
```

API Keys expire after 180 days and can be regenerated, disabled, or deleted. When you regenerate a key, both the previous and new key values remain valid during a grace period, allowing you to update affected integrations without interruption.

Users with API Key management permissions can access API Keys from **Manage > Account Settings > Users and Roles > API Keys**. By default, Organization Admin users have both API Key management permissions, Account Admin users have *Manage own API Keys*, and Regular Users have neither permission. You can add one or both permissions to custom roles via **Manage > Account Settings > Users and Roles > Roles**:

* *Manage own API Keys*: Allows users to create and manage the API Keys they created.
* *Manage all API Keys in organization*: Allows users to view and manage API Keys created by any user in the organization.

The existing *API access* permission allows users to access the API with their personal bearer token but does not grant permission to create or manage API Keys.

For more information, see [API Keys](https://docs.thousandeyes.com/product-documentation/user-management/authorization/api-keys).

### Basic Authentication Tokens Due to be Sunsetted

Support for legacy Basic Authentication tokens ends **March 31, 2027**. This change does not affect API Keys or user OAuth2 Bearer Tokens, and existing Basic Authentication tokens will continue to work during the migration period. To plan your migration:

* For organization-level automation and machine-to-machine integrations, migrate to an API Key.
* For integrations that must authenticate as an individual user, migrate to a user Bearer Token.

ThousandEyes will provide migration guidance and additional notice before Basic Authentication tokens are disabled. For any help with the migration, contact ThousandEyes Support.

## 2026-09-24

### Endpoint PII Permissions Required for OpenTelemetry Streams

Creating or updating an OpenTelemetry stream integration that includes Endpoint Experience data now requires all five Endpoint PII permissions:

* **View endpoint experience data that identifies Endpoint Agents**
* **View endpoint experience data that identifies location**
* **View endpoint experience data that identifies network**
* **View endpoint experience data that identifies users**
* **View endpoint experience data that identifies visited pages**

This requirement applies when the integration includes selections under **Endpoint Experience Tests** or **Endpoint Experience Tags**, or tags associated with Endpoint Experience tests under **Tags**. If you don't have all five permissions, ThousandEyes rejects the save and returns **403 Forbidden** for Streams API requests.

ThousandEyes also checks these permissions when you update an existing integration that retains Endpoint PII scope, including updates that only change the integration name. You can update the integration without these permissions if the resulting configuration no longer includes Endpoint Experience tests or tags.

For configuration details and permission descriptions, see [Getting Started with OpenTelemetry Streaming](https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/getting-started#prerequisites).

### Alert Rules Table Improvements

After the related alert-rule rollout is complete, **Manage > Alert Rules** will let you:

* View and filter rules by severity for supported alert types.
* See when each rule was last modified, sort by modification date, and filter by date range. If a rule has no modification timestamp, the table shows an em dash and keeps it after rules with timestamps in either sort direction.
* Filter supported rules by **Adaptive** or **Manual** detection mode on the **Network & App Synthetics** and **Endpoint Experience** tabs.
* View a complete rule name on hover or keyboard focus when the **Name** column truncates it.
* Combine these filters with search and other active filters. Clear the search and all active filters to restore the complete rule list for the selected product area.

### Device Throughput Values in Alert Emails

After the related rollout is complete, Device throughput alert emails will display measured values in the unit configured in the rule, making values and thresholds directly comparable. Formatting for other Device metrics and alert types is unchanged.

For more information, see [Creating and Editing Alert Rules](https://docs.thousandeyes.com/product-documentation/alerts/creating-and-editing-alert-rules) and [Alert Notifications Via Email](https://docs.thousandeyes.com/product-documentation/alerts/standard-notification-methods/alert-notifs-via-email).

### Kubernetes Cluster Enterprise Agents

ThousandEyes is introducing a new Enterprise Agent installation type, **Kubernetes Agent**, designed to simplify agent deployment and scaling within Kubernetes clusters. Kubernetes agents are deployed using a YAML manifest with customizable configuration and stateful policy, enabling native Kubernetes capabilities such as scaling, self-healing, rolling updates, persistent storage, and declarative configuration.

For more information, see [Kubernetes Agent Installation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing/kubernetes-agent-installation).

### Cisco Catalyst 9550 Support for Enterprise Agents

ThousandEyes now supports installing Enterprise Agents on Cisco Catalyst 9550 Series Smart Switches. For system requirements and installation prerequisites, see [Supported Cisco Switching Platforms](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing/cisco-devices/supported-cisco-switching-platforms).

### SHA256 Checksums Now Included in Enterprise Agent Downloads

ThousandEyes now provides SHA256 checksums for Cisco Application Hosting agent and appliance agent downloads. Customers can compare the published checksum with the downloaded file to verify its integrity before installation.

## 2026-09-23

### Endpoint Agent Support for Cisco Video Phone 8875

The ThousandEyes Endpoint Agent now supports Cisco Video Phone 8875 devices running PhoneOS 5.0.1 or later. Endpoint Agent telemetry complements PhoneOS device data to help you determine whether call-quality problems originate on the phone, local network, network path, or broader network.

Supported capabilities include:

* Scheduled tests for devices registered with Webex Calling multi-tenant (WxC MT), Webex Calling Dedicated Instance (WxC DI), or Cisco Unified Communications Manager (Unified CM).
* Dynamic tests for meetings. WxC MT supports Webex meetings through hybrid or Microsoft 365 calendars. WxC DI and Unified CM support Webex, Microsoft Teams, and Zoom meetings.
* Dynamic tests for SIP calls. WxC MT uses UDP/STUN with automatic protocol detection.

The Endpoint Agent is embedded in PhoneOS and remains disabled until you activate it through Control Hub or Unified CM. You need a ThousandEyes account with the required admin permissions and an Essentials or Advantage license.

Cisco Desk Phone 9811, 9851, and 9841 models are not supported. Detailed Wi-Fi metrics, ICE-optimized calls, proxy configurations, VPNs, WebRTC, BroadWorks, and third-party call control are also not supported. Phones deployed with WxC MT do not support third-party meetings such as Microsoft Teams and Zoom.

For activation instructions, see [Configure 9800 Series and 8875 Phones on Control Hub](https://help.webex.com/en-us/article/n72q8yeb/Configure-Cisco-Desk-Phone-9800-Series-on-Control-Hub#concept-template_765338b4-186f-4098-a549-1e1af863497f) and [Configure 9800 and 8875 Phones on Unified CM](https://help.webex.com/en-us/article/9geimz/Phone-features-and-setup-on-Unified-CM#task-template_05a5d22a-0220-46fe-8e84-92bc5c837117). For ThousandEyes setup and supported-device requirements, see [Endpoint Agent Installation on Cisco Phone Devices (PhoneOS)](https://docs.thousandeyes.com/product-documentation/global-vantage-points/endpoint-agents/installing/cisco-devices/install-phoneos). For device specifications, see the [Cisco Video Phone 8875 Data Sheet](https://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints/unified-ip-phone-8800-series/video-phone-8875-ds.html).

## 2026-09-22

### Color Grid Cards Show Metric Units

Color Grid cards now display the unit alongside each metric value, including percentage values such as **20%**, response-time values such as **42 ms**, and other supported units. Cards without data continue to show a hyphen (**-**).

### Simplified Metric Selection in Dashboards

Dashboard widget configuration now uses a single **Metric** selector to choose the data source, category, and metric. The selector also supports searching for metrics, viewing recently used metrics, filtering by one or more data sources, and choosing the display order for the selected value: **Data Source / Category / Metric** or **Metric / Category / Data Source**. For more information, see [Dashboard Widgets](https://docs.thousandeyes.com/product-documentation/dashboards/dashboard-widgets#selecting-a-metric).

### Cloud Insights Topology View

Visualize your AWS cloud inventory at **Cloud Insights > Topology**. The new **Topology** screen shows the relationships among your AWS cloud resources as nodes and connections, providing a high-level interactive map of your AWS environment. Unlike the fine-grained, test-specific topology views available in **Network & App Synthetics > Views**, it shows the overall structure of your cloud network without requiring you to create a synthetic test.

Cloud Insights Topology is available to all Cloud Insights customers as a preview and currently supports AWS environments only.

For more information, see [Cloud Insights Topology](https://docs.thousandeyes.com/product-documentation/cloud-insights/views/inventory-topology).

## 2026-09-18

### Network Segmentation Widget in Cisco Cloud Control

The Network Segmentation widget is now available in Cisco Cloud Control through AI Canvas. You can use natural language queries about the network path and Path Visualization for Cloud and Enterprise Agents to view the end-to-end network path between a monitored location and an application. Individual network hops are visually grouped into segments to help identify where a problem is occurring and which team or provider may need to investigate it. This complements the detailed, hop-by-hop Path Visualization view.

For more information, see [Network Segmentation Widget](https://docs.thousandeyes.com/product-documentation/thousandeyes-and-cisco-cloud-control#network-segmentation-widget).

## 2026-09-17

### Chromium 152 Available for Browser Test Validation

Chromium 152 is now available for validation through the Dual Chromium option. For page load and transaction tests, set **Chromium Version** to **Newer when available** to test important scripts against the newer browser track before it becomes the default. The current **Default** track remains on Chromium 150.

ThousandEyes is targeting October 1, 2026, to make Chromium 152 the **Default** version. This date might change if validation identifies major issues. Before the target date, validate business-critical scripts and review any new errors or script behavior changes on the newer track.

ThousandEyes also runs automatic validation before the **Default** Chromium upgrade for tests that can use Dual Chromium. These instant tests might appear in your **Activity Log**, but they do not consume units. For details, see [Configuring Dual Chromium](https://docs.thousandeyes.com/product-documentation/browser-synthetics/dual-chromium-option/configure-dual-chromium#thousandeyes-validation-on-dual-chromium-agents).

For Enterprise Agents, use the **Dual Chromium Version** BrowserBot package. Cloud Agents require no additional agent setup.

For more information, see [Dual Chromium Option](https://docs.thousandeyes.com/product-documentation/browser-synthetics/dual-chromium-option).

## 2026-09-15

### Mobile Endpoint Agent Android Version 1.8.2

The Mobile Endpoint Agent includes the following enhancements:

* Improved the enrollment details displayed for fully managed devices.
* Improved device identification using serial numbers provided through mobile device management (MDM).
* Added support for scanning QR code activation links with Zebra device scanners.

### Customer Action Deadline for the Browser Synthetics Screenshot Return Format Change

As announced in the [August 17 notice](https://docs.thousandeyes.com/release-notes/2026/2026-08-release-notes#id-2026-08-17), on September 16, 2026, ThousandEyes plans to change the screenshot data returned by `driver.takeScreenshot()` from base64-encoded PNG data to base64-encoded JPEG data. You can continue to view screenshots in transaction test results as usual.

September 15, 2026, is the customer action deadline. Review transaction scripts that use the return value from `driver.takeScreenshot()`. No change is required for transaction scripts that call `await driver.takeScreenshot();` and don't use its return value. If a script uses the returned data, update it and any downstream systems to detect, correctly label, and accept both PNG and JPEG data. In particular, review scripts that do any of the following:

* Add a `data:image/png;base64,` prefix or label the data as `image/png`.
* Remove a PNG-specific data URL prefix.
* Write the returned data to a `.png` file.
* Send the data to another system that requires PNG.

Validate the complete workflow with both formats instead of relabeling current PNG data as JPEG. If you need help reviewing an affected script, contact ThousandEyes Support.

## 2026-09-10

### AI Assistant Deep Reasoning Mode

The Cisco AI Assistant in ThousandEyes now supports **Deep Reasoning** mode. Deep Reasoning supports both straightforward questions and more complex investigations, including quick lookups, multi-signal troubleshooting, root-cause analysis, and configuration recommendations. It also has access to the full functionality of the ThousandEyes MCP server.

For more information, see [Cisco AI Assistant Integrated in ThousandEyes](https://docs.thousandeyes.com/product-documentation/getting-started/getting-support-from-thousandeyes#cisco-ai-assistant-integrated-in-thousandeyes).

### Metric and Attribute Filtering for OpenTelemetry Streaming Integrations

You can now control the data exported by ThousandEyes for OpenTelemetry integrations by excluding specific metrics or attributes. Metric filtering is available for metric streams using Data Model v1 or v2. Attribute filtering is available for metric streams using Data Model v1 or v2, and for trace and log streams using Data Model v2.

Configure filtering through the ThousandEyes platform or the Streams API. For configuration instructions and supported names, see [Filter Streamed Telemetry](https://docs.thousandeyes.com/product-documentation/integration-guides/opentelemetry/filter-streamed-telemetry).

## 2026-09-08

### Final Reminder About the Browser Synthetics Screenshot Return Format Change

As announced in the [August 17 notice](https://docs.thousandeyes.com/release-notes/2026/2026-08-release-notes#id-2026-08-17), on September 16, 2026, ThousandEyes plans to change the screenshot data returned by `driver.takeScreenshot()` from base64-encoded PNG data to base64-encoded JPEG data. You can continue to view screenshots in transaction test results as usual.

Review transaction scripts that use the return value from `driver.takeScreenshot()` by September 15, 2026. No change is required for transaction scripts that call `await driver.takeScreenshot();` and don't use its return value. If a script uses the returned data, update it and any downstream systems to detect, correctly label, and accept both PNG and JPEG data. In particular, review scripts that do any of the following:

* Add a `data:image/png;base64,` prefix or label the data as `image/png`.
* Remove a PNG-specific data URL prefix.
* Write the returned data to a `.png` file.
* Send the data to another system that requires PNG.

Validate the complete workflow with both formats instead of relabeling current PNG data as JPEG. If you need help reviewing an affected script, contact ThousandEyes Support.

### Modernized Line Chart Experience Now Available

As [previously announced](https://docs.thousandeyes.com/release-notes/2026/2026-08-release-notes#id-2026-08-20), the **Line** chart in the **Time Series** widget now includes new legend, drill-down, tooltip, and zoom interactions that make it easier to compare series and investigate changes over time.

This release applies only to **Line** charts. **Stacked Area** and **Box and Whiskers** charts are unchanged.

* Use the paginated legend to navigate charts with many series. Select one series to isolate it, or Command-click on macOS or Ctrl-click on Windows to compare several series.
* Hover over a legend entry or line to highlight that series while the other lines are dimmed.
* Left-click a data point to drill down. When lines overlap, right-click the point to choose the series you want to investigate.
* Hold Command on macOS or Ctrl on Windows and scroll to zoom. Scrolling without the modifier continues to scroll the dashboard. You can also use the optional zoom slider, move through the zoomed range with the Left Arrow and Right Arrow keys, or select **Reset zoom** to restore the full range.

The tooltip no longer locks in place or contains clickable links. Use left-click or right-click to drill down instead.

Zoom changes only the visible range in the widget. It does not change the dashboard time range or load data at a finer interval. The selected zoom range resets when the widget reloads.

For more information, see [Dashboard Widgets](https://docs.thousandeyes.com/product-documentation/dashboards/dashboard-widgets#line-widget) and [Troubleshooting with Dashboard Drill Down](https://docs.thousandeyes.com/product-documentation/dashboards/troubleshooting-with-drill-down).

## 2026-09-03

### Mobile Endpoint Agent Android Version 1.8.1

The Mobile Endpoint Agent includes the following enhancements:

* Added support for dedicated Honeywell QR scanners, enabling you to scan QR codes during Mobile Endpoint Agent onboarding and registration.
* Added automatic protocol selection for ping and path trace tests. The Mobile Endpoint Agent selects the best-performing protocol for each target based on current network conditions.

## 2026-09-02

### Advance Notice: End of Support for NTLM Authentication

By January 2027, ThousandEyes will end support for NTLM authentication used by Enterprise Agents and Endpoint Agents. This change aligns with Microsoft’s transition away from NTLM and curl’s removal of NTLM support. It also allows ThousandEyes to adopt supported libcurl versions and continue providing security and protocol updates.

After this date, NTLM authentication will no longer be supported for:

* Agent communication through NTLM-authenticated proxies and communication with mirrored repositories.
* HTTP server, page load, and transaction tests that use NTLM-authenticated proxies.
* OAuth endpoints that authenticate using NTLM.

**Action Required** - Review your Enterprise Agent, Endpoint Agent, and test configurations. Before January 2027, migrate all NTLM dependencies to a supported authentication method. For Enterprise Agents, ThousandEyes recommends Kerberos authentication, in line with Microsoft’s guidance.

For additional guidance on Kerberos authentication, see [NTLM and Kerberos authentication considerations](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-test-sso-support/caveats-ntlm-kerberos).

For industry context, see Microsoft's [NTLM transition announcement](https://techcommunity.microsoft.com/blog/windows-itpro-blog/advancing-windows-security-disabling-ntlm-by-default/4489526) and curl's [NTLM removal announcement](https://curl.se/mail/lib-2026-03/0026.html).

### Enhanced Support Chat Now Live

As [previously announced](https://docs.thousandeyes.com/release-notes/2026/2026-08-release-notes#id-2026-08-19), we have now rolled out a significant upgrade to the chat feature available in the ThousandEyes platform at **Help & Support > Chat with Support**:

* **Translation**

  Support chat now includes automatic message translation. You can write in your preferred language, and your message is translated for the Support engineer, with their response translated back to you.
* **Timeout and reconnection**

  Chat conversations now become inactive after 20 minutes, but are not closed permanently. You can resume the conversation by replying within 24 hours. When you resume the conversation, it will return to the Support queue and an available engineer will accept it and continue helping you.
* **File upload**

  You can now upload files, such as agent logs, directly into the chat conversation. Each file can be up to 5 MB.

### Alerting for Cloud Insights Traffic Events

You can now create alerts for anomalous cloud traffic events detected by Cloud Insights. Event alerts help you move from reactive troubleshooting to proactive monitoring by notifying you about relevant traffic patterns without requiring manual threshold configuration.

For more information about cloud traffic event alerts, see [Cloud Insights Views: Alerts Tab](https://docs.thousandeyes.com/product-documentation/cloud-insights/views#alerts-tab).

### Endpoint Agent Client Version 2.57.0

This release includes internal reliability improvements and bug fixes. These changes have no impact on end users, and no action is required.

## 2026-09-01

### ThousandEyes Support & Lifecycle Updates: September 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.

#### Amazon Linux 2 End of Life

Amazon Linux 2 has now reached its End of Life date (as of August 30, 2026). ThousandEyes Enterprise Agents on Amazon Linux 2 must be upgraded to Amazon Linux 2023 or another supported OS to remain functional. For upgrade instructions, see the [AWS documentation](https://docs.aws.amazon.com/linux/al2/ug/prepare-for-al2023.html).

### Cloud Agent Name Update

On September 9, 2026, the Cloud Agent currently listed as Seoul, South Korea (LG Telecom) will be renamed to Seoul, South Korea (LG Uplus). No action is required for this update.

### API Tests on Cloud and Enterprise Agents

[As previously announced](https://docs.thousandeyes.com/release-notes/2026/2026-08-release-notes#id-2026-08-06), ThousandEyes has begun rolling out architectural changes to the API test for both Cloud and Enterprise Agents, eliminating the dependency on BrowserBot.

API tests enable monitoring of HTTP-based APIs using multi-step workflows, assertions, authentication, and detailed performance metrics. For more information, see [API Tests](https://docs.thousandeyes.com/product-documentation/tests/api-tests#configuring-api-tests).

Functionality updates and limitations are listed below. If you notice any issues running API tests on Enterprise Agents without BrowserBot, please ensure that the agents are configured for automatic updates and are running the latest version. For further troubleshooting, please contact ThousandEyes Support.

**What to Expect**

As this capability is rolled out:

* Cloud and Enterprise Agents will automatically gain support for API tests from agent version 1.242.0.
* Existing tests that use supported API-test features, including timestamp modifiers, require no configuration changes.
* Once the rollout is complete, customers will be able to create and run API tests from all Cloud and Enterprise Agents without requiring BrowserBot anymore.

**Functionality Updates**

* The core agent supports HSTS (HTTP Strict Transport Security).
* The core agent supports HTTP/2.
* API tests allow cross-protocol and cross-origin redirects. The core agent reapplies configured headers, request bodies, and client certificates after a redirect, so review redirect destinations before using sensitive values.
* The former 5 MB total-response limit no longer applies to response collection. In the HAR, response text is replaced with a message when the body is larger than 1 MB, but the response size remains available.
* BrowserBot-specific blocking time is not reported.
* `timestamp()` supports `.add()`, `.subtract()`, `.format()`, and `.tz()` modifiers. Add and subtract modifiers run in the order written; `format` and `tz` can each appear once.

**Current Limitations**

For API tests that run on the core agent, the Agent manages the `Accept-Encoding` header and supports *deflate* and *gzip* response compression.
