ThousandEyes Reviews

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.

The best features ThousandEyes offers are network path visualization, deep end-to-end full-stack visibility, and intuitive dashboards. All of these features allow us to formulate a comprehensive view of network performance and how our applications are meeting and exceeding performance thresholds based on SaaS performance, network path visibility, and other attributes.

The intuitive dashboards really allow us to aggregate metrics, so when I think of network visibility, it's really around MELT data: metrics, events, logs, and traces. As part of our full-stack observability protocols and apparatus, we're able to track all of those types of event data and data points onto our dashboards. The dashboards are fully customizable, so we're able to actually, during our path visualization process, navigate the dashboards accordingly for our enterprise-wide deployments and access the dashboards according to roles.

ThousandEyes has provided my organization with invaluable network visibility and insights and incredible ease of use. There is a very narrow learning curve for new users in how to leverage the extensive features that ThousandEyes provides. ThousandEyes has become critical for swift network troubleshooting as well, so anytime that there's potential issues with applications or we want to be proactive in resolving potential issues before they arise, ThousandEyes is really the platform that we're leveraging for WAN monitoring, Wi-Fi, latency, packet loss, etc. ThousandEyes has become a very powerful tool in our toolkit.

ThousandEyes has saved my team on a week-to-week basis about 7 to 9% of our time spent on troubleshooting network and application visibility, availability, and performance. We are able to now allocate that time saved to other mission-critical activities and projects across the organization. ThousandEyes has become a really invaluable tool for not just identifying network issues, but also taking proactive steps in resolving those network issues. It's really been a huge relief in terms of not just time savings, but then also frustration and ease of troubleshooting tool to free up our DevSecOps engineers to more mission-critical activities.

With ThousandEyes, there are some configuration and metric screens that are not entirely intuitive with ThousandEyes, so they can certainly improve in terms of the usability of certain metric screens. ThousandEyes can also offer deeper traffic insights relative to specific applications, so detailed analytics on application-level traffic would help in better understanding and managing our network resources effectively.

I would say that ThousandEyes can also, in terms of providing more extensibility with other observability tools, offer more out-of-the-box integrations with other observability tools so that ThousandEyes can serve as that single source of truth, so that we don't necessarily need to go to other tools to be able to be that one-source dashboard. I think there's a lot that ThousandEyes can continue to improve on there.

The issues that I've talked about, including extensibility with other platforms and the improvement of accessing specific metric screens in order to be able to provide for fuller access and more detailed access to network-level metrics would make the platform feel less complicated to navigate. It wouldn't require as many manual integration inputs.

I have been using ThousandEyes now at three companies, and here at Fruidist, I have been using ThousandEyes for a little over 14 months. At my previous two companies, I had been using ThousandEyes for cumulatively about two and a half years as well.

I would rate ThousandEyes a 9. I think that it has tremendous capabilities around granular data views and dashboard access. I just think that the issues that I've talked about, including some of the metric screens and extensibility across other platforms, can still be improved.

I would say that certainly do your research in terms of the extensibility of ThousandEyes across other observability providers as well. ThousandEyes is an incredibly powerful solution when it comes to network visibility and performance. To get a full scope of coverage across your technology layers, including the application layer and infrastructure layer, you will need to combine other best-in-class observability solutions for a fuller picture. I would certainly do your research in terms of which other providers work and integrate well with ThousandEyes for that full-stack view.

ThousandEyes is deployed via public cloud at our organization.

We are using Amazon Web Services as our public cloud provider.

I did purchase ThousandEyes through the AWS Marketplace.

ThousandEyes pricing can also get more streamlined. Right now, ThousandEyes prices based on cloud and enterprise units, endpoint agents, insights, and implementation services, and I feel that the pricing model can certainly be streamlined.

ThousandEyes has been an incredible partner for network path visualization and full-stack visibility. I have now used ThousandEyes at this my third company utilizing ThousandEyes for network visibility, and the ease of use and learning curve are just incredible. I look forward to utilizing ThousandEyes going forward as well.

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.

In comparison to others, ThousandEyes is having several features, but the most features that I am using are the Enterprise agents where we used it the most, and Path Visualization is another feature that we used for troubleshooting as well. Apart from this, the endpoint agent needs to be configured, and I try to find out how these endpoint agents work on the system of customer devices.

