Kentik Outage History

Kentik is up right now

Pingoru has recorded 53 incidents for Kentik: 35 in the last 12 months and 11 in the last 90 days.

Source: status.kentik.com

53incidents recorded
35last 12 months
11last 90 days
7 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Kentik in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202626 of 720 (1%)
May 202611 of 744 (0%)
June 2026455 of 720 (8%)
July 202639 of 744 (1%)
August 202622 of 744 (0%)
September 2026653 of 720 (7%)
October 202628 of 589 (1%)

Incidents, newest first

Minor January 29, 2026 New Device Query Inaccuracy 2h 10m Query

Started Jan 29, 2026, 11:26 PM UTC· resolved Jan 30, 2026, 01:37 AM UTC

  1. investigating Jan 29, 2026, 11:26 PM UTC

    Customers may observe missing or inaccurate data for devices added or modified within the last ~48 hours. We are actively investigating.

  2. identified Jan 29, 2026, 11:59 PM UTC

    The issue has been identified and we are deploying a fix.

  3. resolved Jan 30, 2026, 01:37 AM UTC

    This issue is now resolved.

Read the full incident report →

Minor December 22, 2025 NMS and Alerting Performance Impact 38m Alerting and Mitigation Services, NMS

Started Dec 22, 2025, 03:15 AM UTC· resolved Dec 22, 2025, 03:54 AM UTC

  1. investigating Dec 22, 2025, 03:15 AM UTC

    We are currently investigating this issue.

  2. resolved Dec 22, 2025, 03:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 16, 2025 Synthetics Service Impact 2h 12m Synthetics Ingest, Synthetics Alerting

Started Dec 16, 2025, 01:21 AM UTC· resolved Dec 16, 2025, 03:34 AM UTC

  1. investigating Dec 16, 2025, 01:21 AM UTC

    We are currently investigating this issue.

  2. identified Dec 16, 2025, 02:05 AM UTC

    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.

  3. monitoring Dec 16, 2025, 02:43 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 16, 2025, 03:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2025 Interface tracking and maps degraded 22h 55m Web Portal, Flow Ingest

Started Dec 10, 2025, 05:04 PM UTC· resolved Dec 11, 2025, 03:59 PM UTC

  1. investigating Dec 10, 2025, 05:04 PM UTC

    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.

  2. monitoring Dec 11, 2025, 02:48 AM UTC

    A fix has been implemented. Network maps and flow tagging are working normally again.

  3. resolved Dec 11, 2025, 03:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 2, 2025 US Customer Portal Degradation 52m Web Portal

Started Dec 02, 2025, 06:06 PM UTC· resolved Dec 02, 2025, 06:58 PM UTC

  1. investigating Dec 02, 2025, 06:06 PM UTC

    We are currently investigating this issue.

  2. monitoring Dec 02, 2025, 06:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Dec 02, 2025, 06:52 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 02, 2025, 06:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 12, 2025 Incomplete results from auto-update 22h 49m

Started Nov 12, 2025, 09:51 PM UTC· resolved Nov 13, 2025, 08:40 PM UTC

  1. identified Nov 12, 2025, 09:51 PM UTC

    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.

  2. resolved Nov 13, 2025, 08:40 PM UTC

    We think the impact from the auto-update queries is over.

Read the full incident report →

Major November 6, 2025 Customer Portal Degradation 2h 49m Web Portal

Started Nov 06, 2025, 12:30 AM UTC· resolved Nov 06, 2025, 03:20 AM UTC

  1. investigating Nov 06, 2025, 12:30 AM UTC

    We are currently investigating this issue.

  2. identified Nov 06, 2025, 01:11 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 06, 2025, 01:13 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Nov 06, 2025, 01:13 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Nov 06, 2025, 03:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 5, 2025 Degraded Performance of Custom Flow Dimensions 3h 2m Flow Ingest

Started Nov 05, 2025, 05:33 PM UTC· resolved Nov 05, 2025, 08:36 PM UTC

  1. investigating Nov 05, 2025, 05:33 PM UTC

    We are currently investigating an issue where a subset of customers may see degraded custom dimension enrichment.

  2. identified Nov 05, 2025, 06:13 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 05, 2025, 06:13 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 05, 2025, 08:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 6, 2025 Reported traffic volumes may be incorrect for some customers 2d 4h AWS Ingest, Azure Ingest, Flow Ingest, GCP Ingest and 1 more

Started Oct 06, 2025, 06:30 PM UTC· resolved Oct 08, 2025, 10:30 PM UTC

  1. identified Oct 10, 2025, 12:37 AM UTC

    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.

  2. resolved Oct 10, 2025, 12:38 AM UTC

    This issue was fully resolved for traffic received as of approximately 08 Oct 2025 22:30 UTC.

