The health of the internet at your fingertips.
Know immediately if a common SaaS app, public cloud, or DNS service is causing issues.
Closely monitor DNS to see if, where, and how breakdowns occur.
Alert on critical BGP activity that could affect network traffic, security, and performance.
“The real-time visibility we need to deliver a great customer experience.”
With Kentik, businesses gain full ‘internet-weather’ visibility — combining BGP-route monitoring, traffic flow analytics, and synthetic tests to track Internet-wide routing events, outage alerts, and path changes across ASes. Real-time dashboards and alerting make it possible to detect and respond to outages before users notice.
Kentik’s BGP Route Viewer + Path View provides real-time AS-path visualizations and hop-by-hop routing data. Combined with flow and synthetic-test info, Kentik lets you watch path changes, reachability events and AS-hops shift immediately when an outage or routing incident occurs.
Kentik provides hop-by-hop path insight via traceroute-based synthetic tests, and also overlays real traffic flows with BGP/AS-path metadata. This lets you reconstruct how traffic travels — hop-by-hop — from user or client networks to a service, through the Internet.
Kentik’s unified platform merges BGP routing data, Internet-wide AS-path metadata, and actual flow traffic — allowing visualization of real traffic paths across the Internet in a single map or path-analysis view. Kentik also uses advanced traceroute mechanisms to trace public internet paths via synthetic testing. These features make Kentik one of the most comprehensive ways to understand where and how your packets traverse the public Internet.
Model outage impact by continuously testing critical destinations from the regions and networks your users depend on, then translating failure windows into affected geographies, ISPs, and paths. Kentik supports this with synthetic monitoring and internet-path context so you can measure blast radius, pinpoint where failures occur, and quantify likely user impact.
You can use Kentik to benchmark ISP performance by running the same set of continuous synthetic tests from (1) private agents placed at remote offices/branch edges and (2) global agents for a neutral baseline. Track latency/loss/jitter and key SaaS/DNS/HTTP checks, compare results across providers and regions, and alert when one office’s path diverges from the baseline. This gives you evidence for whether an incident is caused by the local ISP path, broader internet routing conditions, or the destination service itself.
To compare BGP routes reliably, look at (1) control-plane views from multiple route collectors and peers (to see origins and AS paths over time) and (2) data-plane measurements like traceroute from multiple vantage points (to see the actual hop-by-hop path users take). Kentik supports this by combining BGP route monitoring and AS-path visualization (BGP Route Viewer + Path View) with traceroute-based synthetic tests and traffic context, so you can compare paths across regions, spot where the path changed, and see whether the change impacted performance or reachability.
Anycast can route users to a suboptimal POP when interdomain routing policy produces “path inflation” or unexpected tie-break behavior, so the practical way to find inefficiency is to measure latency and hop/AS paths to the same anycast IP from many locations and then flag cases where users are consistently mapped to a distant site or a longer path than necessary. Kentik supports this by running synthetic tests from many global locations and correlating those results with AS-path visibility so you can see which regions are taking inflated routes, when the mapping shifted, and what changed in routing.
“Zombie routes” can occur when withdrawals are missed and stale routes linger in the global table, while “black holes” occur when traffic is routed to a null destination and dropped. Both show up as sudden reachability loss, abnormal path changes, or traffic disappearing for specific prefixes. Kentik supports faster detection by monitoring prefix reachability and AS paths over time, alerting on suspicious routing events, and correlating BGP changes with synthetic reachability signals and real traffic shifts so teams can quickly confirm whether the problem is a stale route, a withdrawal propagation issue, or an intentional blackhole action.




