Our main use case for ThousandEyes is monitoring external applications like Microsoft 365, Salesforce, ServiceNow, or multi-cloud infrastructure. Our primary use case is gaining visibility into SaaS applications and public cloud connections that run over network infrastructure we don't own. Before ThousandEyes, when a SaaS application slowed down, we couldn't tell if the problem was our local network, the ISP, or the application provider. ThousandEyes gives us a hop-by-hop path visualization, so we immediately isolate fault domains and share evidence directly with third-party vendors to resolve issues.

We had a Monday morning where hundreds of remote users reported that Microsoft 365 or Teams was lagging with dropping calls. Historically, our IT helpdesk would have wasted hours checking local Wi-Fi, restarting firewalls, or opening tickets with our internal ISP. Using our path visualization view, we quickly noticed that our internal network and local ISP hops were completely clean. However, a fourth hop deep into a major transit provider's peering, latency spiked from 15 ms to 280 ms with 25% packet loss. The outcome was that instead of guessing, we generated a live URL with a path trace and sent it directly to the Tier 3 team. The transit provider acknowledged a routing loop on their end and fixed it within 45 minutes. This saved our infrastructure team at least three to four hours of useless internal troubleshooting.

What makes it unique about how our team leverages ThousandEyes is that instead of just testing a specific endpoint, ThousandEyes aggregates anonymous test data from thousands of agents globally across ISPs, SaaS providers, and cloud data infrastructure. ThousandEyes offers Internet Insights, which acts as a weather radar of the public internet before our own helpdesk even receives a ticket. We can see if a massive outage is sweeping through AWS East or Cloudflare or a regional Tier 1 ISP. We don't have to waste time running local diagnosis because collective intelligence immediately shows us macro-level internet outages.

View full review »

We started using ThousandEyes after we moved to SD-WAN. Because we started using DIA circuits, which are not like MPLS ones, the DIA circuit was having so many issues, so we obtained this tool. We started monitoring the underlays first, from our site to our data center, from our sites to any destination. If any client or user is having an issue with some specific destinations, we monitor that. We use the Endpoint Agents for troubleshooting purposes.

We are using two different use cases. One is a standard test that we are running from all our sites as part of our standard protocol. Every site has those tests. The other part is on demand. Whenever we feel that something needs some more deep troubleshooting, we bring up that test for that troubleshooting purpose only. Apart from this, we are using the underlay for SaaS applications, DNS services, and DNS tests. We are using all parts of the Enterprise Agent and Endpoint Agents.

View full review »

My main use cases for ThousandEyes at my current company are leveraging ThousandEyes for digital experience, internet, and internet performance. I'm using ThousandEyes for full network path visualization and network performance, application delivery. I also leverage ThousandEyes for overall ISP, public cloud, edge service monitoring, and what we call digital experience monitoring, which we're using ThousandEyes' endpoint agents to monitor user-side network health, metrics, and application responsiveness. I'm also using ThousandEyes for website and SaaS delivery optimization as well.

I use ThousandEyes for digital experience monitoring by leveraging their endpoint agents to monitor user-side network health, such as Wi-Fi and VPN metrics and application responsiveness to ensure that our applications are performing, are performant and are meeting and exceeding delivery expectations.

We use ThousandEyes in conjunction with our full end-to-end, full-stack observability offering, and we're using ThousandEyes to address critical performance issues. This is to be proactive about knowing how to address issues before they arise and how to ensure that our applications are always performant.

View full review »

We were using ThousandEyes to monitor our Cisco SD-WAN and some Juniper switches and SBCs and our whole network infrastructure. We installed ThousandEyes agents on our multiple devices to monitor their activities. We were also using it for DNS servers.

View full review »

I am a running consultant for ThousandEyes, and as a consultant, I have to perform the build case as well as running on capacity management, as well as the end-to-end connectivity monitoring through ThousandEyes.