When we are troubleshooting, in our earlier scenario, we had to take a lot of time to try to find out where the issue is and what the issues are because in regular troubleshooting, when doing the ping and trace route, we had to find out where the issue is and how we could fix it. In ThousandEyes, ideally, we got all these things in one shot. In Path Visualization, we have the hop-to-hop information so that if something is stuck somewhere, the red button is shown there, so we can find out that the issue is there. This also gives us the identification of that particular item, and if I talk about the IP address, we have that, and then we can try to find out or we have to contact with the ISP or something similar. If there is an issue with the ISP, then we have to catch up with the ISP if there is any issue at that particular time, and then we can interact with them.

All the features are good, and ideally, we are using these two features currently with our customers. Another feature that I know about is Internet Insight, where we have the information regarding the outages, and where the issues are mentioned in that particular part.

ThousandEyes actually advanced the troubleshooting part and the monitoring of the devices, or I would say the management of the devices with monitoring and to identify the root cause. It was very helpful in that sense because I am working on multiple customers, so for every customer, we use ThousandEyes. If we do not use ThousandEyes, then it was very difficult for us to understand where the issue is, how to identify those issues, and how we can drive the RCA on those customers. Another thing that I think is very beneficial in the current scenario is the AI assistance of ThousandEyes, which helps us to identify the root cause analysis.

I think ThousandEyes could include some other devices or servers and that kind of monitoring capability which currently ThousandEyes is not using. Additionally, something related with the security would be beneficial. If they include the security part as well in terms of monitoring, then it would be good.

I have been using ThousandEyes since 2021.

ThousandEyes has been stable.

ThousandEyes is working fine and is excellent in terms of adding the devices or adding the agents and adding the test based on the licenses that we have. It is capable enough to be scalable.

Customer support from ThousandEyes was good. Whenever I raise the queries, I got the prompt answer on that as well as the solution that we needed. I received that kind of support from ThousandEyes.

Before ThousandEyes, we worked on some other solutions including Riverbed and Ipanema Infovista at that time, and those were more on hardware-based and they were not providing that kind of capability in terms of the application because we used Riverbed before 2021. Then we switched over from those products to ThousandEyes or LiveNX or that kind of products, because of the capabilities that ThousandEyes and other products provide in terms of cloud-based solutions and SASE part of these solutions. Additionally, they are providing much more visibility in terms of the network and end-to-end visibility.

Currently I am not actually dealing with licensing and something similar because that was done by the presales team, but whenever I raise the queries with the team, I got the response from them, and that is good.

I am not the right person to answer this question because I am a consultant. As a consultant, I usually am on the customer's run side, so the impact should be there. A positive impact should be there in terms of the customers in that they are very happy when they are using ThousandEyes right now, and earlier, they had multiple issues with the teams. That is the part where we can say that ThousandEyes is working effectively.

In terms of ROI, I am not aware of that because I have not calculated that right now, so it is quite difficult for me to say anything on that part. The time and employee part is very good and is up to the mark.

I am not the right person to answer this question because I am a consultant. As a consultant, I usually am on the customer's run side, so the impact should be there. A positive impact should be there in terms of the customers in that they are very happy when they are using ThousandEyes right now, and earlier, they had multiple issues with the teams. That is the part where we can say that ThousandEyes is working effectively.

In terms of ROI, I am not aware of that because I have not calculated that right now, so it is quite difficult for me to say anything on that part. The time and employee part is very good and is up to the mark.

Currently I am not actually dealing with licensing and something similar because that was done by the presales team, but whenever I raise the queries with the team, I got the response from them, and that is good.

We used ThousandEyes as well as we used LiveNX, LiveSP, and some other products as well, though I am not remembering the names.

The advice to other customers for using ThousandEyes is that if it suits your environment in terms of monitoring and visibility purpose, and you have enough budget for that, then go for it. I think it would be good in terms of the Enterprise agent, in terms of end-to-end visibility, in terms of Path Visualization, in terms of Internet Insight. All the features are very good, and it has the capability to reduce your operational expenses and increase the efficiency in terms of operations. It would be excellent. I would rate this product a 9 out of 10.

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.

