ThousandEyes Incident History

1. resolvedOct 27 · 18:30 UTC

   ThousandEyes has identified an issue with Endpoint Agent Test views not loading. This has been identified and is now resolved.

Reported by ThousandEyes on their status page.

1. ResolvedOct 27 · 18:30 UTC

   ThousandEyes has identified an issue with Endpoint Agent Test views not loading. This has been identified and is now resolved.

Reported by ThousandEyes on their status page.

1. resolvedOct 27 · 19:11 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. ResolvedOct 27 · 19:11 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. CompletedOct 27 · 12:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 24 · 08:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 22 · 04:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. resolvedOct 14 · 19:18 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. CompletedOct 20 · 21:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 26 · 12:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. resolvedOct 13 · 19:50 UTC

   This incident is now resolved.
   Please follow the instructions using one of the options below if any of your Enterprise Agents cannot automatically update themselves.
   

   ---

   Option 1: Add the New DNSSEC Key

   Adding the new DNSSEC key can restore the Agent’s connection to the ThousandEyes platform. After the Enterprise Agent reconnects, the Test Data collected since the Enterprise Agent’s last check-in should be retroactively pushed to the Test timeline as long as the Test Data remains in the Enterprise Agent’s local cache.
   The local cache retains Test Data for up to 36 hours after connectivity is lost; data older than that may be permanently lost.

   Cisco Application-Hosting (CAF) Agent

   Access the CLI of the Cisco device hosting the CAF Agent.
   Open a terminal in the app container:
   app-hosting connect <app-id> session bash
   Append the new DNSSEC key to the key file (note – this is all one line):
   echo ". 172800 IN DNSKEY 257 3 8 AwEAAa96jeuknZlaeSrvyAJj6ZHv28hhOKkx3rLGXVaC6rXTsDc449/cidltpkyGwCJNnOAlFNKF2jBosZBU5eeHspaQWOmOElZsjICMQMC3aeHbGiShvZsx4wMYSjH8e7Vrhbu6irwCzVBApESjbUdpWWmEnhathWu1jo+siFUiRAAxm9qyJNg/wOZqqzL/dL/q8PkcRU5oUKEpUge71M3ej2/7CPqpdVwuMoTvoB+ZOT4YeGyxMvHmbrxlFzGOHOijtzN+u1TQNatX2XBuzZNQ1K+s2CXkPIZo7s6JgZyvaBevYtxPvYLw4z9mR7K2vaF18UYH9Z9GNUUeayffKC73PYc=" >> /usr/lib/te-agent/dns-rootserver.key

   Docker Agent

   Run the following command (note – this is all one line) on the Docker host, replacing <CONTAINER_NAME> with the Agent’s container name:
   docker exec <CONTAINER_NAME> sh -c 'echo ". 172800 IN DNSKEY 257 3 8 AwEAAa96jeuknZlaeSrvyAJj6ZHv28hhOKkx3rLGXVaC6rXTsDc449/cidltpkyGwCJNnOAlFNKF2jBosZBU5eeHspaQWOmOElZsjICMQMC3aeHbGiShvZsx4wMYSjH8e7Vrhbu6irwCzVBApESjbUdpWWmEnhathWu1jo+siFUiRAAxm9qyJNg/wOZqqzL/dL/q8PkcRU5oUKEpUge71M3ej2/7CPqpdVwuMoTvoB+ZOT4YeGyxMvHmbrxlFzGOHOijtzN+u1TQNatX2XBuzZNQ1K+s2CXkPIZo7s6JgZyvaBevYtxPvYLw4z9mR7K2vaF18UYH9Z9GNUUeayffKC73PYc=" >> /usr/lib/te-agent/dns-rootserver.key'

   Linux Package Agent

   Append the new DNSSEC key to the key file (note – this is all one line):
   echo ". 172800 IN DNSKEY 257 3 8 AwEAAa96jeuknZlaeSrvyAJj6ZHv28hhOKkx3rLGXVaC6rXTsDc449/cidltpkyGwCJNnOAlFNKF2jBosZBU5eeHspaQWOmOElZsjICMQMC3aeHbGiShvZsx4wMYSjH8e7Vrhbu6irwCzVBApESjbUdpWWmEnhathWu1jo+siFUiRAAxm9qyJNg/wOZqqzL/dL/q8PkcRU5oUKEpUge71M3ej2/7CPqpdVwuMoTvoB+ZOT4YeGyxMvHmbrxlFzGOHOijtzN+u1TQNatX2XBuzZNQ1K+s2CXkPIZo7s6JgZyvaBevYtxPvYLw4z9mR7K2vaF18UYH9Z9GNUUeayffKC73PYc=" >> /usr/lib/te-agent/dns-rootserver.key
   Please note: Customers will still need to complete Option 2 for a long-term fix, even if Option 1 is applied in the interim.

   ---

   Option 2: Upgrade the Agent Image

   Cisco Application-Hosting (CAF) Agent

   Run the following command on the Cisco device hosting the CAF Agent:
   If you have x86 architecture:
   app-hosting upgrade appid {application-name} package https://downloads.thousandeyes.com/enterprise-agent/thousandeyes-enterprise-agent-x86_64-5.2.1.cisco.tar
   If you have ARM architecture:
   app-hosting upgrade appid {application-name} package https://downloads.thousandeyes.com/enterprise-agent/thousandeyes-enterprise-agent-aarch64-5.2.1.cisco.tar
   Please note: Upgrading the Cisco App-Hosting Image (CAF) Agent image will clear the Enterprise Agent’s local Test Data cache. The Test timeline will have a data gap for the affected period, and the cached Test Data will not be backfilled.

   Docker Agent

   Use the latest image tag (or latest-agent if you are not using BrowserBot), or Docker image version 0.105.0 or later.
   docker pull <name> docker stop <running-agent> docker rm <running-agent> docker run <same options as previous launch>
   

   Linux Package Agent

   Upgrade the te-agent package to the latest version (1.247.2) using the system package manager (yum, dnf, or apt, depending on your distribution).
   For more details, see Upgrading Enterprise Agents.

