bgpreport

Network · data from 2026-11-12

AS265451 INFOLINK TELECOM

Registry name: AS265451 - INFOLINK TELECOM, BR · PeeringDB

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

Announced routes

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

38.211.204.0/23 No ROA Nonecovered by 38.211.204.0/22 114 17% 41
38.211.206.0/23 No ROA Nonecovered by 38.211.204.0/22 114 17% 41
38.211.204.0/22 No ROA Other IRR onlyRADB 671 100% 66
168.196.104.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
45.175.204.0/22 Valid Other IRR onlyRADB, TC 669 99% 66
2804:3454:2000::/35 Valid Other IRR onlyRADB 634 100% 67
2804:3454::/32 Valid Other IRR onlyRADB, TC 632 99% 67
168.196.104.0/23 Valid Other IRR onlyRADB, TC 114 17% 41
168.196.106.0/23 Valid Other IRR onlyRADB, TC 112 17% 41
2804:3454::/33 Valid Other IRR onlyRADB, TC 55 9%low visibility 31
2804:3454:8000::/33 Valid Other IRR onlyRADB, TC 55 9%low visibility 31
2804:3454::/34 Valid Other IRR onlyTC 19 3%low visibility 10
2804:3454:4000::/34 Valid Other IRR onlyTC 19 3%low visibility 10
2804:3454:8000::/34 Valid Other IRR onlyTC 19 3%low visibility 10
2804:3454:c000::/34 Valid Other IRR onlyTC 19 3%low visibility 10

AS-SET

PeeringDB's irr_as_set for AS265451: AS265451:AS-ANNOUNCEMENTS. 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 (AS265451 isn't in the set, or no route object for AS265451 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 objectsAS265451 in itNot covered
AS265451:AS-ANNOUNCEMENTS TC 1223 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 28 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR13
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none38.211.204.0/23No ROA covers it. Add a ROA for AS265451, maxLength 23.114 of 673
Route object: none38.211.204.0/23No route object for it. A route object for 38.211.204.0/22 with origin AS265451 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265451 in the RIR database for the space.114 of 673
ROA: none38.211.206.0/23No ROA covers it. Add a ROA for AS265451, maxLength 23.114 of 673
Route object: none38.211.206.0/23No route object for it. A route object for 38.211.204.0/22 with origin AS265451 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265451 in the RIR database for the space.114 of 673
ROA: none38.211.204.0/22No ROA covers it. Add a ROA for AS265451, maxLength 22.671 of 673
Route object: RIR38.211.204.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.196.104.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.175.204.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:3454:2000::/35Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3454::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR168.196.104.0/23Route object only in RADB, TC. Add it in the RIR database for the space.114 of 673
Route object: RIR168.196.106.0/23Route object only in RADB, TC. Add it in the RIR database for the space.112 of 673
Route object: RIR2804:3454::/33Route object only in RADB, TC. Add it in the RIR database for the space.55 of 636
Route object: RIR2804:3454:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.55 of 636
Route object: RIR2804:3454::/34Route object only in TC. Add it in the RIR database for the space.19 of 636
Route object: RIR2804:3454:4000::/34Route object only in TC. Add it in the RIR database for the space.19 of 636
Route object: RIR2804:3454:8000::/34Route object only in TC. Add it in the RIR database for the space.19 of 636
Route object: RIR2804:3454:c000::/34Route object only in TC. Add it in the RIR database for the space.19 of 636

Route objects not announced

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

45.175.204.0/23TCValid
45.175.204.0/24TCValid
45.175.205.0/24TCValid
45.175.206.0/23TCValid
45.175.206.0/24TCValid
45.175.207.0/24TCValid
168.196.104.0/24RADB, TCValid
168.196.105.0/24RADB, TCValid
168.196.106.0/24RADB, TCValid
168.196.107.0/24RADB, TCValid

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.