Kentik had 29 outages in the last 2 years totaling 256h 6m of downtime — averaging 1.2 incidents per month.
There were 29 Kentik outages since June 6, 2025 totaling 256h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're investigating errors on the Universal Agents page in Portal.
We have identified the issue and are working on a fix. We will update when the fix has been deployed and verified.
The issue has been resolved in all affected environments.
We are currently investigating an issue with the US portal. Customers may experience slow or intermittent performance.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We experienced a brief impact to customer BGP sessions and inbound flow. Kentik Engineering is investigating, although most sessions have recovered.
This incident has been resolved.
We're experiencing an elevated level of errors in our universal agent infrastructure and are currently looking into the issue. This appears to be impacting agent management operations including adding and removing NMS devices.
We are now seeing significantly reduced error rates and systems are operational.
This incident has been resolved.
At approximately 01:00 UTC on February 27, 2026, a configuration change deployed to the Kentik NMS service operated beyond its intended scope. Our monitoring detected the issue and the deployment was halted. As a result, some customers may see gaps in historical NMS metrics data older than 90 days for a subset of devices. We are investigating recovery options and have implemented safeguards to prevent recurrence.
The issue has been identified and a fix is being deployed.
A fix has been deployed as of 1642 UTC, and we are continuing to monitor recovery.
This incident has been resolved.
We are currently investigating an issue with our Customer Portal. Customers may have difficulties logging in and returning data.
We have identified the source of the issue as an underlying network transport problem and are working to remediate. There is no ETA at this time. Updates will be provided.
Customer flow data and associated retention are not believed to be impacted at this time.
Both redundant connections to a core site serving the Ashburn IAD US cluster are currently offline. Our engineers have been dispatched and are actively working to restore service. The Ashburn IAD US portal is unavailable at this time, and some data ingestion may be delayed or incomplete. We will provide regular updates until the US portal is fully restored.
Our underlying inter site transport has been restored, and we are monitoring recovery of all services.
We are continuing to recover services related to flow ingest and query.
This incident has been resolved.
We are currently investigating an issue with query performance that may impact some customers.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with OTT Enrichment affecting a subset of customers.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Customers may observe missing or inaccurate data for devices added or modified within the last ~48 hours. We are actively investigating.
The issue has been identified and we are deploying a fix.
This issue is now resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We have identified the issue and are working on a fix. Synthetics test data at the onset of this incident has been queued and will be processed for customer use once the fix is implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A component handling interface tracking and topology calculation is unstable. This prevents network maps and the device connections list from loading in the portal and may impact updates to flow tagging. We are actively investigating this issue.
A fix has been implemented. Network maps and flow tagging are working normally again.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We've spotted that something has gone wrong. We have identified an issue where auto-update queries can return less data than intended. We are working on a fix, and will provide an update soon.
We think the impact from the auto-update queries is over.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue where a subset of customers may see degraded custom dimension enrichment.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
If your flow volumes fluctuate frequently and you are leveraging Kentik's dynamic sampling functionality, traffic ingested beginning approximately 06 Oct 2026 18:30 may report incorrect volumes.
This issue was fully resolved for traffic received as of approximately 08 Oct 2025 22:30 UTC.
We observed some BGP customer sessions flapping and a brief flow drop between 4:04 and 4:08 due to one of our upstream providers maintenance.
We've identified query errors when utilizing specific dimensions in Data Explorer. We believe we have fixed this problem and are currently monitoring the situation.
Query is fully operational.
We are currently investigating issues with customer BGP sessions to our US IAD1 environment.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing approximately 46% loss of BGP v4/v6 prefix enrichment data. Some customers may have noticed BGP peering session flaps during this time.
From 11:47 - 11:57 UTC, there was partial loss of BGP v4/v6 prefix enrichment data. Peerings have fully recovered at this time, and we are monitoring.
This incident is now resolved.
One of our upstream providers had an incident started at 2025-09-06 10:44:57 UTC which caused customer BGP sessions established with our US SAAS to drop. BGP sessions should be re-established at this time. We are continuing to monitor the situation.
We're currently investigating the issue, and will provide an update soon.
BGP peering and enrichment has been restored to normal operation. We will continue monitoring the service.
We've identified partial flow loss that affected some customers during this event. We will continue monitoring and investigating.
We've made an additional change that we believe will resolve the partial flow and NMS ingest outage. We will continue to monitor.
We continue to investigate a limited number of customers who are experiencing BGP session stability issues.
All remaining BGP sessions should now be stable; we will continue to monitor over the next 24-48 hours.
This incident has been resolved.
We are experiencing partial flow loss and some BGP session instability. We have identified the cause and are working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.