bgpreport

Network · data from 2026-11-12

AS149502 Nearoute Limited - Hong Kong

Registry name: NEAROUTE-AS-AP - NEAROUTE LIMITED, HK · PeeringDB

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

Announced routes

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

206.237.118.0/24 No ROA None 673 100% 67
38.47.120.0/24 No ROA Other origin only 672 100% 67

AS-SET

AS149502'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 9 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none206.237.118.0/24No ROA covers it. Add a ROA for AS149502, maxLength 24.673 of 673
Route object: none206.237.118.0/24No route object for it. Add a route object with origin AS149502 in the RIR database for the space.673 of 673
ROA: none38.47.120.0/24No ROA covers it. Add a ROA for AS149502, maxLength 24.672 of 673
Route object: none38.47.120.0/24Route objects for it name AS6134, AS51847, AS198100. Add a route object with origin AS149502 in the RIR database for the space.672 of 673

Route objects not announced

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

103.181.12.0/24APNIC, RADBValid
103.181.13.0/24APNIC, RADBValid
141.98.75.0/24RADB, RIPEValid
154.18.170.0/24RADBNo ROA
2407:d840:1::/48APNIC, RADBValid

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.