ThousandEyes Outage History

Started Oct 14, 2026, 05:45 PM UTC· resolved Oct 14, 2026, 07:18 PM UTC

1. investigating Oct 14, 2026, 05:45 PM UTC

   Summary We are currently investigating a possible degradation impacting dashboards in US2 Region Impact Dashboards showing data for Dynamic Tests - Network · Endpoint Experience category are not showing correct data since 4PM UTC

2. monitoring Oct 14, 2026, 05:59 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 14, 2026, 07:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 11, 2026, 05:21 PM UTC· resolved Oct 13, 2026, 07:50 PM UTC

1. identified Oct 11, 2026, 05:21 PM UTC

   Cloud and enterprise agents are showing failure message in DNSSEC tests due intermediate validation. The issue started at 14:00 PM UTC.

2. identified Oct 11, 2026, 08:19 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 11, 2026, 10:31 PM UTC

   A fix has been implemented. Operations will continue to monitor performance.

4. monitoring Oct 12, 2026, 06:32 PM UTC

   ThousandEyes is currently monitoring the fix. ThousandEyes Enterprise Agents will receive the fix and recover automatically. Commercial customers with FIPS-dependent configurations will not receive the fix automatically. Commercial customers with offline Agents should reach out to ThousandEyes Support to manually apply the fix. ThousandEyes for Government (FedRAMP) customers will have FIPS-dependent configurations, and will not receive the fix automatically. Please reach out to ThousandEyes FedRAMP Support to manually apply the fix.

5. resolved Oct 13, 2026, 07:50 PM 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 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 with the Agent’s container name: docker exec 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 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 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 docker stop docker rm docker run 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.

Read the full incident report →

Started Oct 10, 2026, 04:47 AM UTC· resolved Oct 15, 2026, 09:42 PM UTC

1. investigating Oct 10, 2026, 04:47 AM UTC

   Dashboard widgets showing data for Events datasource are affected in US1 region. The service is affected/not showing data since 7 PM PDT.

2. monitoring Oct 10, 2026, 05:58 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 15, 2026, 09:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2026, 08:14 PM UTC· resolved Oct 12, 2026, 11:15 PM UTC

1. investigating Oct 09, 2026, 08:14 PM UTC

   ThousandEyes for Government (FedRAMP) Usage and billing page data may show stale data for some customers

2. monitoring Oct 10, 2026, 12:14 AM UTC

   A fix has been implemented and we are monitoring the results. The usage data is reflecting now correctly, no more customer impact

3. resolved Oct 12, 2026, 11:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2026, 07:32 AM UTC· resolved Oct 10, 2026, 03:48 AM UTC

1. investigating Oct 09, 2026, 07:32 AM UTC

   Starting at 06:05 UTC on October 9, 2026, customers using Cloud and Enterprise Agent (CEA) Multi-Test Views and Agent Views may experience slow page loading or temporary timeouts due to elevated latency in backend data retrieval. Scheduled test executions, agent data collection, and alert evaluations remain fully operational. Our engineering team is actively investigating the issue, and we will share our next update in another 30 minutes (or as soon as new information becomes available).

2. identified Oct 09, 2026, 08:03 AM UTC

   We have identified the cause of the backend latency affecting Cloud and Enterprise Agent (CEA) Multi-Test Views and Agent Views. Latency levels have subsided and response times across all views are returning to standard baseline.

3. monitoring Oct 09, 2026, 08:59 AM UTC

   The increased latency affecting Cloud and Enterprise Agent (CEA) Multi-Test Views and Agent Views subsided around 07:06 UTC, and performance across all views has remained stable since. We are currently monitoring platform and system performance to confirm full stability before resolving the incident

4. resolved Oct 10, 2026, 03:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 05, 2026, 09:57 AM UTC· resolved Oct 05, 2026, 06:23 PM UTC

1. investigating Oct 05, 2026, 09:57 AM UTC

   Customers accessing views across the ThousandEyes platform may experience errors loading test and agent metadata, or observe views reporting that no data is available. Test execution and raw data ingestion remain operational, but data visualization in the web UI is currently impacted across query timeframes

2. identified Oct 05, 2026, 10:07 AM UTC

   The cause of the issue has been identified, and corrective action has been taken. Service recovery is currently in progress, and platform performance is improving. Customers may continue to experience brief delays or errors while loading views as systems fully restore. We are closely monitoring the recovery and will provide another update shortly.