ThousandEyes offers the best features including global internet and cloud visibility from distributed vantage points, application and network performance monitoring, real-time outage detection and incident alerts, end-to-end path visualization for rapid troubleshooting, proactive issue demarcation, and historical data. It is easy to use, easy to set up, has a good support team with quick responses, features high-level customization for dashboards and testing, and provides seamless integration with Cisco products.

ThousandEyes has positively impacted my organization by reducing mean time to troubleshoot and resolve issues faster, as well as resulting in fewer user mapping error issues.

ThousandEyes can be improved by making the installation procedure less time-consuming and enhancing the interface to be more user-friendly. Better agent integration on Cisco routers would also be beneficial.

An improvement needed for ThousandEyes that we have not discussed yet would be a unified licensing for the endpoint agent.

I have been using ThousandEyes for four years.

ThousandEyes is fast, reliable, and very stable.

ThousandEyes's scalability is excellent; it is very scalable and grows with my organization's needs.

The customer support for ThousandEyes is very proactive and supportive.

I previously used a different solution called LogicMonitor and Zabbix before switching.

I have seen a return on investment by reducing troubleshooting time and having lesser user mapping error issues, in addition to engineering time saved through better observability and reduced organizational MTTR.

My experience with pricing, setup cost, and licensing has been that everything was cost-effective.

Before choosing ThousandEyes, I evaluated other options such as Atlassian and Confluence.

I would rate ThousandEyes an eight out of ten since it has improved visibility into our infrastructure, which is not under our control.

The advice I would give to others looking into using ThousandEyes is that it is a great tool for application and network performance troubleshooting, especially for understanding upstream SaaS networking pathing and performance. Nevertheless, it is not very appropriate for heavy synthetic application testing where variable consumption of compute units makes the solution cost unpredictable.

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.

ThousandEyes has been the most user-friendly tool I have seen in the past couple of years, making life easier in troubleshooting and helping us find what's happening while offering vivid options on how to use the agents or the server-side tools with multiple options to trace out the issues.

The best features ThousandEyes offers include the ability to place two different points or nodes, such as a server or a node in the cloud in my account, then installing agents and tracing the connectivity which helps me build a perfect user experience to check what's happening while users access my resources.

I love the dashboards in ThousandEyes and the way I see the results after placing or doing the tests; this is perfect, and I would say this is the best thing.

ThousandEyes has positively impacted my organization by raising the customer experience and positive feedback by over 70% due to the complex situation with local service providers, allowing me to resolve user feedback and issues which enhanced the user experience significantly.

I measure the 70% improvement in customer experience through customer tickets and feedback after resolving issues, where previously, users faced problems and limited time on the platform, and after using ThousandEyes, the user time reached up to five to six hours a day, even for teams possibly totaling 30 hours a day.

ThousandEyes could focus more on end-users than enterprises, as the solution is powerful, and collaboration with multiple cloud providers should be developed for better test traceability, with the introduction of a free version for end-users and enhancements to the user interface for easier navigation.

Regarding the user interface, I appreciate dropdowns, but I prefer a guided experience where the interface explains itself instead of requiring extensive searching to reach a point.

I have been using ThousandEyes for the past four years.

From my experience, ThousandEyes has been stable up to 95%; I have not seen any stability issues.

Although I have not encountered a case where I needed to scale up with ThousandEyes, I know that it is highly scalable based on what I have learned.

I have not dealt with customer support, but I know ThousandEyes is well known for having good customer support.

Positive

Before ThousandEyes, I used DirectFN; they offered a good Falcon DF solution, but I switched because their solution was kind of legacy, hard to set up, and time-consuming for results, which led us to choose ThousandEyes.

My experience with pricing and licensing for ThousandEyes is fine; there has not been any setup cost because I am already experienced with the tool, eliminating the need for professional help for installation.

There has been a great ROI from using ThousandEyes, with significant time saved in troubleshooting as I can quickly pinpoint issues rather than spending time isolating them, alongside enhancing customer feedback and experience.

I evaluated multiple other options before choosing ThousandEyes, but I cannot mention specific names, and ultimately, ThousandEyes was the one I picked.

