Endpoint Automated Session Tests Snapshots

Automated Session Tests from Endpoint Agents can now be included in Endpoint Snapshots. Together with Scheduled Tests, Browser Sessions, and Local Network, you will be able to save a snapshot carrying the necessary information related to the specific set of tests that you have defined. In addition, you can still define the data range, the anonymization of the data that identifies users, and whether you want to generate the link to share it with third-parties.
For more information, see Automated Session Tests.

Endpoint Agent NPCAP Library Upgrade to Version 1.55

The NPCAP library on the Endpoint Client Agent for Windows will be upgraded to version 1.55 on September 17, 2022. This library is required by users to leverage TCP network tests. The manual upgrade for testing is available now. You can learn more about this upgrade and how to test it here.

New Cloud Agents

New Cloud Agents have been added to the following locations:
  • Antwerp, Belgium (Proximus) (IPv4)
  • Antwerp, Belgium (Proximus) (IPv6)
  • Bangkok, Thailand (Alibaba ap-southeast-7)
  • Gävle, Sweden (Azure swedencentral)
  • Hong Kong (HKT) (IPv4)
  • Hong Kong (HKT) (IPv6)
  • Jakarta, Indonesia (AWS ap-southeast-3)
  • Jersey City, NJ, USA (IPv4)
  • Jersey City, NJ, USA (IPv6)
  • Madrid, Spain (GCP europe-southwest1)
  • Midlothian, TX, USA (GCP us-south1)
  • Milan, Italy (GCP europe-west8)
  • New Albany, OH, USA (GCP us-east5)
  • Paris, France (GCP europe-west9)
  • Phoenix, AZ, USA (Azure westus3)
  • Santiago de Chile, Chile (GCP southamerica-west1)
  • Seoul, South Korea (Alibaba ap-northeast-2)
  • Tokyo, Japan (NTT) (IPv4)
  • Tokyo, Japan (NTT) (IPv6)
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.

2022-08-04 Bug Fixes

  • An issue was identified when migrating Endpoint labels to the new system. A small subset of customers had an additional set of labels created incorrectly. These labels were removed and did not cause any service impact.


DNS Issues with Cloud Agents in China

At 8:00 UTC time on July 11, 2022, certain Cloud Agents in China began experiencing high packet loss to both configured DNS resolvers. This is representative of conditions that occur in this geographic region. DNS resolution also affected the ability to submit Cloud Agent data to the ThousandEyes Platform.
Between July 13, 2022 at 00:40 UTC and July 13, 2022 at 05:40 UTC, the Cloud Agent operations team took action to enable data submission by updating the DNS resolver for affected locations to, which is a DNS resolver in China Unicom's ASN. This change enabled data collected to be successfully submitted to the ThousandEyes platform.
An expected side-effect of this change is that certain tests' DNS resolution behavior may have changed due to using different resolvers. Our product and engineering teams continually assess DNS performance in China and from their tests, they found the most reliable DNS open resolver is aliDNS ( This is an anycast solution, so we expect good reliability from it moving forward, using as a primary and as a secondary DNS resolver for the following Cloud Agents in China:
  • Beijing, China (China Mobile)
  • Beijing, China (China Telecom)
  • Beijing, China (China Unicom)
  • Changsha, China (China Mobile)
  • Chengdu, China
  • Chengdu, China (China Mobile)
  • Chongqing, China (China Mobile)
  • Dalian, China (China Unicom)
  • Foshan, China
  • Guangzhou, China
  • Guangzhou, China (China Mobile)
  • Guangzhou, China (China Unicom)
  • Jinan, China (China Unicom)
  • Nanjing, China
  • Ningbo, China (China Mobile)
  • Shanghai, China (China Mobile)
  • Shanghai, China (China Telecom)
  • Shanghai, China (China Unicom)
  • Shenyang, China (China Unicom)
  • Shenzhen, China (China Mobile)
  • Shenzhen, China (China Unicom)
  • Shijiazhuang, China (China Unicom)
  • Tianjin, China (China Mobile)
  • Wenzhou, China (China Telecom)
  • Wuhan, China (China Telecom)
  • Wuxi, China
  • Xi'an, China (China Telecom)
  • Zhengzhou, China (China Mobile)
This change took place on the 25th of July, 2022 at 16:00 UTC.


BrowserBot Early Track Program

From July 26th - August 8th, 2022, Enterprise Agents that have already been enrolled in the BrowserBot Early Track Program will receive Browserbot v2.6.0, which will include the Chromium v97 upgrade. For teams using Cloud Agents for browser-based tests, two Cloud Agents will also have BrowserBot upgraded to Chromium v97 for testing page load and transaction tests. These Cloud Agents are:
  • Taipei, Taiwan 2 (IPv6)
  • Tucson, AZ, USA (IPv6)
