The Importance of Monitoring Consumer ISPs
Monitoring consumer ISPs is really crucial. Learn why this type of monitoring is so essential.
Join the DZone community and get the full member experience.Join For Free
at their heart, web performance monitoring companies have a basic goal: to provide their customers with the most comprehensive and accurate look possible into the health of their online systems. this goal is accomplished in multiple ways, but one of the most important is through synthetic testing from servers plugged into the internet backbone.
using these nodes as ‘dummy computers’ on which to run tests of their websites and applications, businesses can glean valuable data pertaining to how their sites and applications are performing, and also how peering issues, connectivity bottlenecks, etc. are affecting their overall performance. remember, the internet is a series of tubes, and congestion in one location often has ripple effects that spread far and wide.
there are two key types of network providers: transit providers (e.g. cogent, level3, ntt) and the last mile (e.g. comcast, verizon, at&t, etc.). as an end user, you do not buy your internet from cogent, but from comcast. yet in your datacenter, you buy connectivity from the backbone providers like cogent or level3, or you buy into peering exchanges.
to present, the most accurate view into the end user experience a monitoring tool requires having nodes on these two types of networks, and more on the “eyeball” or last mile networks like comcast, at&t, etc. – i.e. isps that end users are using to access the internet.
this principle has been made even clearer over the last few years with the fight over net neutrality, during which it was made widely known that some of these isps practice throttling techniques on their networks, showing favor to certain websites by slowing service down for others (the whole “fast lane/slow lane” battle that we saw take place in the halls of congress). but without nodes that are connected to these networks, how were businesses supposed to know if poor performance was due to problems on their own end, or with the consumer isps themselves?
this is why catchpoint has been investing heavily in expanding our node infrastructure on these prominent eyeball networks. when looking at broadband providers in the u.s. , you’ll see that over 60 million internet users in the u.s. (or 71.4%) are subscribers of the big four: comcast (26.5%), at&t (19.1%), time warner (14.9%), or verizon (10.9%).
so not only does catchpoint have over 200 nodes in 39 different cities across the united states, but we are connected to all the big four carriers, as well as the next five biggest isps (centurylink, charter, cox, cablevision, and frontier), which together handle another 21% of all u.s. internet traffic.
(note: despite some statements to the contrary, we are in fact monitoring in the cloud, both from transit networks – where companies buy bandwidth – and from eyeball networks, where actual consumers are. but we’re not limited to monitoring from public clouds like amazon web services, where your consumers are not.)
on top of that, catchpoint has also stayed ahead of the curve by building nodes that are specifically tailored to ipv6 (we’re at 50 and counting), which has already begun to replace the exhausted ipv4 addresses . in doing so, we’re ensuring that our customers have access to the most current platform possible.
of course, the u.s. is hardly the only place where we’re expanding our network; our global node coverage encompasses:
total number of agents/nodes: 459
- backbone: 332
- last mile: 90
- wireless: 37
- 69 countries
- 164 cities
- 180 autonomous systems covered
when you combine all that with the amount of data that every test run provides, plus the ability to isolate and analyze every component of your web transactions, it results in a level of depth into their online systems that’s simply unavailable from any other monitoring system. because we are not just a web monitoring tool; you can with catchpoint keep an eye on 13 different kinds of end points from web, dns, and traceroutes, to our latest one: websockets.
as we like to say, performance is a journey rather than a destination; it’s a never-ending process that can constantly be improved upon. therefore, we’re going to continue to invest in our testing capabilities and our node infrastructure to give the most comprehensive view to our customers.
Published at DZone with permission of Mehdi Daoudi, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.