Read the full incident report →

Minor September 22, 2025 BGP Peering and Enrichment instability and flow loss 8m

Started Sep 22, 2025, 04:00 AM UTC· resolved Sep 22, 2025, 04:08 AM UTC

  1. resolved Sep 22, 2025, 04:44 AM 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.

Read the full incident report →

Minor September 18, 2025 Query errors with specific dimensions 14m Query

Started Sep 18, 2025, 02:31 AM UTC· resolved Sep 18, 2025, 02:45 AM UTC

  1. monitoring Sep 18, 2025, 02:31 AM UTC

    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.

  2. resolved Sep 18, 2025, 02:45 AM UTC

    Query is fully operational.

Read the full incident report →

Major September 10, 2025 US IAD1 BGP Session Impact 4h 25m BGP Peering and Enrichment

Started Sep 10, 2025, 01:21 PM UTC· resolved Sep 10, 2025, 05:47 PM UTC

  1. investigating Sep 10, 2025, 01:21 PM UTC

    We are currently investigating issues with customer BGP sessions to our US IAD1 environment.

  2. monitoring Sep 10, 2025, 01:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 10, 2025, 05:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 9, 2025 Partial BGP Peering & Enrichment Outage 29m BGP Peering and Enrichment

Started Sep 09, 2025, 11:45 AM UTC· resolved Sep 09, 2025, 12:15 PM UTC

  1. investigating Sep 09, 2025, 10:54 PM UTC

    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.

  2. monitoring Sep 09, 2025, 10:55 PM UTC

    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.

  3. resolved Sep 09, 2025, 10:56 PM UTC

    This incident is now resolved.

Read the full incident report →

Notice September 6, 2025 BGP Peering and Enrichment instability – BGP Peering and Enrichment

Started Sep 06, 2025, 12:10 PM UTC· resolved Sep 06, 2025, 12:10 PM UTC

  1. resolved Sep 06, 2025, 12:10 PM UTC

    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.

Read the full incident report →

Minor August 25, 2025 BGP Peering Outage, partial flow and NMS ingest loss in US SaaS 4d BGP Peering and Enrichment

Started Aug 25, 2025, 03:20 PM UTC· resolved Aug 29, 2025, 03:36 PM UTC

  1. investigating Aug 25, 2025, 03:20 PM UTC

    We're currently investigating the issue, and will provide an update soon.

  2. monitoring Aug 25, 2025, 03:37 PM UTC

    BGP peering and enrichment has been restored to normal operation. We will continue monitoring the service.

  3. monitoring Aug 25, 2025, 04:23 PM UTC

    We've identified partial flow loss that affected some customers during this event. We will continue monitoring and investigating.

  4. monitoring Aug 26, 2025, 03:48 AM UTC

    We've made an additional change that we believe will resolve the partial flow and NMS ingest outage. We will continue to monitor.

  5. monitoring Aug 26, 2025, 04:09 PM UTC

    We continue to investigate a limited number of customers who are experiencing BGP session stability issues.

  6. monitoring Aug 27, 2025, 01:23 AM UTC

    All remaining BGP sessions should now be stable; we will continue to monitor over the next 24-48 hours.

  7. resolved Aug 29, 2025, 03:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2025 Partial flow loss and BGP instability 2h 18m BGP Peering and Enrichment, Flow Ingest

Started Aug 21, 2025, 10:41 PM UTC· resolved Aug 22, 2025, 01:00 AM UTC

  1. identified Aug 21, 2025, 10:41 PM UTC

    We are experiencing partial flow loss and some BGP session instability. We have identified the cause and are working on a fix.

  2. monitoring Aug 21, 2025, 10:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 22, 2025, 01:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 19, 2025 Universal agent - partial outage 1d 6h

Started Aug 19, 2025, 02:50 PM UTC· resolved Aug 20, 2025, 09:37 PM UTC

  1. investigating Aug 19, 2025, 02:50 PM UTC

    We're experiencing a partial outage with our Universal Agent infrastructure causing new installs to fail. This is similar to last week's incident.

  2. monitoring Aug 19, 2025, 03:25 PM UTC

    This partial outage seems to be over. We're monitoring.

  3. resolved Aug 20, 2025, 09:37 PM UTC

    We've deployed improvements to our system that should prevent this issue from reoccurring. We're still working on more comprehensive fixes with a Q3 release target.

Read the full incident report →

Major August 9, 2025 Synthetics Test Failures 2d 19h Synthetics Ingest, Synthetics Alerting