My advice to others looking to use ThousandEyes is to give it a try, do the demo, and invest in such solutions that will significantly ease the work for engineers and networking professionals.

I believe ThousandEyes has been helpful along my path, and I look forward to seeing more additions and enhancements to the platform and the solution. I would rate this product a 9 out of 10.

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.

ThousandEyes has really impacted my organization because my organization works a lot with SaaS products and also services other endpoints. It has really helped my organization to not have to hop from different endpoints to see exactly where latency loss or routing issues occur. It has also really helped our organization to understand the importance of performance observability and to understand the risk and single points of failure. The application of ThousandEyes on both internal and external services has helped us to better understand the idea of performance across regions and how internet conditions can vary globally.

There is a reduction in the time spent on root cause analysis. Sometimes, figuring out the root cause without concrete evidence of where the problem is can cause more errors and problems. With ThousandEyes, we are able to perform root cause analysis very effectively, and this also reduces the time spent on troubleshooting. Troubleshooting can be very complex, and if we don't have the right incident sensor, a lot of time can be wasted trying to troubleshoot a small problem. But with ThousandEyes' detection and the ability to provide the right agents, it makes troubleshooting very easy and reduces the time we waste. Faster troubleshooting is essential, and the detection of the root cause is great with the usage of ThousandEyes. I really recommend ThousandEyes for organizations that rely heavily on cloud services or external providers because it provides clear accountability when issues arise.

The best features that ThousandEyes offers are end-to-end network path visualization, and also cloud and internet performance monitoring across the public internet and cloud services. Also, agent deployments are a great feature. This includes deploying lightweight agents in different locations such as on-premises, cloud, and remote sites. This enables the measurement of real user paths and performance. Another great feature of ThousandEyes is its dashboard and historical baselines. The dashboards can enhance historical trends that help you compare against current performance and old performance. This is a great feature, especially when exporting reports that help to explain issues to executives, vendors, or customers during collaboration, reporting, and alerting processes.

I find all of them fascinating and great. You cannot really say one is better than the other because they all work in collaboration to help you detect problems. The end goal is always to present the historical baselines and reports to stakeholders. As a software developer, I find the end-to-end visibility fantastic because it reduces the stress of my work trying to figure out where there is packet loss or latency issues. Also, agent deployment helps in monitoring, detection, and internet performance, which is great. Then, the dashboard's ability to detect a historical trend provides great analysis. This reduces the need for separate data analysis or incorporating a third-party SaaS to explain historical trends. For me, all the features are great and make ThousandEyes stand out among other observability products. I find all of them fantastic. As a software developer, the end-to-end visibility comes first, but there is also the aspect of explaining to management what the issue has been. The operational features are really fantastic. It's a great collaboration where one cannot do without the other.

The feature that surprises me and is very prominent is the ability to deploy agents in cloud regions. I work very well with AWS, and this is a great feature integration with ThousandEyes. The ability to deploy agents in different cloud regions is a great key for monitoring, even on-premises or hybrid infrastructure. Also, custom alerts really help to reduce team noise and focus on real incidents. I find it fantastic. Another ability is the internet outage intelligence. This correlates with internet issues by monitoring the data. Right now, performance optimization is very important with the usage of SaaS products or when you host your infrastructure on a cloud. When there is an internet downtime, it causes heavy traffic. With ThousandEyes being able to detect and monitor this, it's fantastic for me. It reduces the workload and also reduces errors in trying to figure out where there is internet downtime, low visibility, or other incidents. I really find this aspect of ThousandEyes great. There could be improvement in the future, but for now, it works perfectly when you compare ThousandEyes with other observability products.

ThousandEyes can be improved based on path visualization. When you're trying to check exactly where traffic was impacted, the path visualization could be improved by pinpointing the actual performance problem and also detecting the right outages. For me, path visualization is a great area for improvement in ThousandEyes, as well as providing the right agents to detect where problems are occurring. Another area of improvement could be proactive incident detection. Incidents should be alerted on and traced early, before they escalate to full outages. With ThousandEyes, there should be the possibility of alerting on incidents. This helps in incident detection and being proactive so that time, which is essential, is not lost. An alert can be given so the problem can be solved very quickly. Alert detection and path visualization are two strong areas to improve on ThousandEyes.