I am working on multiple customers currently. For some customers, I have to build ThousandEyes agent on end-to-end agent or Enterprise agent, and I have to build those and run the test on those agents so that I can monitor the customer network. For other customers, I have to try to identify the incident raised by the customer CSM or something similar, and I try to find out the RCA for those incidents.

Apart from these two use cases, I have to manage the users as well, creating the users, managing the users, and to update the certificates and other items on ThousandEyes portal for the customers.

View full review »

ThousandEyes is utilized primarily for WAN observability, where we monitor the WAN circuit hop-by-hop from end-to-end to gain end-to-end visibility for application monitoring of Microsoft Teams, voice, and other critical applications in our organization. Whenever we experience any kind of alerts for these applications, we immediately investigate through ThousandEyes. ThousandEyes has a capability to integrate with the ServiceNow tool, where we receive notifications and alert integration, which provides us advanced notification and helps our engineers navigate the problem and identify exactly where it is occurring in the routing path.

Recently, we experienced one of our users having slowness while accessing their Teams calls. When we took the individual user's account details and diagnosed those reports in ThousandEyes with the username and the location, within a second, we were able to see exactly where the high latency and packet loss was happening. Due to this, the user was experiencing slowness while accessing their application. This helped us to immediately switch the route path from the primary to the redundant secondary link, which reduced the high latency and packet loss and also mitigated the problem.

Since we are using ThousandEyes at an enterprise level, this agent helps us to understand the latency, jitter, and intermittent performance of the applications and compare between the hops how exactly this latency, packet loss, or jitter is occurring. It helps us to rectify instantly where the abnormal path is and which path has no issues. If you have redundancy in place, that will work.

View full review »

My main use case for ThousandEyes is to keep an eye on vital enterprise tools, which are mostly cloud-hosted in the form of SaaS apps. It helps us provide visibility into our performance and availability and also figure out when issues occur and who is the responsible party. It is also used to monitor all our public-facing services hosted in our private data center.

A quick specific example of how we use ThousandEyes in our day-to-day work is that we usually use it for observability purposes, monitoring and alerting, and identifying an issue before the customer does. We monitor nodes in the colocation facility around our location in the USA. The biggest problem that ThousandEyes addresses is being able to do off-net tests to compare our network with external networks. This allows us to create historical baselines and verify reachability for customers that may have issues getting to specific websites. Sometimes those issues are local, but ThousandEyes helps us verify if they are global or part of a larger issue.

ThousandEyes is deployed in my organization using a hybrid cloud model with AWS as our cloud provider. We purchased ThousandEyes through the AWS Marketplace.

We use ThousandEyes in our day-to-day activities to try to fix problems quickly and ensure a smooth experience for our customers.

View full review »

My main use case for ThousandEyes is troubleshooting, with a specific example being testing connectivity through IXP to ensure the fastest route in collaboration with service providers over the region.

ThousandEyes helps with troubleshooting and collaborating with service providers by providing a sample or proof of issues at a certain level, which helps us prove what's happening when service providers act as if the issue isn't from their end.

View full review »

My main use case for ThousandEyes has been for two major tasks. Previously, while I was working at HCL Tech, I used ThousandEyes to monitor the enterprise network, focusing on latency and availability for various IP addresses and domains. Currently at Sohos, I am monitoring external connectivity towards the customer API using ThousandEyes.

My current example of how I use ThousandEyes for monitoring activity towards the customer API involves monitoring the SSL certificate of the particular APIs and the URL. We recently had an issue with the SSL certificate of one of the APIs that had expired, preventing the customer from gaining access to its services. When we checked in ThousandEyes, we received notification seven days prior to its expiration to check that certificate, which is one of the useful things we have implemented in ThousandEyes. Before using it, we did not receive such proactive reports.

I am using ThousandEyes for various purposes, including monitoring test types such as HTTPS, agent-to-server tests, HTTPS servers, and SSL certificate monitoring. I use it to monitor the customer APIs to ensure that the customer is successfully able to connect with our APIs. Monitoring external connectivity through ThousandEyes is how it is useful to us as a monitoring tool.

