
Kentik launches Traffic Costs, an automated workflow delivering instant cost estimates for granular network traffic slices.
Traffic Costs provides network, financial, and sales teams with insights to optimize spend, improve margins, and drive revenue.
“For service providers in particular, optimizing network spend is essential to maintaining healthy margins between traffic delivery costs and revenue, directly impacting profitability, and competitive positioning,” said Jezzibell Gilmore, VP and GM of Service Providers at Kentik. “Providers want clear visibility into how each customer's traffic impacts their top and bottom lines – understanding traffic routes, costs to deliver, and more, gives providers the insights they need to reach greater profitability.”
Traditionally, obtaining accurate insights into network connectivity and traffic costs has been a significant challenge for infrastructure teams for a number of reasons:
- Complex Cost Structures – Traffic flows across multiple interfaces, transit providers, transport links, IXs, and PNIs, each with its own contract terms and cost structure, making accurate cost allocation difficult.
- Manual, Time-Consuming Analysis – Existing methods rely on multiple tools, spreadsheets, and fragmented data sources, requiring engineers and various cross-functional teams to collaborate piecing together cost estimates manually.
- Data Limitations – Flow-based tracking provides granular visibility but lacks billing accuracy, while SNMP-based utilization captures total traffic but cannot isolate specific slices.
Traffic Costs is a new workflow purpose-built to solve this long-standing problem at scale. By bringing together connectivity contract data, traffic flows, and SNMP utilization, Traffic Costs delivers instant flow-based cost estimates for key slices of traffic. With just a few clicks, operators can instantly see which slices of traffic are driving global connectivity spending – by customer, geographical market, ASN, CDN, OTT services, or even a specific set of IP addresses.
Network operators can use Kentik Traffic Costs to:
- Identify high-cost paths: Instantly surface routes and interconnects driving the most spend – and take action to optimize traffic engineering and interconnect agreements, to reduce costs over time.
- Improve profit margins: See exactly how much a customer’s traffic is costing you, and compare that against revenue to make smarter, more strategic decisions on deal pricing and renewal negotiations.
- Eliminate manual toil: Replace hours of spreadsheet wrangling and data stitching with automated traffic cost insights – freeing engineering teams to focus on higher-impact work.
- Track trends over time: With monthly cost tracking, measure the financial impact of peering optimizations or routing changes – and share progress across teams.
- Democratize cost insights: Make network cost data accessible across the business – from finance to sales to leadership – to enable more accurate services pricing, better contract negotiations, and data-backed decision making.
- More granular traffic slicing. Calculate costs by specific CDNs, OTT services and providers, geographic regions or markets, all the way down to specific customers and IP addresses.
The Latest
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...