The visual reports should be much easier to explain, for example, when explaining network issues to application teams and management. Also, when it comes to vendor accountability, the platform should be able to provide solid data to back up claims when working with service providers or on third-party issues. This is an aspect of integrating third-party providers on ThousandEyes, and especially when we talk about security, there should be solid data to back up claims. This would enable third-party vendors to know the essential work when they are integrated with ThousandEyes.

I chose eight out of ten because of the lack of objective performance data. With observability, performance data is very important, which isn't fully the case with ThousandEyes. Also, as I mentioned, path visualization needs improvement to provide better visibility into connectivity issues, especially with remote users across different regions. These are the two aspects I removed points for. ThousandEyes needs to improve its visibility, which can affect connectivity for remote users in different regions, and it needs to improve its path performance visibility. It also needs to improve its service level agreement in terms of performance data. It's all about the data, which is essential when explaining things to management or stakeholders.

The advice I would give others looking into ThousandEyes is that it's a great product. The ability to deploy agents in cloud regions is a key feature for monitoring hybrid, on-premises, and private cloud infrastructure. The custom alerts and dashboards help reduce noise and focus on real incidents, which is a great feature. Also, the ability for path visualization, addressing performance issues, and being proactive in troubleshooting complex network issues are great aspects of ThousandEyes. It can help organizations reduce the time they spend troubleshooting network issues or their ISP. Another aspect is the idea of proactive alerting, especially for latency loss thresholds. ThousandEyes is really good in that aspect, which can help define problems and improve current performance. I would rate this product an eight out of ten.

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.

The best features ThousandEyes offers include monitoring page load times, assessing how long it takes for an application to load, checking for packet loss and jitter, and monitoring the routing path from the user to the server hosted in the cloud or on-premises. Additionally, you could know if the page is currently loading or not; there are still many more features, but those are what we use at the moment.

ThousandEyes has positively impacted our organization by enabling us to know if a third-party hosted application isn't functioning properly, allowing us to determine what's actually going on and whether the issue lies on our side or with the application provider.

An area where ThousandEyes can be improved is in providing more in-depth packet analysis; we've found instances where ThousandEyes indicates everything is okay, but it's actually not. I would recommend incorporating something similar to Wireshark into ThousandEyes for deeper packet analysis as there are still aspects that ThousandEyes isn't able to determine. When something goes wrong, despite all the investments, certain results remain elusive, so they need to explore areas where Wireshark excels.

The knowledge base around ThousandEyes is quite limited; many engineers are unaware of its existence or the benefits it can provide, and this needs to be addressed. On a rating of 1 to 10, I would give ThousandEyes a maximum of five, indicating that there are many areas for improvement, especially in helping engineers understand how to resolve issues related to third-party hosted applications, as opposed to more recognized brands such as Cisco which have extensive resources for independent study.

Lastly, the servers sometimes require rebooting to monitor applications accurately, which may indicate a potential bug or issue.

I have been using ThousandEyes for almost two years.

ThousandEyes is not very stable; sometimes you have to reboot the servers to get actual results.

Scalability with ThousandEyes is straightforward as you don't really need to scale; it's designed to monitor multiple applications, accommodating 50 or 100 applications simultaneously, and if you need multiple testing points, you just deploy agents at different parts of your network or different sites that you're managing, which it does well.

I have not previously used a different solution, so I don't have any comparisons to provide.

Before choosing ThousandEyes, I did not evaluate other options as I do not make that decision.

There have been multiple instances when the insight from ThousandEyes has helped my team solve a problem faster or avoid downtime. Before we had ThousandEyes, we were not so sure where the problem was coming from, so for example, if a third-party application goes down or becomes very slow, we could never tell whether the problem was coming from the infrastructure side or from the application provider.

The application service provider would often tell us that everything is fine on their end, but after checking our infrastructure, we discovered that every other application was fine except this one, prompting a need for in-depth analysis into what exactly is happening and where the problem is coming from so that it can be properly fixed. We then begin to track what's going on with network path visualization, checking the page load time, jitter, packet loss, and every other component.

My advice for others looking into using ThousandEyes would be to try out a demo to see if that meets their needs and solves their problems.

