bgpreport

Network · data from 2026-11-12

AS151786 HPLink COLO

Registry name: HPLINKINTERNET-AS-AP - HPLink, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS151786, 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.
103.67.63.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.213.221.0/24 Invalid: origin Other origin only 2 0%low visibility 3
160.25.7.0/24 No ROA None 672 100% 68
103.72.65.0/24 No ROA Other origin only 2 0%low visibility 3
2400:ac20:3000::/36 No ROA None 1 0%low visibility 1
2400:ac20:4000::/36 No ROA None 1 0%low visibility 1
2400:ac20:5000::/36 No ROA None 1 0%low visibility 1
103.146.37.0/24 Valid RIR databaseAPNIC 672 100% 67
160.191.212.0/24 Valid RIR databaseAPNIC 672 100% 67
220.152.115.0/24 Valid RIR databaseAPNIC 6 1%low visibility 5

AS-SET

AS151786'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: origin2
  • ROA: none5
  • Route object: none7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin103.67.63.0/24ROAs covering it name AS137526, AS151968, not AS151786. If AS151786 should announce it, add a ROA for AS151786.2 of 673
Route object: none103.67.63.0/24Route objects for it name AS137526. Add a route object with origin AS151786 in the RIR database for the space.2 of 673
ROA: origin103.213.221.0/24ROAs covering it name AS137453, not AS151786. If AS151786 should announce it, add a ROA for AS151786.2 of 673
Route object: none103.213.221.0/24Route objects for it name AS137453. Add a route object with origin AS151786 in the RIR database for the space.2 of 673
ROA: none160.25.7.0/24No ROA covers it. Add a ROA for AS151786, maxLength 24.672 of 673
Route object: none160.25.7.0/24No route object for it. Add a route object with origin AS151786 in the RIR database for the space.672 of 673
ROA: none103.72.65.0/24No ROA covers it. Add a ROA for AS151786, maxLength 24.2 of 673
Route object: none103.72.65.0/24Route objects for it name AS55501. Add a route object with origin AS151786 in the RIR database for the space.2 of 673
ROA: none2400:ac20:3000::/36No ROA covers it. Add a ROA for AS151786, maxLength 36.1 of 636
Route object: none2400:ac20:3000::/36No route object for it. Add a route object with origin AS151786 in the RIR database for the space.1 of 636
ROA: none2400:ac20:4000::/36No ROA covers it. Add a ROA for AS151786, maxLength 36.1 of 636
Route object: none2400:ac20:4000::/36No route object for it. Add a route object with origin AS151786 in the RIR database for the space.1 of 636
ROA: none2400:ac20:5000::/36No ROA covers it. Add a ROA for AS151786, maxLength 36.1 of 636
Route object: none2400:ac20:5000::/36No route object for it. Add a route object with origin AS151786 in the RIR database for the space.1 of 636

Route objects not announced

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

103.7.4.0/24APNICValid
2a13:9500:d8::/48RADB, RIPEValid

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.