After the conclusion of the Early Track Program, all Cloud and Enterprise Agents will be upgraded to BrowserBot v2.6.0 with Chromium v97 during the week of August 8th, 2022.


New Agent Status Settings for the Endpoint Agent

Efficiently managing hundreds or thousands of Endpoint Agent licenses is not simple. In order to make the maintenance process easier, the Endpoint Agent now includes the new Agent Status Settings. This new feature provides you with a set of configuration options to automatically manage the status of Endpoint Agents. In particular, these options allow you to configure the number of days after which the agents can be automatically disabled, deleted, or re-enabled. After the initial configuration, the system will periodically evaluate the conditions defined on the agents' statuses and notify you with any change in the Activity Log.

Minor Enhancements

  • The usability of the agent selection within Endpoint Agent labels has been improved. In particular, a 'deleted' filter in the drop-down agent list has been added. You can use this filter to find all agents that have been deleted from the platform.

2022-07-19 Bug Fixes

  • An issue has been resolved where the Endpoint Agent label search function was not allowing for the correct search results.
  • An issue in the ThousandEyes Enterprise Agent that occurred when the agent was configured with link local IPv6 addresses only and the target of a test was an IPv6 address has been corrected.
  • An issue was found where the link to download the Endpoint Agent was not properly generating when the “Allow anyone with the link to download” option was enabled. This has been resolved.
  • An issue was resolved in Internet Insights where, when switching from the Network Outage layer to Application Outages, the alerts swimlane was not updated. This would only occur when the "Affected Test" metric was selected and would result in Network Outage alerts appearing in the Application Outages alerts swimlane.
  • Fixed an issue where alert suppression windows of shared tests were incorrectly being applied to multiple account groups, instead of the account group that created and assigned the alert suppression window. Moving forward, any alert suppression window applied to a shared test will only suppress alerts in the same account group as the alert suppression window.
  • An issue was found that was preventing users from downloading a PDF or CSV of a report when accessing the download link through the notification icon in the header of the product. This has been resolved.
  • An issue was resolved that was preventing users from creating a browser session alert rule with an underscore in the domain. Customers can now set alert rules for a specific visited site with a custom domain including an underscore.
  • An issue was resolved with our built-in reports where we were incorrectly rendering the top ten tests in specific widgets and showing a "Render Anyway" message. The top ten tests for each widget now show as expected when loading the report.
  • An issue was resolved where our report PDF downloads were incorrectly showing "Generated by null" instead of showing the specific user that generated the PDF.


Endpoint Agent Metrics for Dashboards and Reports

Our dashboards and reports now support additional metrics, filters, and group bys for Endpoint Agent browser sessions and scheduled tests.

Browser Sessions

  • VPN Latency
  • VPN Loss
Filters and Group Bys
  • Gateway
  • SSID
  • VPN Vendor
  • VPN Gateway
  • Proxy Addresses
  • Session Errors
  • IP Address

Scheduled Tests

  • TCP Connection Failures
  • VPN Latency
  • VPN Loss
Filters and Group Bys
  • Endpoint Agent Types
  • Target IP
  • Gateway
  • SSID
  • VPN Vendor
  • VPN Gateway


Microsoft Azure Support for Enterprise Agents

The ThousandEyes Enterprise Agent can now be deployed with an Azure Resource Manager template. For installation instructions, see Installing Enterprise Agents with Microsoft Azure.

Packet Spreading for One-Minute Interval Tests

Previously, the ThousandEyes platform sent 50 packets in a burst at the start of a one-minute interval network test. This resulted in ThousandEyes potentially missing intermittent blips that lasted a few seconds. These blips were sometimes caught by black-box tools, resulting in confusion for customers.
With this release, customers can configure ThousandEyes to send one packet per second over the full duration of a network test. Packet loss is calculated as an average over the minute, and jitter and latency calculations have also been updated to match the new capability. In addition, we've added a sparkline visualization to show exactly when a packet drop occurred during your test.
This feature is specific to network tests, and is currently only available to agent-to-server network tests with one-minute intervals.
To configure packet spreading:
  1. 1.
    Log into the ThousandEyes web application using a user with permission to modify tests.
  2. 2.
    Navigate to Test Settings.
  3. 3.
    Select the desired test, either by scrolling through the list or using the text search field.
  4. 4.
    Navigate to the Advanced Settings tab.
  5. 5.
    Select the Perform network measurements in 1-second intervals checkbox.
  6. 6.
    Click Save Changes.
