bgpreport

Network · data from 2026-11-12

AS262966 KDM INTERNET

Registry name: AS262966 - KDM INTERNET TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262966, 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.
168.121.248.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
186.250.28.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
190.89.12.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
168.121.248.0/23 Valid Other IRR onlyTC 669 99% 67
168.121.250.0/23 Valid Other IRR onlyTC 669 99% 67
186.250.30.0/23 Valid Other IRR onlyTC 669 99% 67
186.250.28.0/23 Valid Other IRR onlyTC 668 99% 67
190.89.12.0/23 Valid Other IRR onlyTC 668 99% 67
190.89.14.0/23 Valid Other IRR onlyTC 668 99% 67
2804:ea8::/32 Valid Other IRR onlyTC 635 100% 69
2804:ea8::/33 Valid Other IRR onlyTC 635 100% 69
2804:ea8:8000::/33 Valid Other IRR onlyTC 635 100% 69
168.121.248.0/24 Valid Other IRR onlyTC 121 18% 41
168.121.249.0/24 Valid Other IRR onlyTC 121 18% 41
168.121.250.0/24 Valid Other IRR onlyTC 121 18% 41
168.121.251.0/24 Valid Other IRR onlyTC 121 18% 41
186.250.28.0/24 Valid Other IRR onlyTC 121 18% 41
186.250.29.0/24 Valid Other IRR onlyTC 121 18% 41
186.250.30.0/24 Valid Other IRR onlyTC 121 18% 41
186.250.31.0/24 Valid Other IRR onlyTC 121 18% 41
190.89.12.0/24 Valid Other IRR onlyTC 121 18% 41
190.89.13.0/24 Valid Other IRR onlyTC 121 18% 41
190.89.14.0/24 Valid Other IRR onlyTC 121 18% 41
190.89.15.0/24 Valid Other IRR onlyTC 121 18% 41
2804:ea8::/34 Valid Other IRR onlyTC 107 17% 40
2804:ea8:4000::/34 Valid Other IRR onlyTC 107 17% 40
2804:ea8:8000::/34 Valid Other IRR onlyTC 107 17% 40
2804:ea8:c000::/34 Valid Other IRR onlyTC 107 17% 40

AS-SET

PeeringDB's irr_as_set for AS262966: TC::AS262966:AS-KDM. 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 (AS262966 isn't in the set, or no route object for AS262966 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 objectsAS262966 in itNot covered
TC::AS262966:AS-KDM TC 2653 Yes 0

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

  • Route object: RIR28
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
Route object: RIR168.121.248.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.250.28.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR190.89.12.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR168.121.248.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR168.121.250.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.250.30.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.250.28.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR190.89.12.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR190.89.14.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:ea8::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:ea8::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:ea8:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR168.121.248.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR168.121.249.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR168.121.250.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR168.121.251.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR186.250.28.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR186.250.29.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR186.250.30.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR186.250.31.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR190.89.12.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR190.89.13.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR190.89.14.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR190.89.15.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR2804:ea8::/34Route object only in TC. Add it in the RIR database for the space.107 of 636
Route object: RIR2804:ea8:4000::/34Route object only in TC. Add it in the RIR database for the space.107 of 636
Route object: RIR2804:ea8:8000::/34Route object only in TC. Add it in the RIR database for the space.107 of 636
Route object: RIR2804:ea8:c000::/34Route object only in TC. Add it in the RIR database for the space.107 of 636

Route objects not announced

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

2804:ea8::/35TCValid
2804:ea8::/36TCValid
2804:ea8:1000::/36TCValid
2804:ea8:2000::/35TCValid
2804:ea8:2000::/36TCValid
2804:ea8:3000::/36TCValid
2804:ea8:4000::/35TCValid
2804:ea8:4000::/36TCValid
2804:ea8:5000::/36TCValid
2804:ea8:6000::/35TCValid
2804:ea8:6000::/36TCValid
2804:ea8:7000::/36TCValid
2804:ea8:8000::/35TCValid
2804:ea8:8000::/36TCValid
2804:ea8:9000::/36TCValid
2804:ea8:a000::/35TCValid
2804:ea8:a000::/36TCValid
2804:ea8:b000::/36TCValid
2804:ea8:c000::/35TCValid
2804:ea8:c000::/36TCValid
2804:ea8:d000::/36TCValid
2804:ea8:e000::/35TCValid
2804:ea8:e000::/36TCValid
2804:ea8:f000::/36TCValid

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.