bgpreport

Network · data from 2026-11-12

AS269089 Hilan Telecom

Registry name: AS269089 - Hilan Telecom Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269089, 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.
45.179.144.0/24 No ROA Other IRR onlyTC 667 99% 67
45.179.144.0/22 No ROA Other IRR onlyALTDB, RADB, TC 663 99% 67
45.179.145.0/24 No ROA Other IRR onlyTC 663 99% 67
45.179.144.0/23 No ROA Other IRR onlyTC 662 98% 67
45.179.146.0/24 No ROA Other IRR onlyTC 662 98% 67
45.179.147.0/24 No ROA Other IRR onlyTC 662 98% 67
45.179.146.0/23 No ROA Other IRR onlyTC 661 98% 67
2804:5f48::/32 No ROA Other IRR onlyALTDB, RADB, TC 634 100% 67

AS-SET

AS269089'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 16 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none45.179.144.0/24No ROA covers it. Add a ROA for AS269089, maxLength 24.667 of 673
Route object: RIR45.179.144.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
ROA: none45.179.144.0/22No ROA covers it. Add a ROA for AS269089, maxLength 22.663 of 673
Route object: RIR45.179.144.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.663 of 673
ROA: none45.179.145.0/24No ROA covers it. Add a ROA for AS269089, maxLength 24.663 of 673
Route object: RIR45.179.145.0/24Route object only in TC. Add it in the RIR database for the space.663 of 673
ROA: none45.179.144.0/23No ROA covers it. Add a ROA for AS269089, maxLength 23.662 of 673
Route object: RIR45.179.144.0/23Route object only in TC. Add it in the RIR database for the space.662 of 673
ROA: none45.179.146.0/24No ROA covers it. Add a ROA for AS269089, maxLength 24.662 of 673
Route object: RIR45.179.146.0/24Route object only in TC. Add it in the RIR database for the space.662 of 673
ROA: none45.179.147.0/24No ROA covers it. Add a ROA for AS269089, maxLength 24.662 of 673
Route object: RIR45.179.147.0/24Route object only in TC. Add it in the RIR database for the space.662 of 673
ROA: none45.179.146.0/23No ROA covers it. Add a ROA for AS269089, maxLength 23.661 of 673
Route object: RIR45.179.146.0/23Route object only in TC. Add it in the RIR database for the space.661 of 673
ROA: none2804:5f48::/32No ROA covers it. Add a ROA for AS269089, maxLength 32.634 of 636
Route object: RIR2804:5f48::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS269089 is announced.

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.