On a scale of 1-10, this solution rates as a 5.

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

The historical timeline feature is what I appreciate most about ThousandEyes because when people report that something occurs at a specific time of day, I can set up a test and capture the issue in action.

One of the specific challenges I face with hybrid and distributed enterprise networks that Cisco addresses is SD-WAN visibility, as it can be difficult to see both the underlay and the overlay, creating some visibility gaps.

My impression of the end-to-end visibility offered by Cisco is that aside from those gaps, it captures nearly everything.

Cisco does optimize the experience in a hybrid distributed enterprise setup, and if there is a portion of the network that we cannot see, then that becomes a problem that affects our organization's troubleshooting capabilities.

ThousandEyes could be improved by unifying the GUI with the rest of the Cisco products since it remains legacy from its original state when Cisco acquired it.

I have been using ThousandEyes for approximately five years.

ThousandEyes scales adequately for our needs as my organization grows.

I would rate customer service and technical support as excellent based on my experience. I would give it a rating of 10 because whenever we have any issues, we can typically reach someone who has the knowledge to help us.

Prior to adopting ThousandEyes, I was using traceroutes and packet captures to address similar needs.

My experience with deploying ThousandEyes involved learning how to set up the tests. When I am setting up tests, I have a certain amount of credits allocated for each test, and it is difficult to see how many tests I can set up at one time before exhausting the credits, making it a trial-and-error process.

I have seen a return on investment with ThousandEyes.

My experience with pricing, setup costs, and licensing indicates that licensing is somewhat complicated because of the credits system.

I did not have any specific alternative solutions in mind when considering options before ThousandEyes.

I would rate ThousandEyes an eight on a scale of one to ten, with ten being the best.

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.

I think the best features that ThousandEyes offers are path monitoring, and obviously, the HTTP monitoring and the others are also good.

For the path monitoring feature, what stands out to me is the ability to see the unmanaged network. ThousandEyes has a lot of vantage points across the world, it helps us quickly identify whenever there is an issue with an ISP or MSP or even at the cloud site, and how that is visually described is what I find really useful.

ThousandEyes has positively impacted my organization because of the ability to identify issues proactively. Digital experience monitoring is an integral part of observability and monitoring nowadays. I need to know not only what's happening in my network, but also what's happening in the network that's not managed by me.

I have seen specific outcomes and improvements since using ThousandEyes such as reduced downtimes, faster troubleshooting, and identifying root causes faster.

I think ThousandEyes can be improved, specifically the licensing model.

It's too complex, too expensive, and it takes a lot of time to manage the licensing model.

My experience with pricing, setup cost, and licensing indicates that the licensing model is quite challenging. Every path, the frequency of gathering the data, consumes the units, so that's where I think a lot of improvement is needed or a lot of simplicity needs to be added.

I have been using ThousandEyes for probably four years.

ThousandEyes is stable.

ThousandEyes is very scalable.

The customer support is very good.

On a scale of one to ten, I would rate the customer support as an eight.

We haven't used other solutions before.

The setup is easy.

I did not purchase ThousandEyes through the AWS Marketplace.

I think the return on investment is mainly in time saved because the amount of effort needed to troubleshoot an issue when it is with an ISP is saved.

It's too complex, too expensive, and it takes a lot of time to manage the licensing model.

We haven't evaluated any other options before choosing ThousandEyes.

I would not add anything else about the features.

I haven't used the AI capabilities, so I'm not too sure about its accuracy and reliability of output.

We haven't faced any specific challenges with hybrid and distributed enterprise networks that Cisco addresses. ThousandEyes is a great product. The only thing is they need to improve the licensing model.

From ThousandEyes perspective, Cisco indeed optimizes the experience in a hybrid or distributed enterprise setup.

I am really impressed with the end-to-end visibility offered by Cisco through ThousandEyes.

End-to-end visibility from ThousandEyes affects my organization's troubleshooting capabilities because sometimes the problem is not in my network. Sometimes the problem is in the cloud or sometimes the problem is with the ISPs that provide the services, so ThousandEyes is able to quickly identify those and reduces our time to troubleshoot.

I would advise others looking into using ThousandEyes to look at the licensing model and also look at the dashboarding capabilities as well. When I used it last time, dashboarding was not really great, so these two cautions I would give them.