3. monitoring Oct 05, 2026, 10:26 AM UTC

   A fix has been implemented, and platform services have been restored. All ThousandEyes views are loading data as expected. Our engineering team is continuing to monitor platform performance to ensure ongoing stability.

4. monitoring Oct 05, 2026, 10:51 AM UTC

   Platform services remain stable and all views continue to load data normally following the implemented fix. Our engineering and operations teams are actively monitoring performance to ensure continued reliability. A final update will be provided once full recovery is confirmed.

5. resolved Oct 05, 2026, 06:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 06:12 PM UTC· resolved Sep 25, 2026, 12:05 AM UTC

1. investigating Sep 24, 2026, 06:12 PM UTC

   Summary The Internet Insights “Views” timeline is unresponsive and/or not displaying the topology of recent application outages. Status Our engineering team is actively working to resolve this issue. We will provide updates as soon as more information becomes available.

2. investigating Sep 24, 2026, 09:13 PM UTC

   We are continuing to investigate this issue.

3. investigating Sep 25, 2026, 12:05 AM UTC

   Issue has been resolved.

4. resolved Sep 25, 2026, 12:05 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 11, 2026, 02:12 PM UTC· resolved Sep 11, 2026, 04:39 PM UTC

1. investigating Sep 11, 2026, 02:12 PM UTC

   Customers may encounter errors when editing Custom Webhook integrations. Custom Webhook functionality itself is not affected. We are investigating the issue

2. monitoring Sep 11, 2026, 02:28 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 11, 2026, 04:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 08, 2026, 05:01 AM UTC· resolved Sep 08, 2026, 11:18 AM UTC

1. investigating Sep 08, 2026, 05:01 AM UTC

   US1 region customers with BGP private collectors might experience BGP session disconnections

2. resolved Sep 08, 2026, 11:18 AM UTC

   Issue affecting BGP Private Collector peering in the US1 region has been identified and resolved.

Read the full incident report →

Started Aug 26, 2026, 04:52 PM UTC· resolved Aug 26, 2026, 09:31 PM UTC

1. identified Aug 26, 2026, 04:52 PM UTC

   Summary: We are currently investigating a service degradation affecting Internet Insights Provider Intelligence, which began at 01:00 UTC on August 26th. Impact: Customers may be unable to view the latest hourly Provider Intelligence metrics. While performance data for 30-day, 90-day, and 180-day views remains accessible, users may experience delays in data updates for these views as well. Status: Our engineering team is actively working to resolve this issue. We will provide updates as soon as more information becomes available. ThousandEyes support is available 24 hours a day. If you have questions or require further assistance, please initiate a chat within app.thousandeyes.com to connect with a support engineer, or email [email protected].

2. monitoring Aug 26, 2026, 08:24 PM UTC

   After applying a fix, hourly Provider Intelligence metrics are once again available. Our engineering team is currently backfilling the data for the duration of the incident to ensure complete visibility.

3. resolved Aug 26, 2026, 09:31 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 26, 2026, 08:44 AM UTC· resolved Aug 27, 2026, 03:57 PM UTC

1. investigating Aug 26, 2026, 08:44 AM UTC

   Customers may encounter an error when accessing Chat with Support from the Contact Support page in the ThousandEyes application. It may remain in a loading state and fail to open. As a temporary workaround, please refresh the page. ThousandEyes Engineering team is investigating the issue.

2. monitoring Aug 26, 2026, 09:04 PM UTC

   A fix has been deployed, and we are monitoring the results. Please log out of ThousandEyes and log back in before starting a new chat. This ensures the update takes effect.

3. resolved Aug 27, 2026, 03:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2026, 09:00 AM UTC· resolved Aug 27, 2026, 04:11 PM UTC

1. investigating Aug 25, 2026, 09:00 AM UTC

   Customers may encounter an error when accessing the Contact Support page within the ThousandEyes application. ThousandEyes Engineering teams are investigating the issue. Please send an email to our Support team at [email protected] to open a new case

2. investigating Aug 25, 2026, 07:42 PM UTC

   We are continuing to investigate this issue.

3. identified Aug 25, 2026, 11:33 PM UTC

   We have identified the issue preventing access to the Contact Support page. ThousandEyes Engineering is actively deploying a fix to affected regions.

4. monitoring Aug 25, 2026, 11:47 PM UTC

   ThousandEyes Engineering has remediated the issue for customers accessing the Contact Support page. Functionality is restored and we will continue to monitor.

