bgpreport

Network · data from 2026-11-12

AS396502 HOTSPOTPR BROADBAND INTERNET

Registry name: HOTSPOTPR - HOTSPOTPR BROADBAND INTERNET, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS396502, 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.
66.248.228.0/22 No ROA RIR databaseARIN 671 100% 68
161.129.76.0/22 No ROA RIR databaseARIN, RADB 671 100% 68
23.172.64.0/24 Valid RIR databaseARIN, RADB 671 100% 68
66.248.228.0/24 Valid RIR databaseARIN 671 100% 68
66.248.229.0/24 Valid RIR databaseARIN 671 100% 68
161.129.78.0/24 Valid RIR databaseARIN 671 100% 68
161.129.79.0/24 Valid RIR databaseARIN 671 100% 68
208.68.40.0/24 Valid RIR databaseARIN 671 100% 68
208.68.41.0/24 Valid RIR databaseARIN 671 100% 68
23.172.65.0/24 Valid RIR databaseARIN, RADB 667 99% 68
66.248.230.0/24 Valid RIR databaseARIN, RADB 667 99% 68
66.248.231.0/24 Valid RIR databaseARIN, RADB 667 99% 68
161.129.76.0/24 Valid RIR databaseARIN, RADB 667 99% 68
161.129.77.0/24 Valid RIR databaseARIN, RADB 667 99% 68
208.68.42.0/24 Valid RIR databaseARIN 667 99% 68
208.68.43.0/24 Valid RIR databaseARIN 667 99% 68
2602:fe96::/38 Valid RIR databaseARIN, RADB 635 100% 69
2602:fe96:400::/38 Valid RIR databaseARIN, RADB 631 99% 69
2602:fe96:800::/38 Valid RIR databaseARIN, RADB 631 99% 69
2602:fe96:c00::/39 Valid RIR databaseARIN, RADB 631 99% 69
2602:fe96:e00::/39 Valid RIR databaseARIN, RADB 631 99% 69

AS-SET

AS396502'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 4 are in fix.csv.

  • ROA: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none66.248.228.0/22No ROA covers it. Add a ROA for AS396502, maxLength 22.671 of 673
ROA: none161.129.76.0/22No ROA covers it. Add a ROA for AS396502, maxLength 22.671 of 673

Route objects not announced

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

2602:fe96::/36ARINValid
2602:fe96:f000::/36RADBNo 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.