View full review »

I have been using ThousandEyes for the past four years.

The main use case for ThousandEyes is in the visualization of paths and it also helps in troubleshooting, software optimization, and understanding where there is packet loss. It enables me to troubleshoot if there is a downtime and also provides visibility to notice if there is an internal network problem or ISP problems. These are the primary use cases. ThousandEyes enables me to be aware of any performance degradation before users report any problem or issues are being reported.

A great specific example where I used ThousandEyes in solving a problem is as a tool for troubleshooting. I use it in troubleshooting complex network applications, especially with the integration of ThousandEyes with AWS. We use it to monitor our ISP, our third-party services, and also to monitor our DNS and our software application performance. The usage of ThousandEyes really helped in creating an end-to-end visibility. Instead of guessing where there might be a network issue, ThousandEyes made it very clear whether the problem was in our internal network, ISP, or a third-party service.

ThousandEyes really helped me in noticing latency issues in our network. This really helps a lot for us to know how to improve our network, especially when it comes to performance issues or ISP issues. Also, in our cloud and SaaS performance monitoring, it helps us to monitor the actual users in our SaaS applications and also to detect packet loss outside our own infrastructure. Because our own infrastructure is hosted on AWS, ThousandEyes being hosted on AWS really helps us to detect any packet loss in our infrastructure and also notice any performance against incident periods and identify anomalies very clearly. Another good use case that helped me so well is that ThousandEyes helped me to confirm whether performance actually improved or if new issues were introduced, especially when I'm trying to monitor packet loss or latency issues.

View full review »

My main use case for ThousandEyes is to monitor third-party applications; we monitor BGP paths to the cloud, so if applications are not hosted in our own private cloud, we monitor what's going on in terms of third-party applications.

A specific example of a third-party application I monitor with ThousandEyes is a clinical system called Rio; we monitor them to know the performance because they are not hosted in our own private cloud.

Although we do monitor our own applications hosted by ourselves to see what could be going on from multiple sites into our data center if something is going wrong, my main use case for ThousandEyes remains focused on third-party applications.

View full review »

My main use cases for ThousandEyes are troubleshooting slow speeds and investigating disconnection issues that users report.

View full review »

My main use case for ThousandEyes is to monitor network performance like network input/output rates and network latencies, and it is primarily for network monitoring.

For example, I monitor network latencies, network packet usage, identify network connectivity related issues, and check the availability of network devices such as routers and switches using ThousandEyes.

View full review »

My main use case for ThousandEyes is path monitoring.

I use ThousandEyes for path monitoring to see how my traffic is flowing in my network, what the hops are in between, and then see at what hop exactly the issue occurs whenever it happens. So for example, the recent use cases that we have implemented is the hub-spoke topology for one of our customers wherein they had a hub and multiple spokes. Then we created the paths using ThousandEyes to monitor continuous performance between hub and spokes.

Other use cases would be to monitor cloud performance, checking HTTP URL availability, or web session monitoring, and others.

View full review »

My main use case for ThousandEyes is network and endpoint observability.

A specific example of how I use ThousandEyes for network and endpoint observability is running synthetic tests from endpoints against SaaS applications, as well as against egress routers.

View full review »

I have been using ThousandEyes with this company for two years. The main use case is that we would like to get insights into our calls.

Currently, we are still in the POC state with ThousandEyes, but as of now, we get insights into our calls data and telephony data, which is quite useful for us.

View full review »

We use ThousandEyes primarily for monitoring our production and BCP servers. We specifically utilize it to monitor URL alerts. We have multiple applications, and at times, URLs may go down due to patching schedules or upgrades. When that happens, ThousandEyes sends an alert, allowing us to see the exact error and client details. This helps us determine what the client is experiencing, and we can then contact the relevant team, such as L2 support, to resolve the issue. View full review »