5. resolved Aug 27, 2026, 04:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 21, 2026, 05:50 PM UTC· resolved Aug 21, 2026, 06:50 PM UTC

1. resolved Aug 21, 2026, 08:40 PM UTC

   Between 8/20/26 at 17:50 UTC and 8/21/26 at 18:50 UTC, alerts configured with dynamic baselines or sensitivity conditions may be delayed or sent incorrectly.

Read the full incident report →

Started Aug 21, 2026, 08:19 AM UTC· resolved Aug 22, 2026, 01:23 AM UTC

1. investigating Aug 21, 2026, 08:19 AM UTC

   Starting at 07:15 UTC, some users in the EU1 region are unable to login. API requests are unaffected. We are investigating the issue

2. identified Aug 21, 2026, 08:35 AM UTC

   A fix has been implemented and we are seeing signs of recovery. We are monitoring the results.

3. monitoring Aug 21, 2026, 09:00 AM UTC

   Monitoring confirms the fix has been successful and users can login. We will continue to monitor.

4. resolved Aug 22, 2026, 01:23 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 20, 2026, 07:28 AM UTC· resolved Aug 20, 2026, 11:46 AM UTC

1. investigating Aug 20, 2026, 07:28 AM UTC

   Starting at 8/20/26 at 3:15 AM UTC, users may have seen some delays in triggering Network & App Synthetics alerts or clearing existing Network & App Synthetics alerts. We are currently investigating this issue

2. identified Aug 20, 2026, 08:20 AM UTC

   We have identified the issue and implemented mitigation steps. We expect the system to return to normal within the next hour and are continuing to monitor recovery.

3. monitoring Aug 20, 2026, 11:08 AM UTC

   The issue is successfully mitigated. All services have returned to normal operation and are performing as expected. We will continue to monitor the systems closely to ensure ongoing stability.

4. resolved Aug 20, 2026, 11:46 AM UTC

   This issue has been resolved. All services have returned to normal operation and are performing as expected.

Read the full incident report →

Started Aug 09, 2026, 06:01 AM UTC· resolved Aug 09, 2026, 06:35 AM UTC

1. investigating Aug 09, 2026, 06:01 AM UTC

   We are currently investigating this issue to determine if users are experiencing delays with Endpoint scheduled tests. We will update this announcement if a service degradation is identified.

2. resolved Aug 09, 2026, 06:35 AM UTC

   The incident has been resolved

Read the full incident report →

Started Aug 07, 2026, 02:13 PM UTC· resolved Aug 12, 2026, 11:58 AM UTC

1. identified Aug 07, 2026, 02:13 PM UTC

   Summary: We are investigating intermittent delays and login failures affecting a subset of users authenticating in our US regions since approximately 12:07 UTC. We have identified a degradation in our identity services and are working to resolve it. Impact: Users may experience delays or issues when logging into the ThousandEyes platform in the US1 and US2 regions. Status: Our engineering team is working to resolve this issue. We will provide further updates as they become available. ThousandEyes support is available 24 hours a day. Please open a chat from within app.thousandeyes.com to speak with a support engineer, or email [email protected] if you have any questions.

2. monitoring Aug 07, 2026, 02:40 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 12, 2026, 11:58 AM UTC

   The incident has been resolved

Read the full incident report →

Started Jul 23, 2026, 01:48 PM UTC· resolved Jul 23, 2026, 04:57 PM UTC

1. investigating Jul 23, 2026, 01:48 PM UTC

   Dashboard widgets are not showing the last 30 minutes of data for the Endpoint Scheduled Tests data source in US1. We are investigating the issue.

2. monitoring Jul 23, 2026, 02:40 PM UTC

   The display of data in Dashboard widgets for the Endpoint Experience Scheduled Tests data source in US1 is delayed by approximately 20 minutes. Data processing has resumed, and widgets are expected to be up to date by Jul 23rd at 14:40 UTC.

3. monitoring Jul 23, 2026, 02:52 PM UTC

   Data availability has been restored and we are monitoring the system.

4. resolved Jul 23, 2026, 04:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 21, 2026, 03:05 PM UTC· resolved Jul 22, 2026, 04:44 PM UTC

