bgpreport

Network · data from 2026-11-12

AS265447 romaotelecom

Registry name: AS265447 - Hilink Comunicacoes, BR · PeeringDB

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

Announced routes

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

170.238.36.0/24 Valid Nonecovered by 170.238.36.0/23 670 100% 66
170.238.37.0/24 Valid Nonecovered by 170.238.36.0/23 670 100% 66
170.238.36.214/32 Valid Nonecovered by 170.238.36.0/23 1 0%low visibility 1
170.238.37.188/32 Valid Nonecovered by 170.238.36.0/23 1 0%low visibility 1
168.196.84.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
168.196.84.0/23 Valid Other IRR onlyRADB, TC 671 100% 66
170.238.36.0/22 Valid Other IRR onlyTC 671 100% 66
45.70.74.0/24 Valid Other IRR onlyTC 670 100% 66
170.238.36.0/23 Valid Other IRR onlyRADB 670 100% 66
45.70.75.0/24 Valid Other IRR onlyTC 669 99% 67
45.70.72.0/24 Valid Other IRR onlyRADB 667 99% 67
45.70.73.0/24 Valid Other IRR onlyTC 667 99% 66
170.238.38.0/23 Valid Other IRR onlyRADB 667 99% 67
2804:3448::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:3448:2d00::/40 Valid Other IRR onlyRADB 635 100% 67
2804:3448:2e00::/40 Valid Other IRR onlyTC 634 100% 67
2804:3448:2f00::/40 Valid Other IRR onlyTC 634 100% 67
2804:3448::/33 Valid Other IRR onlyTC 633 100% 67
2804:3448:8000::/33 Valid Other IRR onlyTC 633 100% 67
168.196.86.0/23 Valid Other IRR onlyRADB, TC 9 1%low visibility 6
168.196.84.0/24 Valid Other IRR onlyTC 7 1%low visibility 5
168.196.85.0/24 Valid Other IRR onlyTC 7 1%low visibility 5
168.196.86.0/24 Valid Other IRR onlyTC 7 1%low visibility 5
168.196.87.0/24 Valid Other IRR onlyTC 7 1%low visibility 5

AS-SET

AS265447'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 29 are in fix.csv.

  • Route object: none4
  • Route object: RIR20
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none170.238.36.0/24No route object for it. A route object for 170.238.36.0/23 with origin AS265447 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265447 in the RIR database for the space.670 of 673
Route object: none170.238.37.0/24No route object for it. A route object for 170.238.36.0/23 with origin AS265447 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265447 in the RIR database for the space.670 of 673
Route object: none170.238.36.214/32No route object for it. A route object for 170.238.36.0/23 with origin AS265447 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS265447 in the RIR database for the space.1 of 673
Route object: none170.238.37.188/32No route object for it. A route object for 170.238.36.0/23 with origin AS265447 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS265447 in the RIR database for the space.1 of 673
Route object: RIR168.196.84.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.196.84.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.238.36.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.70.74.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.238.36.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.70.75.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.70.72.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.70.73.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR170.238.38.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:3448::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3448:2d00::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3448:2e00::/40Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3448:2f00::/40Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3448::/33Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:3448:8000::/33Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR168.196.86.0/23Route object only in RADB, TC. Add it in the RIR database for the space.9 of 673
Route object: RIR168.196.84.0/24Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR168.196.85.0/24Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR168.196.86.0/24Route object only in TC. Add it in the RIR database for the space.7 of 673
Route object: RIR168.196.87.0/24Route object only in TC. Add it in the RIR database for the space.7 of 673

Route objects not announced

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

45.70.72.0/22RADBValid
2804:3448::/34TCValid
2804:3448:4000::/34TCValid
2804:3448:8000::/34TCValid
2804:3448:c000::/34TCValid

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.