Reported by ThousandEyes on their status page.

1. investigatingOct 10 · 14:50 UTC

   London, England (Webex Calling) is currently experiencing a networking outage impacting service connectivity. The Cisco Webex Infrastructure team is actively investigating the issue and performing troubleshooting efforts to identify the root cause and restore normal operations as quickly as possible. Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitter Affected Cloud Agents: London, England (Webex Calling) Start time: Oct 02, 2026, 11:35 PM UTC

Reported by ThousandEyes on their status page.

1. InvestigatingOct 10 · 14:50 UTC

   London, England (Webex Calling) is currently experiencing a networking outage impacting service connectivity. The Cisco Webex Infrastructure team is actively investigating the issue and performing troubleshooting efforts to identify the root cause and restore normal operations as quickly as possible.Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitterAffected Cloud Agents:London, England (Webex Calling)Start time: Oct 02, 2026, 11:35 PM UTC

Reported by ThousandEyes on their status page.

1. resolvedOct 15 · 21:42 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. ResolvedOct 15 · 21:42 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. resolvedOct 12 · 23:15 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. resolvedOct 10 · 03:48 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. CompletedOct 22 · 21:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 22 · 12:01 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 22 · 12:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 20 · 09:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. resolvedOct 5 · 18:23 UTC

   This incident has been resolved.

Reported by ThousandEyes on their status page.

1. CompletedOct 22 · 13:01 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 14 · 04:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. CompletedOct 20 · 10:00 UTC

   The scheduled maintenance has been completed.

Reported by ThousandEyes on their status page.

1. investigatingAug 6 · 12:48 UTC

   Frankfurt, Germany (Webex Calling) is currently experiencing a networking outage impacting service connectivity. The Cisco Webex Infrastructure team is actively investigating the issue and performing troubleshooting efforts to identify the root cause and restore normal operations as quickly as possible. Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitter Affected Cloud Agents: Frankfurt, Germany (Webex Calling) Start time: Jun 23, 2026, 10:36 PM UTC

Reported by ThousandEyes on their status page.