Kentik Blog

Today we’re introducing the most important update to OTT Service Tracking for ISPs since its inception. To understand the power of this workflow, we’ll review the basics of OTT service monitoring and explain why our capability is so popular with our broadband provider customers.

VP of Engineering Mike Ho kicks off a blog series to talk about Kentik’s engineering team, where they’ve been, decisions they’ve made, problems solved, and fun facts about the team and the platform.

BGP is a critical network protocol, and yet, BGP is often not monitored. BGP issues that go unchecked can turn into major problems. This post explains how Kentik can help you to easily monitor BGP and catch critical issues quickly.

From a threat actor’s side, launching a DDoS attack is both easy and cheap. For a business, it’s costly, disruptive and comes with big hurdles for effective detection and mitigation. Kentik Protect can help.

TechEnabler is a Kentik Channel Partner headquartered in Sao Paulo, Brazil. In this Q&A, VP of Channel Sales Jim Frey highlights a bit about the partner, who they are and what they do.

In this post, we offer insight into how to monitor traffic through transit gateways by understanding routing dynamics and cloud architecture. Learn more.

In our employee spotlight series, we highlight members of the Kentik team, what they’re working on, and their most memorable moments within the company. In this Q&A, meet Steven Reynolds, a Kentik UI engineer.

Networking in the cloud can be like a black box. In this blog we discuss five essential properties of network observability for cloud, giving you the ability to answer any question about your cloud network.

Read how this leading internet services provider in Latin America uses Kentik for peering and capacity planning and a real-time view of performance and availability throughout the network.

Today we expand our partnership with New Relic. Together, we’re deepening New Relic’s full-stack observability into the network layer and giving IT operations, SREs and development teams shared context to resolve issues quickly.