bgpreport

Network · data from 2026-11-12

AS147293 Nearoute AS147293

Registry name: NEAROUTE-AS-AP - Nearoute Limited., HK · PeeringDB

17IPv4 routes 88.2% RPKI valid · 70.6% with a route object
5IPv6 routes 80.0% RPKI valid · 80.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
2No ROA 6 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS147293, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS147293, 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.62.168.0/24 Invalid: origin Other origin onlycovered by 45.62.168.0/23 1 0%low visibility 1
154.64.227.0/24 No ROA Other origin only 671 100% 67
2400:8a20:128::/48 No ROA None 631 99% 68
185.113.66.0/24 Valid Nonecovered by 185.113.66.0/23 673 100% 67
185.113.67.0/24 Valid Nonecovered by 185.113.66.0/23 673 100% 67
45.146.232.0/24 Valid Nonecovered by 45.146.232.0/23 2 0%low visibility 2
104.234.20.0/24 Valid Other IRR onlyRADB 671 100% 67
178.214.220.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.146.232.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
46.20.109.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.22.78.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
88.80.139.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
89.43.141.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
141.11.22.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
141.98.75.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
151.243.20.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
87.76.185.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
2400:8a20:120::/48 Valid RIR databaseAPNIC 636 100% 69
2400:8a20:121::/48 Valid RIR databaseAPNIC 636 100% 69
2400:8a20:122::/48 Valid RIR databaseAPNIC 636 100% 69
2407:d840:40::/48 Valid RIR databaseAPNIC 636 100% 69
104.234.176.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS147293'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 23 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin45.62.168.0/24ROAs covering it name AS270168, not AS147293. If AS147293 should announce it, add a ROA for AS147293.1 of 673
Route object: none45.62.168.0/24Route objects for it name AS270168. A route object for 45.62.168.0/23 with origin AS147293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147293 in the RIR database for the space.1 of 673
ROA: none154.64.227.0/24No ROA covers it. Add a ROA for AS147293, maxLength 24.671 of 673
Route object: none154.64.227.0/24Route objects for it name AS51847. Add a route object with origin AS147293 in the RIR database for the space.671 of 673
ROA: none2400:8a20:128::/48No ROA covers it. Add a ROA for AS147293, maxLength 48.631 of 636
Route object: none2400:8a20:128::/48No route object for it. Add a route object with origin AS147293 in the RIR database for the space.631 of 636
Route object: none185.113.66.0/24No route object for it. A route object for 185.113.66.0/23 with origin AS147293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147293 in the RIR database for the space.673 of 673
Route object: none185.113.67.0/24No route object for it. A route object for 185.113.66.0/23 with origin AS147293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147293 in the RIR database for the space.673 of 673
Route object: none45.146.232.0/24No route object for it. A route object for 45.146.232.0/23 with origin AS147293 covers it (filters allowing more-specifics accept it). Add a route object with origin AS147293 in the RIR database for the space.2 of 673
Route object: RIR104.234.20.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

38.207.140.0/24RADBNo ROA
45.62.168.0/23ARINNo ROA
87.76.202.0/24RADB, RIPEValid
103.172.183.0/24APNIC, RADBValid
109.121.33.0/24RADB, RIPEValid
146.19.174.0/24RADB, RIPEValid
154.64.226.0/24RADBNo ROA
185.113.66.0/23RADB, RIPEValid
2001:df0:64c0::/48APNIC, RADBValid
2400:8a20:130::/48APNICValid
2407:d840:3::/48APNICValid
2407:d840:41::/48APNICValid
2407:d840:42::/48APNICValid

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.