bgpreport

Network · data from 2026-11-12

AS6169 Kentik Technologies

Registry name: CLOUD-42-6169 - Kentik Technologies, Inc., US · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS6169, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6169, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
208.76.14.0/24 No ROA RIR databaseARIN 673 100% 67
141.193.37.0/24 Valid Other origin onlycovered by 141.193.36.0/22 374 56% 62
141.193.36.0/22 Valid RIR databaseARIN 673 100% 67
209.50.158.0/24 Valid RIR databaseARIN 673 100% 67
209.50.159.0/24 Valid RIR databaseARIN 673 100% 67
2620:129::/44 Valid RIR databaseARIN 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS6169: ARIN::AS-KENTIK. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS6169 isn't in the set, or no route object for AS6169 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS6169 in itNot covered
ARIN::AS-KENTIK ARIN 010 No 6

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none208.76.14.0/24No ROA covers it. Add a ROA for AS6169, maxLength 24.673 of 673
Route object: none141.193.37.0/24Route objects for it name AS207063. A route object for 141.193.36.0/22 with origin AS6169 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6169 in the RIR database for the space.374 of 673
AS-SET: own ASNARIN::AS-KENTIKAS6169 isn't in AS-KENTIK (ARIN) once expanded. Add AS6169 to it.

Route objects not announced

Every route object with origin AS6169 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.