bgpreport

Network · data from 2026-11-12

AS268940 Kayros Link

Registry name: AS268940 - Kayros Link, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268940, 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.

2804:5cf0:8000::/38 Invalid: maxLength Nonecovered by 2804:5cf0:8000::/33 39 6%low visibility 19
189.39.176.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 66
189.39.178.0/24 Valid Other IRR onlyTC 671 100% 67
189.39.179.0/24 Valid Other IRR onlyTC 668 99% 67
2804:5cf0::/32 Valid Other IRR onlyALTDB, RADB, TC 633 100% 67
2804:5cf0:8000::/33 Valid Other IRR onlyRADB 356 56% 65
189.39.178.0/23 Valid Other IRR onlyRADB, TC 212 32% 57
189.39.176.0/23 Valid Other IRR onlyRADB, TC 210 31% 57

AS-SET

AS268940's PeeringDB record names no AS-SET.

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 12 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:5cf0:8000::/38ROA 2804:5cf0::/32 AS268940 has maxLength 34; the route is a /38. Raise the maxLength, or add a ROA for 2804:5cf0:8000::/38.39 of 636
Route object: none2804:5cf0:8000::/38No route object for it. A route object for 2804:5cf0:8000::/33 with origin AS268940 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268940 in the RIR database for the space.39 of 636
Route object: RIR189.39.176.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR189.39.178.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR189.39.179.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:5cf0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:5cf0:8000::/33Route object only in RADB. Add it in the RIR database for the space.356 of 636
Route object: RIR189.39.178.0/23Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR189.39.176.0/23Route object only in RADB, TC. Add it in the RIR database for the space.210 of 673

Route objects not announced

Route objects with origin AS268940 whose prefix no peer sees AS268940 announce. Many are kept on purpose (backup routes, space announced only in some places).

189.39.176.0/24TCValid
189.39.177.0/24TCValid
2804:5cf0::/33RADBValid

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.