Started Aug 09, 2025, 04:00 AM UTC· resolved Aug 11, 2025, 11:08 PM UTC

  1. investigating Aug 09, 2025, 04:10 PM UTC

    We are currently investigating Synthetics test failures.

  2. identified Aug 09, 2025, 04:35 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Aug 09, 2025, 04:38 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Aug 09, 2025, 05:04 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Aug 09, 2025, 05:05 PM UTC

    Synthetics currently appears stable, but the team will be monitoring throughout the weekend.

  6. resolved Aug 11, 2025, 11:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 11, 2025 Query Failures 2m Query

Started Jun 11, 2025, 05:15 PM UTC· resolved Jun 11, 2025, 05:17 PM UTC

  1. monitoring Jun 11, 2025, 05:15 PM UTC

    We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

  2. resolved Jun 11, 2025, 05:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 6, 2025 Potential Elevated Query Errors 3h 27m Query

Started Jun 06, 2025, 09:51 PM UTC· resolved Jun 07, 2025, 01:18 AM UTC

  1. identified Jun 06, 2025, 09:51 PM UTC

    We're experiencing an elevated level of query errors and are currently deploying a fix.

  2. identified Jun 06, 2025, 11:16 PM UTC

    We are currently monitoring a situation that may potentially impact queries. While there is no confirmed disruption at this time, we are proactively investigating early indicators. This status was created out of an abundance of caution, and we will provide updates as we learn more.

  3. monitoring Jun 07, 2025, 12:37 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 07, 2025, 01:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 20, 2025 Internet Instability 20h 24m BGP Peering and Enrichment, Web Portal, Flow Ingest

Started May 20, 2025, 06:16 PM UTC· resolved May 21, 2025, 02:40 PM UTC

  1. investigating May 20, 2025, 06:16 PM UTC

    We've spotted that something has gone wrong with out upstream Internet connectivity. We're currently investigating the issue, and will provide an update soon.

  2. identified May 20, 2025, 06:40 PM UTC

    A widespread outage is affecting multiple providers in the DC area and disrupting communication between Kentik and some customers.

  3. monitoring May 20, 2025, 08:18 PM UTC

    We have engineered inbound traffic away from our affected transit providers and should be fully reachable. We will continue to monitor and will shift traffic back once connectivity has been restored.

  4. resolved May 21, 2025, 02:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 15, 2025 IAD Network Impact 5h 14m BGP Peering and Enrichment, BGP Monitoring and Alerting, Flow Ingest

Started May 15, 2025, 02:10 PM UTC· resolved May 15, 2025, 07:24 PM UTC

  1. investigating May 15, 2025, 02:41 PM UTC

    We are currently investigating a network issue impacting our IAD Ashburn data center. Customers may observe impact to flow ingest and BGP sessions.

  2. identified May 15, 2025, 02:53 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 15, 2025, 03:35 PM UTC

    Customer flow and telemetry ingest impact has been mitigated, however, some customers with direct BGP sessions (PNI's) with Kentik in IAD Ashburn may notice their sessions currently down. We expect to recover these sessions throughout the day, and will update this incident when this effort is complete and sessions have been restored. Customers experiencing impact are encouraged to reach out to our support team -- [email protected]. We apologize for this inconvenience.

  4. resolved May 15, 2025, 07:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 3, 2025 transient internet congestion 2h 30m

Started May 03, 2025, 04:00 AM UTC· resolved May 03, 2025, 06:30 AM UTC

  1. resolved May 05, 2025, 08:56 PM UTC

    From the period of 04:00 to 06:30 UTC 3 May 2025 the Kentik US production cluster experienced internet congestion as a result of upstream provider maintenance activities. Customers may have experienced poor ingest performance from the US cluster during this time. We do not expect a recurrence of this issue.

Read the full incident report →

Critical May 1, 2025 Ingest outage 2h 10m AWS Ingest, Synthetics Ingest, Azure Ingest, Flow Ingest and 2 more

Started May 01, 2025, 11:15 PM UTC· resolved May 02, 2025, 01:25 AM UTC

  1. investigating May 02, 2025, 12:14 AM UTC

    We are currently addressing a complete loss of ingest from all agent-based ingest including kproxy, synthetics, NMS, and cloud.

  2. investigating May 02, 2025, 12:16 AM UTC

    We are continuing to investigate this issue.

  3. identified May 02, 2025, 12:17 AM UTC

    The issue has been identified and a fix is being deployed.

  4. monitoring May 02, 2025, 12:38 AM UTC

    A fix has been in place since approximately 00:11 UTC.

  5. resolved May 02, 2025, 01:25 AM UTC

    This incident has been resolved.

Read the full incident report →