Corvil Primary Use Case

Senior Network Engineer at a financial services firm with 501-1,000 employees
Latency analysis is our primary use case. View full review »
Kaarthik Elangovan
User at a financial services firm with 10,001+ employees
We use it primarily for latency monitoring and capturing latency statistics. View full review »
Ralph Muro
Performance Engineer at a individual & family service with 1,001-5,000 employees
Monitoring our environments is our primary use case. We use it to monitor our trading platform, customer experience, troubleshooting message flow, troubleshooting message formations, as well as for capacity performance analysis, and system testing. View full review »
User with 10,001+ employees
We use it for checking the latency for different markets, clients, and brokers across different sites and core locations. We are using this internally within our team for measuring latency for different points, across the whole flow, within our applications. View full review »
Srini Venkatesan
Director at a financial services firm with 10,001+ employees
We use it to monitor our client connectivity latencies, as perceived by the client. We have a number of clients connecting and we monitor their sessions. The real-time analytics we use are for the electronic trading environment, the client coming into the electronic trading order flow, the buy side and the sell side. That's where we are primarily using it, but we are planning to expand it further in due course to other trading venues. Right now, most of our Corvil devices are monitoring the electronic trading environment. View full review »
EMEA Head of Electronic Trading App Management at a financial services firm with 10,001+ employees
We primarily use it for latency monitoring and benchmarking. We look at the geographical location of our servers and European exchanges, using this product to measure the amount of time: * It takes for us to receive an order from a client. * Routing the client's order to the exchange in the exchange data center. * Executing on the order book. * The hops all the way back to the client's execution. That latency allows us to establish whether or not there might be any problems with the connection, or understand if we're meeting expectations around latency benchmarks from the clients' perspective. View full review »
Network Operations at a financial services firm with 1,001-5,000 employees
We are using it mostly for order entry and FIX protocol. View full review »

Sign Up with Email