The screenshot below shows how the data looks with packet spreading enabled, using a test with packet loss:

Auto-Detect Now in Open Beta for Endpoint Agents Using Automated Session Tests for Microsoft Teams

The auto-detect feature is now in open Beta for Endpoint Agent users, focused on Microsoft Teams.
Previously, when configuring automated session tests (ASTs), it has been difficult for customers to know what the best test configuration was to monitor a specific application. This was especially true if targeting an application that ran hundreds of nodes spread around the globe and that were accessed through different scenarios (for example, different locations, different network configurations, etc).
In order to make the configuration of ASTs easier, ThousandEyes has developed a new feature that will allow you to select an "auto-detect" protocol configuration that will automatically select the best configuration to monitor the selected application.
In order for the auto-detect configuration to work correctly, the TCP driver should be installed. This is because some configurations may rely on TCP.
When configuring an AST within the ThousandEyes dashboard, you will now see an Auto-detect option under protocol, which will automatically select the most reachable protocol for the selected application.

Enhanced Priorities for Endpoint Tests

Previously, the priority of a test to be executed on an Endpoint Agent followed a simple priority line. The 10-slot limit per agent first focused on tests where the agent was selected within the Specific Agents field. After that, the tests applied to a specific Label were selected. Finally, if there were still available slots for an agent, the tests that were configured for All Agents were executed.
In order to provide you more flexibility on the prioritization of the tests, you can give priority to tests, both in the creation of a test or directly in the Tests Settings dashboard. Prioritized tests will now be selected over non-prioritized tests, each of them internally following the previous simple priority line (i.e., Specific Agents > Labels > All Agents).

Enhanced Endpoint Labels

We have enhanced the definition of Endpoint Agent labels. In particular, you can now define whether a label includes or does not include agents that match the following filters:
  • Location
  • Connection
  • Public Network
  • Agent
  • Agent Type
  • Platform
  • Gateway
  • Proxy Address
  • VPN Address
  • SSID
  • IP Address Family
  • Username
  • Local Networks (Private)
  • Hostname
In addition, you can now use wildcards (i.e., *) within the SSID, Username and Hostname fields in order to define the desired target (e.g., Hostname in "SF-*").
For more information, see Configure Endpoint Agent Labels.

New Cloud Agents

New Cloud Agents have been added to the following locations:
  • Durban, South Africa
  • Durban, South Africa (IPv6)
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.

New Webex Cloud Agent

A new Webex Cloud Agent has been added to the following location:
  • Ashburn, VA, USA
For more information on how to use Webex Cloud Agents, see the product documentation.

Minor Enhancements

  • We have changed our Report Snapshot email subject from Report - 'Snapshot Name' to Snapshot - 'Snapshot Name' in order to remain future-proof with upcoming changes to our reporting and dashboarding structure.
  • You can now modify interface groups via the API, providing parity with the current solution in our product UI.
  • Activity logs are now generated when Endpoint Agent tests are created using the API, in the same way that they are when tests are created in the UI.

2022-07-07 Bug Fixes

  • An issue was resolved where a link to fetch more data on some Endpoint API endpoints was provided even when no more data was available.
  • An issue with our v6 Integrations API that was preventing users from using the .json format has been resolved. When a customer used .json, we were incorrectly sending back a 404 error. This has been corrected and you can use the .json format in our v6 Integrations API as expected.
  • An issue that was preventing users from duplicating our built-in dashboards has been resolved.
  • An issue that was preventing the update of the Endpoint Agent usage after deleting Endpoint Agents has been resolved. You will now see that as soon as an agent is deleted, the Endpoint Agent usage is reduced.
  • An issue where users without the "Can add or modify tests to consume over 100% resources" permission were able to configure tests that increased the organisation's usage above the purchased subscription amount has been resolved.
  • An issue was resolved where some Internet Insights customers did not have the default Application Outage alert rule, which should have been created automatically at provisioning. This has been corrected, and impacted customers will now begin receiving these alerts.
  • An issue was resolved that was preventing Network Outage alerts from clearing in production. Alerts should now clear as expected.


Japanese Language Support

ThousandEyes Customer Engineering team now offers technical support in the Japanese language as outlined in Getting Support from ThousandEyes.

New Cloud Agents

