bgpreport

Network · data from 2026-11-12

AS269658 HUGS TELECOM

Registry name: AS269658 - HUGS TELECOM, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Route objects not announced registered with origin AS269658, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269658, 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.191.16.0/23 Valid Other IRR onlyRADB 671 100% 66
2804:67e8::/32 Valid Other IRR onlyRADB 629 99% 67
2804:67e8::/33 Valid Other IRR onlyRADB 354 56% 64
2804:67e8:8000::/33 Valid Other IRR onlyRADB 354 56% 64
45.191.16.0/24 Valid Other IRR onlyRADB 128 19% 43
45.191.17.0/24 Valid Other IRR onlyRADB 128 19% 43

AS-SET

AS269658'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 6 are in fix.csv.

  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: RIR45.191.16.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:67e8::/32Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:67e8::/33Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:67e8:8000::/33Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR45.191.16.0/24Route object only in RADB. Add it in the RIR database for the space.128 of 673
Route object: RIR45.191.17.0/24Route object only in RADB. Add it in the RIR database for the space.128 of 673

Route objects not announced

Every route object with origin AS269658 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.