1. monitoring Jul 21, 2026, 03:05 PM UTC

   Summary We have identified an issue causing delays in displaying Endpoint Experience Local Network data within Dashboards in the US2 Region, beginning at 14:00 UTC. Impact Users may experience delays in data updates for dashboard widgets showing Endpoint Experience Local Network metrics. Status Our engineering team has applied a fix, and we are currently monitoring the environment to ensure full service restoration.

2. resolved Jul 22, 2026, 04:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 15, 2026, 10:51 PM UTC· resolved Jul 16, 2026, 12:17 AM UTC

1. investigating Jul 15, 2026, 10:51 PM UTC

   Starting 22:10 UTC we have identified a hardware issue in the EU region causing issues receiving and displaying data for Cloud and Enterprise Agent tests. Our team is investigating and working on remediation. Alerts and visualization of data may be delayed

2. investigating Jul 15, 2026, 10:52 PM UTC

   We are continuing to investigate this issue.

3. investigating Jul 15, 2026, 10:53 PM UTC

   We are continuing to investigate this issue.

4. investigating Jul 15, 2026, 11:25 PM UTC

   Cloud and Enterprise Agent data continues to be intermittently delayed for visualization, API, and alerting. We are continuing to investigate and work on mitigation.

5. monitoring Jul 15, 2026, 11:59 PM UTC

   Cloud and Enterprise Agent data is correctly ingesting without delays. All services are operating normally and we continue to monitor.

6. resolved Jul 16, 2026, 12:17 AM UTC

   This incident has been resolved

Read the full incident report →

Started Jul 11, 2026, 02:42 PM UTC· resolved Jul 11, 2026, 04:59 PM UTC

1. identified Jul 11, 2026, 02:42 PM UTC

   Delays in Endpoint test data in US1 region Impact: Endpoint test data is delayed in platform on the US1 region. Start Time: Jul 11, 2026, 14:58 PM UTC

2. monitoring Jul 11, 2026, 03:13 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 11, 2026, 04:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 09, 2026, 11:57 AM UTC· resolved Aug 06, 2026, 11:38 AM UTC

1. investigating Jul 09, 2026, 11:57 AM UTC

   Ongoing outage Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitter Start time: 2026-07-09 02:00:00 UTC Affected Cloud Agents: - Daejeon, South Korea (SK Telecom - AWS Wavelength) - Seoul, South Korea (SK Telecom - AWS Wavelength)

2. resolved Aug 06, 2026, 11:38 AM UTC

   https://status.thousandeyes.com/incidents/2yf1r9hs84j2

Read the full incident report →

Started Jul 08, 2026, 03:28 PM UTC· resolved Jul 08, 2026, 07:29 PM UTC

1. investigating Jul 08, 2026, 03:28 PM UTC

   We are investigating the issue affecting login to the ThousandEyes platform. EU customer are not impacted.

2. investigating Jul 08, 2026, 03:41 PM UTC

   We are continuing to work on a fix for this issue

3. monitoring Jul 08, 2026, 04:03 PM UTC

   A fix has been implemented and we are monitoring the results. Users should now be able to authenticate correctly and the team is continuing work on mitigation.

4. monitoring Jul 08, 2026, 04:26 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Jul 08, 2026, 07:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 02, 2026, 03:27 PM UTC· resolved Aug 06, 2026, 12:16 PM UTC

1. investigating Jul 02, 2026, 03:27 PM UTC

   Several Cloud Agents in Chennai, India, are currently experiencing a service outage due to an emergency data center migration. Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitter. Start time: 2026-07-02 09:00:00 UTC Affected Cloud Agents: Chennai, India (JIO) Chennai, India - IPv6 (JIO) Chennai, India (Vodafone Idea) Chennai, India - IPv6 (Vodafone Idea) Chennai, India (Bharti Airtel) Chennai, India - IPv6 (Bharti Airtel). We are working on these issues.

2. resolved Aug 06, 2026, 12:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2026, 12:38 PM UTC· resolved Jul 02, 2026, 03:21 PM UTC

1. investigating Jul 01, 2026, 12:38 PM UTC

   Cloud Agent in Chennai, India (Reliance) is currently experiencing a service outage due to an emergency data center migration. Impact: Possible missing test rounds, destination unreachable, high loss/latency/jitter Start time: 2026-07-01 09:00:00 UTC Affected Cloud Agents: Chennai, India (Reliance) Chennai, India - IPv6 (Reliance)

2. resolved Jul 02, 2026, 03:21 PM UTC

   This incident has been resolved

Read the full incident report →