New Cloud Agents have been added to the following locations:
  • Detroit, MI, USA (IPv6)
  • Melbourne, Australia (Optus)
  • Melbourne, Australia (Optus) (IPv6)
  • Melbourne, Australia (Telstra)
  • Melbourne, Australia (Telstra) (IPv6)
  • Sydney, Australia (Telstra)
  • Sydney, Australia (Telstra) (IPv6)
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.

New Webex Cloud Agent

A new Webex Cloud Agent have been added to the following location:
  • Mumbai, India
For more information on how to use Webex Cloud Agents, see the product documentation.

Minor Enhancements

  • The visualization of Endpoint Agent Browsers Sessions when the visited page is cached has been improved. It will now explicitly show that the connection was cached in the page details and, as a result, the path visualization won't show any network nodes (for example, Connection, VPN, or Proxy) between the agent and the destination. This way, users will no longer be confused by seeing network metrics for requests that didn't go through the network.
  • Enterprise Agents will now report the underlying ICMP error when agents are unable to connect in agent to agent tests.

2022-06-23 Bug Fixes

  • An issue that was not allowing customers to define Endpoint Agent HTTP server tests with Customer Headers longer than 1024 characters has been resolved. The limit has been extended and up to 3000 characters is now supported.
  • An issue was found where Endpoint Agent labels could not be created or updated if they contained non-latin characters. This issue has been resolved, and non-latin characters can be used as expected.
  • An issue was found with the endpoint-data/user-sessions API endpoint where it was provided with a "pages[next]" element when no more data was available. This has been resolved.
  • An issue has been resolved where log messages were not generated in the activity log when Endpoint Agent scheduled tests were modified by internal operations (for example, tests being disabled as there were no agents associated with it).


New Cloud Agents

New Cloud Agents have been added to the following locations:
  • Antwerp, Belgium (Telenet Belgacom)
  • Antwerp, Belgium (Telenet Belgacom) (IPv6)
  • Buffalo, New York, USA
  • Buffalo, New York, USA (IPv6)
  • Liege, Belgium (Telenet Belgacom)
  • Liege, Belgium (Telenet Belgacom) (IPv6)
  • Sacramento, CA, USA
  • Sacramento, CA (IPv6)
  • Slough, England
  • Slough, England (IPv6)
  • Sydney, Australia (Optus)
  • Sydney, Australia (Optus) (IPv6)
For a full list of Cloud Agents, see ThousandEyes Cloud Agent Locations.

New Alerter Engine for Network Outage Alerts

Internet Insights Network Outage alerts are being migrated to a new alerts engine, which is shared with Application Outage alerts. As part of the migration, the behavior of the Network Outage alerts Affected Interfaces condition will be updated to match the behavior of the Application Outages alerts Affected Servers condition (selecting a specific set of tests will filter but not reduce the size of the set of interfaces reported in the Network Outage alert).

Updated VMware Support for ThousandEyes Virtual Appliance

The OVF package included in the ThousandEyes Virtual Appliance has been updated to remove support for end-of-life releases of VMware ESXi and to update the OVF specified VM hardware version to version 13.
For installation instructions, see How to Set Up the Virtual Appliance.

Minor Enhancements

  • Previously, ThousandEyes assumed that Internet Explorer was present by default on all Windows devices. This is no longer the case, and from Endpoint Agent client v1.119.0 and later, we now explicitly probe for this when displaying the supported browser icons on Windows OS.

2022-06-07 Bug Fixes

  • An issue was found where the incorrect assignment of network labels in Endpoint Agents resulted in tests not running as expected. This has been resolved.
  • An issue was resolved that caused Endpoint Agents to be assigned the incorrect geolocation for a small set of IP addresses.
  • An issue was found where some alert webhook payloads were not correctly sending test labels associated with the test that triggered an alert. This has been resolved.
  • An issue was found with the ThousandEyes PagerDuty integration where the alert severity values were not correctly mapped to the PagerDuty Severity field. This has been resolved.
  • Previously, Endpoint Agent users would see a mismatch between the millisecond value they selected in their Scheduled Test alert rule configuration versus what was being displayed in the UI. This was purely a visual bug, as the alert rule configuration was still capturing the correct millisecond value entered by the customer and alerting appropriately, and has been resolved.
  • An issue that allowed the creation of Endpoint Agent labels with invalid machine IDs through the API has been resolved. Extra validation has been added in the API to make sure only consistent labels can be created.
  • An issue where the Enterprise Agent repeatedly failed to run after being restarted, if there wasn't enough disk space available, has been resolved.

Endpoint Agent Client v. 1.119.1 Bug Fixes

  • Previously, an issue resulted in Windows 11 devices being identified as Windows 10 by the Endpoint Agent client. This has been resolved.