bgpreport

Network · data from 2026-11-12

AS263459 Interlink Comunicação Virtual

Registry name: AS263459 - Interlink Comunicacao Virtual LTDA ME, BR · PeeringDB

9IPv4 routes 0.0% RPKI valid · 88.9% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
12No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS263459, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263459, 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.
177.190.169.0/24 No ROA Nonecovered by 177.190.168.0/23 672 100% 67
2804:1224::/33 No ROA Nonecovered by 2804:1224::/32 1 0%low visibility 1
2804:1224:8000::/33 No ROA Nonecovered by 2804:1224::/32 1 0%low visibility 1
177.190.168.0/21 No ROA Other IRR onlyALTDB, NTTCOM, RADB, TC 672 100% 67
177.190.168.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.190.171.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.190.172.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.190.173.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.190.174.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.190.175.0/24 No ROA Other IRR onlyRADB 672 100% 67
177.190.170.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:1224::/32 No ROA Other IRR onlyALTDB, NTTCOM, RADB, TC 634 100% 67

AS-SET

AS263459'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 30 are in fix.csv.

  • ROA: none12
  • Route object: none3
  • Route object: RIR9
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none177.190.169.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: none177.190.169.0/24No route object for it. A route object for 177.190.168.0/23 with origin AS263459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263459 in the RIR database for the space.672 of 673
ROA: none2804:1224::/33No ROA covers it. Add a ROA for AS263459, maxLength 33.1 of 636
Route object: none2804:1224::/33No route object for it. A route object for 2804:1224::/32 with origin AS263459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263459 in the RIR database for the space.1 of 636
ROA: none2804:1224:8000::/33No ROA covers it. Add a ROA for AS263459, maxLength 33.1 of 636
Route object: none2804:1224:8000::/33No route object for it. A route object for 2804:1224::/32 with origin AS263459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263459 in the RIR database for the space.1 of 636
ROA: none177.190.168.0/21No ROA covers it. Add a ROA for AS263459, maxLength 21.672 of 673
Route object: RIR177.190.168.0/21Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.190.168.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: RIR177.190.168.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.190.171.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: RIR177.190.171.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.190.172.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: RIR177.190.172.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.190.173.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: RIR177.190.173.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.190.174.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: RIR177.190.174.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.190.175.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.672 of 673
Route object: RIR177.190.175.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.190.170.0/24No ROA covers it. Add a ROA for AS263459, maxLength 24.671 of 673
Route object: RIR177.190.170.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:1224::/32No ROA covers it. Add a ROA for AS263459, maxLength 32.634 of 636
Route object: RIR2804:1224::/32Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

177.190.168.0/22RADBNo ROA
177.190.168.0/23RADBNo ROA
177.190.170.0/23RADBNo ROA
177.190.172.0/22RADBNo ROA
177.190.172.0/23RADBNo ROA
177.190.174.0/23RADBNo ROA

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.