Kentik announced the launch of Kentik Cloud, a new product suite for public cloud environments.
As part of the Kentik platform, Kentik Cloud fuses traffic and telemetry data with business, security, internet and cloud metadata to give enterprise customers increased visibility, improved performance and better cost control of the networking that connects their entire cloud environment.
The launch of Kentik Cloud extends observability to public clouds, putting forward the industry’s most comprehensive way to visualize cloud network performance, troubleshoot connectivity issues, control and reduce traffic costs, optimize service delivery, migrate apps to the cloud and secure cloud environments from network attacks.
Kentik Cloud expands on the company’s existing cloud monitoring capabilities with four core new feature sets:
- Observation Deck: an integrated user experience with configurable widgets that lets users put their most important data and insights front and center, and quickly answer any question about the network, using all types of network telemetry and contextual data.
- Kentik Map: an end-to-end visual depiction of virtual private clouds (VPCs), on-premises networks and the connectivity between them to see traffic to and through the cloud network elements for faster troubleshooting. This feature also brings together AWS CloudWatch and infrastructure health metrics.
- Cloud Performance Monitor: a feature that automatically detects the most important network paths used inside cloud networks and interconnections to on-prem networks. Proactive tests measure latency, jitter and packet loss data, and interface with Kentik’s large network of public cloud agents for easy performance monitoring of internet and multi-cloud services.
- Cloud Traffic Cost Explorer: a tool to automatically calculate actual costs of cloud network traffic over time, as well as cost projections by group and account, helping to lower data transfer costs by quickly finding traffic inefficiencies.
“We built the Kentik Cloud product suite because we saw our customers struggling to run cloud networks with the precision and control that they’re accustomed to,” said Christoph Pfister, Chief Product Officer at Kentik. “Most cloud monitoring tools don’t focus on infrastructure or can’t see beyond a single cloud environment — and the old networking tools simply don’t keep up with the pace of CloudOps, if they even understand cloud networking constructs or VPC Flow Logs. With Kentik Cloud, our customers can manage the performance, visibility and costs of their cloud networking, at-scale and all within one solution.”
The Latest
IT organizations have historically measured success by how quickly they can respond when something goes wrong. The entire discipline of Incident Management has been optimized around mean time to resolution, first-response SLAs and ticket closure rates. But new research suggests that even though this is a well-executed playbook, it's no longer enough to retain customers ...
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...