bgpreport

Network · data from 2026-11-12

AS132168 ESUN TECHNOLOGY INTERNATIONAL

Registry name: ESUNHK-AS-AP - ESUN TECHNOLOGY INTERNATIONAL CO., LIMITED, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132168, 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.
2401:d640::/32 Valid None 635 100% 67
202.160.143.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 67
103.204.73.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.160.142.0/23 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
202.160.142.0/24 Valid Other IRR onlyNTTCOM, RADB 670 100% 67
103.204.72.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
202.160.140.0/23 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
202.160.141.0/24 Valid Other IRR onlyNTTCOM, RADB 669 99% 67
103.204.72.0/23 Valid Other IRR onlyNTTCOM, RADB 668 99% 67
103.204.74.0/23 Valid Other IRR onlyNTTCOM, RADB 668 99% 67
103.204.74.0/24 Valid Other IRR onlyNTTCOM, RADB 668 99% 67
103.204.75.0/24 Valid Other IRR onlyNTTCOM, RADB 668 99% 67
202.160.140.0/24 Valid Other IRR onlyNTTCOM, RADB 668 99% 67
202.160.140.0/22 Valid Other IRR onlyNTTCOM, RADB 656 97% 67
45.114.236.0/23 Valid RIR databaseAPNIC 673 100% 67
45.114.238.0/23 Valid RIR databaseAPNIC 673 100% 67
103.90.51.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
45.114.236.0/24 Valid RIR databaseAPNIC 672 100% 67
45.114.237.0/24 Valid RIR databaseAPNIC 672 100% 67
45.114.239.0/24 Valid RIR databaseAPNIC 672 100% 67
45.114.236.0/22 Valid RIR databaseAPNIC 671 100% 67
103.71.24.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
45.114.238.0/24 Valid RIR databaseAPNIC 663 99% 67

AS-SET

PeeringDB's irr_as_set for AS132168: AS-ESUN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS132168 isn't in the set, or no route object for AS132168 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS132168 in itNot covered
AS-ESUN APNIC 3150 Yes 1

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 18 are in fix.csv.

  • Route object: none1
  • Route object: RIR13
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2401:d640::/32No route object for it. Add a route object with origin AS132168 in the RIR database for the space.635 of 636
Route object: RIR202.160.143.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.204.73.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.160.142.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR202.160.142.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.204.72.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR202.160.140.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR202.160.141.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.204.72.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR103.204.74.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR103.204.74.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR103.204.75.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR202.160.140.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR202.160.140.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.656 of 673

Route objects not announced

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

103.90.56.0/23APNICValid
103.90.56.0/24APNIC, NTTCOM, RADBValid
103.90.57.0/24APNIC, NTTCOM, RADBValid
103.204.72.0/22NTTCOM, 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.