We use ThousandEyes for monitoring and troubleshooting, especially when end-users complain about latency or poor performance. We rely on ThousandEyes to provide metrics to see if the problem is related to the local Wi-Fi or the Internet. The main goal for ThousandEyes at our company is monitoring. We also have some integration with our other monitoring systems, and we use ThousandEyes to dive deeper into specific problems when they occur.

View full review »

ThousandEyes is an AI-based element. 

I felt it is slightly more intuitive, providing more end-to-end service delivery because it’s integrated with AI.

The usage is okay. The tool is helpful. It shows the impact assessment and structures that impact.

For application and user monitoring, we have been using it for different healthcare users. We have different sales-based solutions for healthcare.

Their user monitoring is slightly more practical. We’re really using it in user monitoring and Internet insights, which include customer journeys and creating those elements. That is more practical, I felt.

A few teams are still not using it completely. A few teams are partially adopting it. Only in the US and a few parts of Europe are they use it. But in Japan and a few other Asian countries, they are not using it. Only a few units in the US and Europe are using it.

So, it might add more value as it go into network operations. In the context of healthcare organizations, it might need slight improvement. Otherwise, it is good.

I was in a pure consulting role. See, I work with McKinsey and a few other organizations. What I do is support in bridging. I’m supporting three or four healthcare institutions and also an automobile organization where I see immense potential. 

So, my role is more strategic: how the tool system would help, how it will contribute, and how it will help the product managers and product owners define the roadmap execution. Also, the service management team, how do you look into execution design? My role is more strategic. 

View full review »

We primarily use it for monitoring our corporate network, our internet service providers, and our staff's connectivity. Also, we use it to keep an eye on the performance of multiple cloud providers, each serving various functions within our organization.

View full review »

We use the solution for network monitoring.

View full review »

Our customers use ThousandEyes to monitor their voice and video applications, especially those integrated with our Cisco systems.

View full review »

The solution provides me with diverse links from ISPs.

View full review »

We usually monitor for our public prefixes and propagations and if they are getting dropped or there is a route application. It is mainly on the public-facing side or the internet-facing use case. There are other use cases, however, for me, for the work that I do, that's what I'm using a ThousandEyes for.

View full review »

ThousandEyes is basically for network monitoring.

View full review »

ThousandEyes gives companies better visibility. So it shows you the effective notes on the network layer and the application's performance for anyone inside or outside the data center. It provides deep visibility on the network, legal support, and user requests.

In addition, it shows you averages around the world, so if there's a breach or problem on the public cloud around the world, ThousandEyes notifies you of this problem and if you're affected.

View full review »

We're in security and video, and Cisco is the main product we use as far as routers and switches. It's all high-end, we do a lot of government work. Right now, we have over 4,500 users, and we've been in business for close to 16 years. 85% of our clients are businesses. At the moment we have 300 users on the cloud, and maybe 30 or 40 cameras. We are resellers and I'm a systems integrator.

View full review »

Our enterprise solution uses ThousandEyes for end-to-end point-to-cloud and network flow monitoring. We usually automate the monitoring of traffic flow with ThousandEyes.

View full review »

We use ThousandEyes to have visibility of our entire business core with approximately 70 clients.

View full review »

We use the solution on a daily basis. 

View full review »

The typical use case for this solution is for authentication devices in the network. It's for authentication in cable networks and WiFi networks and is used as well as enterprise WiFi for branch offices. The main use case, therefore, is basically for LAN and corporate WIFI.

View full review »

We primarily used the solution mainly to monitor the network latency and network quality between different sites including company and internet sites. It helped us to see the connection quality.

View full review »

ThousandEyes is primarily adopted for professional services and managed services within the company. This involves obtaining the solution, adapting it to professional and managed services, and applying comprehensive monitoring capabilities such as monitoring the enterprise network, implementing observability for end users, monitoring the ISP network, and tracking all network paths from the customer brand to the data center.

The solution is adapted to professional and managed services with this monitoring applied, and then sold to customers.

View full review »