Overall it is a great product, but a few improvements are needed. I would rate this review an eight out of ten.

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.

The best features ThousandEyes offers include low noise, no false alerts, very early awareness, and reduced MTTR from issues that pop up, as well as an overall awareness and metrics, KPIs out of the environment for client and network performance.

The low noise and early awareness features allow us to become aware and generate alerts to the network operation center when an issue is brewing and also identify whether it is client-side, network-side, or backend.

ThousandEyes has positively impacted my organization by increasing employee satisfaction and reducing outages, saving dollars from idle employees that may have otherwise been having system or network issues, so we have that awareness to troubleshoot right away.

Downtime would be in the tens of hours saved just from being able to pinpoint where an issue is occurring, and a unique feature of ThousandEyes is the path visibility, which shows if an issue is within our corporate network or with a service provider.

One area where ThousandEyes can be improved is possibly having more stats on the endpoint; they may be there, and we may have just not dug deep enough yet to configure it where we can be alerted for endpoint issues itself, and ThousandEyes can do that but requires a little digging.

ThousandEyes definitely has differentiators versus the peers in the space, as there are other tools that are a bit more user-friendly to configure, especially around enterprise agents; for example, when upgrades are required, it sometimes needs a complete de-installation and re-installation of a newer version, which leads to a bit of administrative overhead from time to time, but overall, it has been an excellent product.

I have been using ThousandEyes for three years.

ThousandEyes is stable.

ThousandEyes's scalability seems infinite.

The customer support is excellent.

Positive

I did not previously use a different solution.

My experience with pricing, setup cost, and licensing is that it comes in cheaper than alternatives, and for setup, the package auto-updates, which is certainly a reduced administrative burden.

ThousandEyes is deployed in my organization in a hybrid cloud environment.

The cloud provider we mostly use is Amazon.

I did not purchase ThousandEyes through the AWS Marketplace.

I have seen a return on investment, and while I cannot quantify money, I can definitely say I have saved time.

My experience with pricing, setup cost, and licensing is that it comes in cheaper than alternatives, and for setup, the package auto-updates, which is certainly a reduced administrative burden.

I did not evaluate other options before choosing ThousandEyes.

I advise others looking into using ThousandEyes that the enterprise agent might be their most valuable module, as the endpoint agent certainly gives visibility into the client and can also be used for Webex RoomOS; their other modules are very useful as well, with internet insights being much more robust than DownDetector, which can provide early awareness when there is a global outage with a SaaS provider, for example, so cycles are not spent troubleshooting issues locally that do not reside locally.

ThousandEyes is an excellent product that really provides accurate metrics into network performance as well as the user experience, and I would highly recommend it. I give ThousandEyes a rating of nine out of ten.

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.

The features I like the most about ThousandEyes are the visualizations that let you see how the call flow went and how many hops it took and everything.

Cisco does optimize the experience in a hybrid and distributed enterprise setup. Our customer has almost four thousand sites, and they use Cisco phones. We also deploy the infrastructure behind it for us to understand how the phones are doing, if the phones are not, and we do proactive testing rather than reactive. That is why ThousandEyes helps us.

We face challenges with hybrid and distributed enterprise networks since we use Cisco, but we also have other third party integrations. When it comes to ThousandEyes, it does not show anything when it is out of Cisco. That is where we have a lack.

My impression of the end-to-end visibility offered by Cisco is that they could do slightly better things.

I think the pricing, setup cost, and licensing for ThousandEyes are too costly. This is a big one. From my perspective, I think the licensing model can be improved because not everybody is a large-scale company.

I have been in the industry for six years.

I would assess the stability and reliability of ThousandEyes as good, with no downtime or crashes or performance issues experienced.

ThousandEyes scales pretty well with the growing needs of our organization.

I would evaluate customer service and tech support for ThousandEyes as good.

Prior to adopting ThousandEyes, we tried to do a POC on Forward Networks.

My experience with deploying ThousandEyes was easy because the tag team was quick and easy to respond.

When we were deciding on ThousandEyes, we were considering other solutions. The competition type would have been Forward Networks.

I would rate this product a 9 out of 10.