Cisco ThousandEyes logo

    Cisco ThousandEyes

    ThousandEyes delivers Assurance for Cloud, Internet, and SaaS Performance, providing real-time visibility into network dependencies that impact application delivery. Our platform helps enterprises detect, troubleshoot, and resolve disruptions across any environment to deliver seamless digital services.

    Ratings and reviews

    4.4
    111 ratings
    2 star
    1 star
    67%
    30%
    3%
    0%
    0%
    11 AWS reviews
    |
    100 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (111)
    reviewer2924925

    Monitoring has become proactive and troubleshooting performance issues becomes faster and clearer

    Reviewed on Nov 11, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for ThousandEyes is performance monitoring, and I am using it to support the performance monitoring teams.

    A quick specific example of how my team has used ThousandEyes for performance monitoring is when there are issues with meeting room devices. ThousandEyes helps me pinpoint network problems and alert me to device failures by providing information on whether it's a network issue or a software issue.

    We use our internal process, ITSM, in ways that path visualization and hop-by-hop metrics influence how my team escalates service degradation with external transit providers and cloud hosts.

    My teams are still in a POC phase in utilizing AI-assisted anomaly detection and automated event recommendations within ThousandEyes to distinguish systemic outages from localized network blips.

    My team deployed ThousandEyes alongside traditional SNMP and flow-based monitoring tools in response to specific blind spots across underlay transit networks or cloud hops, and the POC is still ongoing.

    What is most valuable?

    The best feature ThousandEyes offers is troubleshooting. When I say troubleshooting, I do not mean the ability to quickly share troubleshooting reports or incident findings with my team.

    ThousandEyes provides a lot of reports on governance regarding its AI capabilities. It gives fairly good output concerning its accuracy and reliability.

    ThousandEyes has positively impacted my organization by assisting in troubleshooting devices and providing operational support. It has helped with troubleshooting devices and operational support, which has resulted in a correct reduction in the time to resolve issues and improved collaboration between teams.

    After introducing ThousandEyes data, great collaboration tool changes occurred in my cross-functional triage workflows between NetOps, SecOps, and service desk teams, allowing us to share information across teams.

    For how long have I used the solution?

    I have just recently started using ThousandEyes, only for one month.

    What do I think about the stability of the solution?

    I find ThousandEyes stable.

    What do I think about the scalability of the solution?

    Its scalability is great.

    How are customer service and support?

    Customer support for ThousandEyes is great.

    Which solution did I use previously and why did I switch?

    Before ThousandEyes, I did not previously use a different solution.

    How was the initial setup?

    We are still not integrated when correlating ThousandEyes network path telemetry with existing APM or Cisco ecosystem tools during multi-domain incident response.

    What's my experience with pricing, setup cost, and licensing?

    My experience with pricing, setup cost, and licensing is still in early stages.

    Which other solutions did I evaluate?

    Before choosing ThousandEyes, I evaluated other options, and the next option came up.

    What other advice do I have?

    On a scale of one to ten, I would rate ThousandEyes a nine. I give it a nine because it stands out as a good product. My advice to others looking into using ThousandEyes is that it is a good product.

    Glenn Alves

    Network observability has strengthened service quality and has supported major client contracts

    Reviewed on Nov 09, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for ThousandEyes is observability from a standpoint of the company's networking and connectivity solutions.

    As an example of how I use ThousandEyes for observability in our networking and connectivity solutions, our company currently serves many solution partners, in particular, a major pharmaceutical client. Our telecom operations teams have to report out on the number of calls and the information shared from various pharmaceutical solutions that this client offers, and our team is the basic conduit between questions and customer feedback. Those have to be observed relative to where they come from, where they go to, and secure in the process.

    How has it helped my organization?

    ThousandEyes has positively impacted my organization by ensuring that our service to those customers has to be impeccable, fast, and expedient. We drive our customer base from the standpoint of providing excellent service, where the survey performance is given to them. On a scale of one to ten, we're in the 90 plus percent area, which allows us to retain our long-term service contracts and use these customer successes as a case to win additional customer successes.

    As for specific outcomes or metrics, one of our largest clients has a contract with us that supports a whole team of over 70 plus people. To the extent that that contract is maintained means hundreds of thousands of dollars in revenue for the company, which when that contract ends would create quite a gap in our expected revenue success stream for the company.

    What is most valuable?

    The best features ThousandEyes offers include dashboard visibility, which I'd say is a great feature relative to our team's use. Being able to see everything in one spot, almost like an MRI in the healthcare example, is very useful from the team's assessment and speed upon which solving any issues can be addressed.

    The dashboard visibility helps my team specifically by providing a full viewability standpoint, which has allowed us to reduce the number of management staff. I have been able to pinpoint issues without going through several other dashboard screens previously, which speeds things up far more quickly in terms of our ability to address an issue.

    Additionally, it's providing an effective tool to ensure both security as well as cost savings from a protection standpoint.

    What needs improvement?

    ThousandEyes could be improved by offering more effective long-term contract pricing and potentially spending more time understanding what our sales and service teams have as challenges from our customers to see whether ThousandEyes could provide solutions in its broader portfolio of services, enabling us to be more effective with our customer base.

    For how long have I used the solution?

    I have been using ThousandEyes for roughly about two years.

    What was our ROI?

    I have seen a return on investment with ThousandEyes, and I can share that we could reduce the headcount if needed.

    What's my experience with pricing, setup cost, and licensing?

    I approved the overall contract regarding pricing.

    What other advice do I have?

    On a scale of one to ten, I would rate ThousandEyes a solid eight.

    I give it an eight because, while I have had great service and solutions from ThousandEyes, they could probably do more to help me be more fully utilizing the software overall.

    My advice to others looking into using ThousandEyes is to have the team do an assessment and a good means of determining a return on investment, with examples that can be readily deployed and things of that nature.

    reviewer2923881

    Network insights have improved call quality and now pinpoint faults across complex paths

    Reviewed on Nov 09, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for ThousandEyes is to look at the quality of our traffic and identify any network faults and problems along the way, particularly for Teams phone calls in call centers in the Philippines and how they traverse the network to and from.

    Based on where the fault is, that will determine which team is responsible for that part of the network, and that team will then be asked to investigate.

    I deployed ThousandEyes alongside traditional SNMP and flow-based monitoring tools due to specific blind spots across underlay transit networks or cloud hops, as we were having some issues with some Microsoft tools and complex networks from international areas. I often receive feedback that the Enterprise Data Network is at fault when, in fact, other teams or areas are responsible, so ThousandEyes helps me redirect the calls to the actual problem areas rather than always blaming the network.

    How has it helped my organization?

    ThousandEyes has positively impacted my organization as I have been able to utilize it for the tracking of defects, allowing me to identify the defects more quickly.

    I have not seen any measurable improvements so far because it has not been fully deployed yet.

    What is most valuable?

    ThousandEyes offers the best features in that it runs easily, and I do not have to run separate tests to operate it. It has an agent that monitors the traffic and then is able to provide the information depending on which path the packet takes.

    The automatic path information has helped my team troubleshoot issues and validate network performance in practice because it is beneficial to know that I am not always going to get the fault when I want it, so going back and trying to troubleshoot the network after the fault occurred is the best way. It is also beneficial that I do not have to install it at different data centers and points; I can utilize Cisco's network.

    Regarding ThousandEyes's AI capabilities, I think its governance and security are good. I think it is appropriate as it is using the Cisco agent, which is suitable in today's world, and I have no concerns about it.

    Regarding ThousandEyes's AI capabilities, I find its accuracy and reliability of output to be very accurate. For everything I have used it for, it seems spot on. Sometimes I might need to correct it due to some minor issues, but when it comes down to the data analysis, I think it is spot on.

    Path visualization and hop-by-hop metrics influence how my team escalates service degradation with external transit providers and cloud hosts by helping us understand the hops, which reveals which area of the network the problem lies in, allowing us to direct the query specifically to that team. We have the facts to have a proper discussion about the problems and where the problem area is located.

    What needs improvement?

    ThousandEyes can be improved by having more agents deployed and more points which would enable us to make measurable improvements. For those data points that we have, it is beneficial, but we obviously need more of those.

    For how long have I used the solution?

    I have been using ThousandEyes for the last month.

    What do I think about the stability of the solution?

    ThousandEyes is stable, and I have not heard of it not being stable.

    What do I think about the scalability of the solution?

    I think ThousandEyes's scalability is very capable.

    How are customer service and support?

    The customer support is good. I have dedicated Cisco account managers and success managers, so it is all good.

    I would rate the customer support as a nine at the moment.

    How was the initial setup?

    ThousandEyes is deployed in my organization on the agents and on some of the network devices, including network points like switches, and that is as far as I know at the moment.

    What was our ROI?

    I have seen a return on investment on a few incidents, but I have no metrics at this point in time.

    What's my experience with pricing, setup cost, and licensing?

    Regarding my experience with ThousandEyes's pricing, setup cost, and licensing, I have just assumed the roles and I am not entirely sure. However, I have heard from some of the team that it has been a bit difficult to understand the licensing. I have an ELA where everything is included in the enterprise agreement, so I am not entirely sure if I get to see the pricing. On a separate basis, I have heard it was a bit confusing.

    What other advice do I have?

    On a scale of 1 to 10, I would rate ThousandEyes overall as an eight out of 10.

    I rate it an eight out of 10 because I think it is a great product, it works very well, and it has potential to become a really detailed flow, though the licensing is a bit confusing with all the regions and all the licenses I have to get, and it is a bit costly.

    My advice to others looking into using ThousandEyes is that it is a great product and they should deploy it as soon as possible.

    reviewer2923911

    End-user monitoring has improved transaction visibility but still needs more maturity

    Reviewed on Nov 09, 2026
    Review from a verified AWS customer

    What is our primary use case?

    My main use case for ThousandEyes is end-user monitoring. I use ThousandEyes for end-user monitoring by integrating it with AppDynamics to monitor bank transactions and understand the overall picture of where the transaction is getting blocked.

    I correlate ThousandEyes network path telemetry with existing APM or Cisco tools by integrating it with AppDynamics and Splunk.

    What is most valuable?

    The best features ThousandEyes offers include synthetic monitoring, which performs from the synthetic health check.

    ThousandEyes positively impacts my organization by helping with early detection and reducing downtime. I cannot disclose how much it has reduced time to detect or resolve issues.

    After introducing ThousandEyes data, the operational changes that occurred in our cross-functional triage workflows include early detection.

    What needs improvement?

    ThousandEyes is at its maturity stage and performs well. The reason I rate it at a seven rather than a higher score is that it still needs additional maturity.

    For how long have I used the solution?

    I have been using ThousandEyes for three to four years.

    What do I think about the stability of the solution?

    ThousandEyes is stable.

    What do I think about the scalability of the solution?

    ThousandEyes is scalable.

    What other advice do I have?

    On a scale of 1 to 10, I rate ThousandEyes a seven.

    Regarding ThousandEyes' AI capabilities, I think the accuracy and reliability of its output is adequate.

    ThousandEyes is deployed in a hybrid environment in my organization and is deployed in the public cloud.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Pharmaceuticals

    End-to-End Network Visibility That Speeds Up Troubleshooting

    Reviewed on Nov 05, 2026
    Review provided by G2
    What do you like best about the product?
    Cisco ThousandEyes stands out for the end-to-end visibility it provides across the network, the Internet, cloud environments, and SaaS services. It helps me quickly determine whether an issue is coming from the internal network, the ISP, the Internet path, or the cloud service itself, which greatly speeds up troubleshooting and root-cause analysis.
    What do you dislike about the product?
    One drawback of ThousandEyes is that the platform can be complex to configure and manage, especially for users who are new to network monitoring. The sheer amount of data it provides can also feel overwhelming at first, and it takes time to learn how to interpret the results and use them effectively.
    What problems is the product solving and how is that benefiting you?
    ThousandEyes helps us identify and isolate network and application performance issues across our corporate network, the Internet, and cloud services. It gives us clearer visibility into where a problem is happening, which makes it easier to determine whether the root cause is in the local network, the ISP, the Internet path, or the SaaS provider. As a result, we spend less time troubleshooting, resolve incidents faster, and minimize disruption for users.
    Samarth Banaji

    Continuous global monitoring has reduced downtime and detects login issues before clients report them

    Reviewed on Oct 08, 2026
    Review provided by PeerSpot

    What is our primary use case?

    My main use case for ThousandEyes is that it checks our product website, and if it flags that it is unable to log in, it checks for all the components from all the agents, which are from different locations. It keeps on scanning every five minutes or every minute, and it flags issues immediately through email alerts.

    When we receive email alerts, we thoroughly troubleshoot what is causing the issue, whether it's a false alert or a true alert. If it's a false alert, we receive a recovery email, and if it's a true alert, we don't get recovery alerts. Then we engage the next level of support and keep checking the troubleshooting issue.

    There are many situations where ThousandEyes has helped us catch an issue, such as a product login where there was a certification issue. In one of my use cases, the certificates were updated as part of one of the recent changes.

    With the help of our monitoring team, we have defined a lot of use cases in ThousandEyes, and we have predefined sets that are very useful for us. That acts as a radar for us.

    How has it helped my organization?

    ThousandEyes positively impacts our organization by flagging issues immediately, which helps us reduce downtime whenever we seize or acknowledge the alerts. That is the benefit of ThousandEyes.

    ThousandEyes has helped in a lot of situations, especially before the start of client login hours, by flagging issues immediately so we can resolve them and ensure the product is available all the time.

    What is most valuable?

    In my opinion, the best features ThousandEyes offers include its ability to act as a radar, logging in from different regions across the globe and confirming whether our product is working as expected. This is very useful for us.

    The global monitoring from ThousandEyes alerts us immediately about issues, and troubleshooting is handled by us, allowing us to resolve the issue before the client reports it.

    The alerting and reporting features are all done at the real-time level.

    What needs improvement?

    I believe ThousandEyes is working perfectly, but I feel that with more AI integration, it could flag issues with more detailed error information, which would help support engineers immediately pinpoint what exactly is causing the issue.

    Regarding needed improvements, I think the user interface could be better. It is sometimes a little confusing and should be very user-friendly, including a guide for how alerts are configured to assist first-time users.

    For how long have I used the solution?

    I have been using ThousandEyes for more than five years.

    What do I think about the stability of the solution?

    ThousandEyes is stable.

    What do I think about the scalability of the solution?

    I believe it is scalable.

    How are customer service and support?

    I deal with customer support through our dedicated team working with ThousandEyes team, and I believe they are doing great.

    What other advice do I have?

    Regarding ThousandEyes's AI capabilities, I believe they are very capable, and from a security perspective, we haven't found any issues.

    I haven't explored ThousandEyes's accuracy and reliability feature much, so if there is a feature that has not yet been introduced to us, I need to explore more on that.

    My advice to others looking into using ThousandEyes is to go for it, as they are the best in the market.

    I would rate ThousandEyes a nine because there are features I would like to see improved. Not every product can be perfect, and I believe it should evolve to have a more user-friendly UI.

    Roopadharshini Vk

    Network visibility has transformed incident reduction and now delivers faster root cause analysis

    Reviewed on Oct 01, 2026
    Review provided by PeerSpot

    What is our primary use case?

    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.

    How has it helped my organization?

    ThousandEyes is utilized as a monitoring tool and integrated with application monitoring to provide network-level visibility, which alerts us before an outage happens so we can investigate and fix the problem before it becomes a big outage.

    Earlier, we were blindfolded to all of these application issues at the network level and used to have numerous incidents. For example, in the two years before we onboarded ThousandEyes four years ago, all the issues were being blindfolded, and our engineers used to end up troubleshooting for long hours. With ThousandEyes, we have reduced the time of investigation for any application issue at the network level, which helps us to focus on the genuine issues rather than simply sitting and troubleshooting network issues that are not actually network issues. We have reduced almost 76% of the incident count for issues that are not network issues but were application-based issues.

    What is most valuable?

    The best features offered by ThousandEyes that we are using in our GSK platform are Path Visualization, Network Performance Monitoring, and Internet Insights. No other platform provides Internet Insights. This is where we always lag with other monitoring platforms, but ThousandEyes provides Internet Insights, Enterprise Agents, and BGP visibility. These are the areas where we are majorly focusing and using ThousandEyes. There is also SaaS application monitoring so that we can correlate the application experience with the network behavior. Most of the time, we don't know whether the issue is happening at the application end or at the network level. ThousandEyes helps us to provide the correlation. When we have the correlation between the application and the WAN part through the SaaS platform, this helps us to understand exactly where the problem is occurring, whether at the network level or at the application level. ThousandEyes analyzes Cisco SD-WAN telemetry and provides path recommendations. As mentioned previously with the use case, ThousandEyes helps us by recommending the path and which path is clear without any issues and which path can be used when we encounter any issue in the routing path or the current path.

    Internet Insights uses collective intelligence to identify internet, network, and application outages and provides visibility into the impact involving providers and SaaS applications. When I say Internet Insights, today, once we exit the egress path, we will not have visibility. Outside our network, we will not have any visibility to troubleshoot. Internet Insights through ThousandEyes gives us, with the border patterns, geographical providers, domain servers, and network interfaces, a way to understand exactly what is happening on the internet. Today, we don't have visibility at the internet level, so that is where ThousandEyes helps us to track that as well.

    ThousandEyes detects the degradation, identifies the affected path, SREs localize the domains, and correct the path. The team provides the engagement. These are some of the things we are utilizing ThousandEyes for.

    What needs improvement?

    For ThousandEyes, I am looking for AI integration, which would help us to auto-correct the problem and fix it before it creates any issues. Currently, whenever there is an issue, based on the threshold configuration, we receive an alert and then we utilize the platform for investigation purposes. Instead of that, if the platform itself is able to identify the problem and give a suggestion instantly for rectification or correction of the problem, through the necessary approval of the platform owner or the SMEs, with their approval, it could correct the problem by itself. This is the expectation from AI in ThousandEyes.

    For how long have I used the solution?

    It has been four years since we started using ThousandEyes, which is one of the excellent platforms for monitoring, where we can monitor complete hop-by-hop and improved Microsoft Teams health and network metrics, enhanced end-to-end troubleshooting, and stronger WAN observability and visibility.

    How was the initial setup?

    I have not experienced any issues with the hybrid cloud deployment. It was a very flawless deployment we experienced because Cisco expertise came and helped us complete the deployment.

    What other advice do I have?

    ThousandEyes has reduced our troubleshooting time for our organization. This platform is very useful from the telemetric information for the WAN perspective and observability information. The primary opportunities for improvement are AI integration, as governance and security should be the primary focus when integrating AI capabilities, which we are missing today in the AI world. Everybody is talking about the data, but nobody is worried about data security.

    Through SLA and SLO metrics, I assess the operational efficiency of Cisco in my IT environment.

    This is a very good platform for monitoring purposes. If you are looking for a platform to have more telemetric information from the WAN perspective and from the application level, I always recommend ThousandEyes. I would rate this product an 8 out of 10.

    AsifKhan 1

    Monitoring has improved end-to-end visibility and has enabled proactive troubleshooting

    Reviewed on Sep 25, 2026
    Review provided by PeerSpot

    What is our primary use case?

    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.

    What is most valuable?

    The best thing that I feel is that it holds the data. The purpose that we are using includes monitoring the underlay and monitoring the internet path. When we have an issue, by the time we get the notification and join the audio call, we realize that the issue is gone and we are clueless about what exactly happened. With ThousandEyes, we can go back in the history and see what exactly happened during that time. We can see the data for up to 90 days. In the normal dashboard, we can see data for 14 to 30 days, but if we do some additional things, we can see the data for 90 days.

    Another best part is that it gives us where the loss is coming from. If we do a normal ICMP test, we can see from which node the drop is coming from or which node is spiking the latencies. If we do an HTTP server test, we can see the entire waterfall flow. We can see which object is taking how much time, which object is taking how long to load, and all those DOM and content delivery things. Everything we can see. It's actually amazing.

    What needs improvement?

    The first thing is that we don't have any option to export the reports. If we want to export any reports, we don't have any such options. Sometimes when we deal with leadership, they don't want to see the screen. They want to see the data on an Excel file or maybe in a graph. Even if we want the raw data, we need to do some API things or play with other workarounds, and then only we can get the raw data. We don't have the export options.

    The other thing with the Endpoint Agent is a limitation. In our current scenario, we are not using Endpoint highly. We have a few licenses that we are still checking whether we need. If we have an available license for an Endpoint Agent and we ask our site IT team to install the agent on the machine, as soon as the agent is installed, it will show up on my ThousandEyes dashboard and it will consume the units. What I want is for it to be in a disabled mode, not an enabled mode, and not consume the units or the license until I assign it manually. This will help us a lot with license management.

    The dashboard can be more flexible. The way we are monitoring, the dashboard length is getting very long. We need more options to bring all those things into one single dashboard on one single page. We don't need to scroll down and see what is going on.

    There are a few more things concerning filters on the Endpoint Agent. When we see the results, the bare minimum option is 5%. If we are talking about packet loss, we can see only if there is a packet loss of either 5% or above 5%. There is no option for less than 5%. In my current organization, we are very strict with packet loss. Even if there is a 1% or 2% packet loss, we want to see from which node it is coming from. However, in ThousandEyes, we don't have any option to go below the 5%.

    When we create tests to monitor applications on the Endpoint Agent part, we have very limited options with the protocols. Only the ICMP and the TCP packets can be monitored. If we want to do some other kind of port, it's not there. It's not flexible.

    What do I think about the stability of the solution?

    Regarding stability, I feel there is none. I have never experienced any kind of downtime with this tool.

    What do I think about the scalability of the solution?

    On the scale of how scalable ThousandEyes is, I find scalability easy. It's stable, and we can install it wherever we want. We have many options regarding exactly where we need to install. In our current scenario, we are using it on four different platforms. Two are on the Cisco SD-WAN on different router models that we are using. We are using it on our servers at our sites. And we are using it on Linux, which is on the GCP. It's very scalable, and we can install it wherever we want.

    How are customer service and support?

    If I have to contact technical support, I think the speed and the quality of the support is very good. A while ago, I raised a concern with the TAC team, and I see there is a response from them within 15 minutes. I didn't see the response immediately, but I did receive an email that the case has been updated and is ready for my view. It's fast and on point. If I were to put the support on a scale from 1 to 10, with 10 being the highest, I would give a nine.

    Which solution did I use previously and why did I switch?

    I haven't used any alternatives to ThousandEyes, so this is something different. This is not a traditional monitoring tool. In traditional monitoring tools, we work with SNMP and just do the ping-pong and nothing else. This one is different. It's not traditional. I haven't come across any other similar tools that have this number of flexibility and this number of options.

    How was the initial setup?

    The initial deployment of ThousandEyes is very easy for me. There is no rocket science that we need to understand. The GUI of this tool is very friendly. The installation and implementation processes are very friendly as well.

    What other advice do I have?

    ThousandEyes does require maintenance on my end, such as upgrading. Currently, the version that is being used is going to be EOL by November. We need to upgrade and do some manual work on any agents that we have on SD-WAN and on our Catalyst switches because it is EOL. Otherwise, it upgrades itself without any intervention. Pricing is not in my view because it is being managed by the leadership team, so I am not sure what exactly and how exactly they are purchasing from Cisco. All I am doing is handling the tool. My overall review rating for ThousandEyes is 10 out of 10.

    Siddumanisria Mindi

    Monitoring has transformed internet visibility and speeds up resolving external service issues

    Reviewed on Sep 22, 2026
    Review from a verified AWS customer

    What is our primary use case?

    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.

    How has it helped my organization?

    ThousandEyes isn't just an internal monitoring tool; it's an internet visibility engine. It turns external unowned networks into public ISPs and SaaS environments into transparent, measurable infrastructures.

    ThousandEyes benefits my organization through metrics that show reduction in mean time to resolution, with a 40% to 60% reduction in MTTR. Instead of hours spent manually collecting traceroutes or holding war room calls across teams, engineers identify point-to-point root causes in minutes, detecting an ISP peering hop drop versus an application server issue. This also reduces mean time to detect or identify incidents. AI summaries and path visualization immediately highlight whether packet loss or latency is occurring on-site across SD-WAN or within external SaaS providers' infrastructures. Ticket escalation and help load metrics show a 30% plus drop in escalated Tier 3 network tickets and first contact resolution improvements. Tier 1 and Tier 2 helpdesk teams can directly diagnose last-mile Wi-Fi or local ISP issues via endpoint agents, avoiding unnecessary escalations to senior network architects.

    What is most valuable?

    The best features that define ThousandEyes' value include end-to-end path visualization and Internet Insights as macro outage detection. It matters because it automatically detects macro outages across major ISPs. ShareLinks generate live or read-only URL snapshots of active or historical test results. ShareLinks are used primarily for my field as a network engineer, used for BGP or route visualization and multi-layer agent deployment fleet. WAN or Cloud Insights is another valuable feature. AI operations and assistant integrations complete the set of features we consider most valuable.

    As the network engineer and operations team, the primary benefit of ShareLinks is transforming vendor escalations and cross-team collaboration from a time-consuming back and forth into an efficient, data-driven process, which eliminates vendor blame games and scripted triage. A ShareLink provides a live, interactive 3D map of the network path and the exact moment that incident occurred, where third-party engineers can drag or zoom and inspect specific router interfaces or latency spikes and packet loss metrics directly. This cuts the mean time to resolution. As a network engineer, I bypass Tier 1 and Tier 2 helpdesk triage by attaching a ShareLink to vendor tickets, demonstrating proof of where the traffic is dropping within the vendor backbone or peering point.

    Cisco has embedded AI capabilities and integrations into ThousandEyes to automate root cause analysis and reduce manual diagnostic efforts. The AI algorithms automatically synthesize complex data across Layer 3 to Layer 7 and generate a human-readable executive summary. For example, latency increases by 180 ms due to packet loss at an upstream Cogent peering interface in Frankfurt. This enables Tier 1 NOC staff to triage issues without immediately escalating to Tier 3 network architects.

    Highlighting these advanced or high-value capabilities of ThousandEyes will set our review apart. Advanced capabilities include adaptive alert detection, noise reduction, multi-step API synthetic testing, open telemetry integrations, open observability, edge-embedded deployments, and Cisco Assurance in genetic ops.

    What needs improvement?

    ThousandEyes needs to specify unit consumption forecasting or scaling testing and deeper app analytics. It needs deeper out-of-the-box Layer 7 code or database-level insights. Additionally, it should unify the GUI with broader Cisco platforms and flatten the learning curve, adding better correlation with local laptop system metrics such as endpoint depth, CPU, RAM, or processes.

    ThousandEyes isn't designed to be a full-blown SNMP monitoring tool for on-premises infrastructure. While it tracks network paths effectively, it doesn't provide deep local device telemetry such as switch port buffer utilization, fan status, or power supply health. For full internal device monitoring, you'll still need to pair it with traditional tools such as SolarWinds or Cisco Catalyst Center.

    For how long have I used the solution?

    I have used ThousandEyes for four years.

    What do I think about the stability of the solution?

    Stability issues are present in the solution.

    What do I think about the scalability of the solution?

    Backend architecture is seamless at 10 by 10, and global reach is instant at 10 by 10. For remote endpoints, it is 9 by 10, and cost and licensing is 7 by 10.

    How are customer service and support?

    Customer support is highly responsive, deeply technical, and proactive.

    How was the initial setup?

    Deploying agents across a hybrid multi-cloud environment is fast and straightforward. However, the unit consumption pricing model can be complex to forecast and requires careful ongoing management. This makes procurement most efficient when blended into a Cisco Enterprise Agreement or leveraged through an AWS Marketplace cloud commit.

    What was our ROI?

    The return on investment is immediate, delivering a 40% to 60% reduction in MTTR by eliminating multi-team war rooms and saving hundreds of engineering hours annually through instant ISP path proof, directly protecting business productivity and SaaS SLA accountability.

    What other advice do I have?

    If I were giving advice to another NetOps team evaluating ThousandEyes, my main recommendation would be to focus on governance and operational workflows from day one. I would rate this review as a 9.

    Which deployment model are you using for this solution?

    Hybrid Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    SanjeevKumar28

    Visual mapping has improved network monitoring while integration and support still need work

    Reviewed on Sep 21, 2026
    Review provided by PeerSpot

    What is our primary use case?

    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.

    What is most valuable?

    My favorite feature is that we were able to see everything on a map. It shows how the connection is going from one device to another device and we can see where the issue is happening. It is easy to find the point where an error is occurring or something is down. We can easily map it out, which is why we were using it.

    What needs improvement?

    There were many compatibility issues and integration issues which we were facing. We could not easily connect it with different types of devices and we were facing the integration aspect. There is very limited API support. When we were integrating with Splunk, we could only pull a little data, not all of the data.

    I would like to see better support from ThousandEyes, along with improved documentation. They can provide FAQs and troubleshooting guides so we can resolve issues before reaching out to them. There should be a list of things we can do independently. Documentation should be provided for all supported products, including how we can integrate Splunk, Cisco, and other portals. API documentation can be increased. From the time I used it, it was not updated. It was kind of a beta experience, I would say. It was not fully developed at that time. It looked like an unfinished project with many gaps.

    For how long have I used the solution?

    I did not use it this year. Last year, I used it for almost eight to nine months in my previous organization.

    What do I think about the stability of the solution?

    I did not see any downtime. However, it used to be a little laggy, but I do not know if that was from their end or our end. I think it was good. I would rate it an eight.

    What do I think about the scalability of the solution?

    I think it is good. I would rate it an eight to nine. It was scalable. We could easily add hundreds of devices with no issue.

    How are customer service and support?

    ThousandEyes technical support is slow until you mark the issue as a P1 or P2. They have categories for issues, and if you don't mark it as higher priority, they will not reply as soon as possible. They will take two or three days to respond.

    We need to clarify the severity of the ticket. If it is a P1, then they will respond faster. Otherwise, they will send us the documentation link and tell us to review the documentation. After four or five days of continued messaging, they will set up a call and send an analyst or support engineer, but they will also not be able to help us the first time. Then they will call our senior in another call and maybe then the issue will be resolved. It is slow. I would rate their support a six out of ten.

    How was the initial setup?

    The initial deployment was not that hard. It was a cloud-based solution, so only the agent installation was required. It was easy. However, if some product is not supported or if there is no documentation, we need to find a lot of workarounds. When we were trying to integrate some Cisco switches with SNMP, there were a lot of problems and we were not able to figure it out. We reached out to Cisco technical support and they helped us, but it took a lot of time, like two weeks to integrate one switch for our testing. I would say it was not a good experience for our whole team.

    Which other solutions did I evaluate?

    I have not used alternatives, but I have used Splunk to monitor our devices via SNMP and Syslog. I have also used one more product, an open-source tool called Zabbix.

    Zabbix has more templates and better documentation. They keep updating it, and I see a lot of updates coming for Zabbix on a daily basis. It is open-source, not a Cisco product or some big company product. I would say it provides a lot of features. Zabbix does have some issues, but I don't think we can compare them directly. It is also a good tool.

    What other advice do I have?

    I don't think there was scheduled maintenance. However, sometimes the connection used to go out, but that was kind of an internal network issue, not a ThousandEyes-related issue.

    Regarding ThousandEyes pricing, I don't know about the specific costs because my management was dealing with that. They did not tell me the pricing details. However, I think they did not buy the license later. They used it for one year and then canceled it.

    My overall rating for this product is seven out of ten.