bgpreport

Network · data from 2026-11-12

AS63689 ESUNNET - Esun Technology(Shanghai) Co.,Ltd

Registry name: ESUNNET - Esun Technology(Shanghai) Co.,Ltd, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63689, 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.204.72.0/22 Valid Other origin only 672 100% 67
2402:1440::/39 Valid None 635 100% 67
2402:1440::/48 Valid None 635 100% 67
2402:1440::/32 Valid None 61 10%low visibility 37
2402:1440:30::/48 Valid None 61 10%low visibility 37
202.160.140.0/22 Valid Other origin only 15 2%low visibility 14
202.160.141.0/24 Valid Other origin only 4 1%low visibility 7
103.204.72.0/23 Valid Other origin only 3 0%low visibility 5
103.204.72.0/24 Valid Other origin only 3 0%low visibility 5
103.204.73.0/24 Valid Other origin only 3 0%low visibility 5
103.204.74.0/23 Valid Other origin only 3 0%low visibility 5
103.204.74.0/24 Valid Other origin only 3 0%low visibility 5
103.204.75.0/24 Valid Other origin only 3 0%low visibility 5
202.160.140.0/23 Valid Other origin only 3 0%low visibility 5
202.160.140.0/24 Valid Other origin only 3 0%low visibility 5
202.160.142.0/23 Valid Other origin only 3 0%low visibility 5
202.160.142.0/24 Valid Other origin only 2 0%low visibility 2
202.160.143.0/24 Valid Other origin only 1 0%low visibility 4
103.90.56.0/23 Valid RIR databaseAPNIC 672 100% 67
103.90.56.0/24 Valid RIR databaseAPNIC 5 1%low visibility 6
103.90.57.0/24 Valid RIR databaseAPNIC 5 1%low visibility 6

AS-SET

AS63689 isn't in PeeringDB, where networks name their 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 27 are in fix.csv.

  • Route object: none18
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none103.204.72.0/22Route objects for it name AS4837, AS132168. Add a route object with origin AS63689 in the RIR database for the space.672 of 673
Route object: none2402:1440::/39No route object for it. Add a route object with origin AS63689 in the RIR database for the space.635 of 636
Route object: none2402:1440::/48No route object for it. Add a route object with origin AS63689 in the RIR database for the space.635 of 636
Route object: none2402:1440::/32No route object for it. Add a route object with origin AS63689 in the RIR database for the space.61 of 636
Route object: none2402:1440:30::/48No route object for it. Add a route object with origin AS63689 in the RIR database for the space.61 of 636
Route object: none202.160.140.0/22Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.15 of 673
Route object: none202.160.141.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.4 of 673
Route object: none103.204.72.0/23Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none103.204.72.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none103.204.73.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none103.204.74.0/23Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none103.204.74.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none103.204.75.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none202.160.140.0/23Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none202.160.140.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none202.160.142.0/23Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.3 of 673
Route object: none202.160.142.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.2 of 673
Route object: none202.160.143.0/24Route objects for it name AS132168. Add a route object with origin AS63689 in the RIR database for the space.1 of 673

Route objects not announced

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

45.114.236.0/22APNICValid
45.114.236.0/23APNICValid
45.114.236.0/24APNICValid
45.114.237.0/24APNICValid
45.114.238.0/23APNICValid
45.114.238.0/24APNICValid
45.114.239.0/24APNICValid
103.71.24.0/24APNICValid
103.90.51.0/24APNICValid

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.