---
title: "March 2026 - Cloud"
slug: "march-2026-cloud"
updated: 2026-06-26T20:54:00Z
published: 2026-06-26T20:54:00Z
canonical: "kb.kentik.com/march-2026-cloud"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.kentik.com/llms.txt
> Use this file to discover all available pages before exploring further.

# March 2026 - Cloud

The following updates were released to the Kentik platform for Cloud during March 2026.

## Features
- **Cloud Pathfinder performance & accuracy**: Faster connectivity reports that load only the relevant accounts, with the ability to run security group tests on ENIs and more accurate results.
- **More cost charges per group**: The connectivity cost charge limit has been raised from 10 to 100 per cost group, enabling more granular cost configuration.
- **Cloud topology metadata API**: Cloud Topology Metadata API jobs now initialize and run correctly, enabling proper fetching and management of cloud topology metadata.
- **Cloud API observability**: New metrics provide visibility into cloud integration health by provider and status code, helping identify problematic providers and troubleshoot connectivity.
- **Cloud Map without cloud devices**: The overview map now shows cloud provider icons when cloud regions exist even if there are no cloud devices, so you can navigate to the Cloud Map for metadata-only exports.

## Bug Fixes
- **Cloud Map loading**: Simplifies cloud-export detection so the topology map loads without unnecessary empty states.
- **CloudPak FPS warning**: The "Received FPS is high" warning now appears only when received FPS actually exceeds the plan's max FPS.
- **Complete flow enrichments**: A failure to fetch `kt_` enrichment columns is now treated as a fatal error, preventing flow data from shipping with missing enrichments.
- **Correct SPN credentials**: Fixes a query that could deliver expired/duplicate Azure SPN credentials, ensuring customers receive the latest valid credentials.
- **Preserve AWS action/status enrichment**: Stops ingest-time tagging from overwriting proper enrichment values (e.g., ACCEPT/OK) for AWS flow.
