bgpreport

Network · data from 2026-11-12

AS17490 ETFiberNet - 3/F,Yi Qing Building,Hua Jing Xin Cheng,Guangzhou

Registry name: ETFiberNet - 3/F,Yi Qing Building,Hua Jing Xin Cheng,Guangzhou, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17490, 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.
61.28.20.0/24 Valid Nonecovered by 61.28.16.0/20 672 100% 67
61.28.22.0/24 Valid Nonecovered by 61.28.16.0/20 672 100% 67
61.28.49.0/24 Valid Nonecovered by 61.28.48.0/21 672 100% 67
61.28.108.0/24 Valid Nonecovered by 61.28.104.0/21 672 100% 67
2401:9a00:a::/48 Valid None 549 86% 66
2401:9a00:e::/48 Valid None 549 86% 66
2401:9a00::/48 Valid None 548 86% 66
2401:9a00:1::/48 Valid None 548 86% 66
2401:9a00:2::/48 Valid None 548 86% 66
2401:9a00:3::/48 Valid None 548 86% 66
2401:9a00:4::/48 Valid None 548 86% 66
2401:9a00:5::/48 Valid None 548 86% 66
2401:9a00:6::/48 Valid None 548 86% 66
2401:9a00:7::/48 Valid None 548 86% 66
2401:9a00:8::/48 Valid None 548 86% 66
2401:9a00:9::/48 Valid None 548 86% 66
2401:9a00:b::/48 Valid None 548 86% 66
2401:9a00:c::/48 Valid None 548 86% 66
2401:9a00:d::/48 Valid None 548 86% 66
2401:9a00:f::/48 Valid None 548 86% 66
2401:9a00:10::/48 Valid None 548 86% 66
2401:9a00:11::/48 Valid None 548 86% 66
2401:9a00:12::/48 Valid None 548 86% 66
2401:9a00:13::/48 Valid None 548 86% 66

AS-SET

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

  • Route object: none24
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
Route object: none61.28.20.0/24No route object for it. A route object for 61.28.16.0/20 with origin AS17490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17490 in the RIR database for the space.672 of 673
Route object: none61.28.22.0/24No route object for it. A route object for 61.28.16.0/20 with origin AS17490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17490 in the RIR database for the space.672 of 673
Route object: none61.28.49.0/24No route object for it. A route object for 61.28.48.0/21 with origin AS17490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17490 in the RIR database for the space.672 of 673
Route object: none61.28.108.0/24No route object for it. A route object for 61.28.104.0/21 with origin AS17490 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17490 in the RIR database for the space.672 of 673
Route object: none2401:9a00:a::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.549 of 636
Route object: none2401:9a00:e::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.549 of 636
Route object: none2401:9a00::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:1::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:2::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:3::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:4::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:5::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:6::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:7::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:8::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:9::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:b::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:c::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:d::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:f::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:10::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:11::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:12::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636
Route object: none2401:9a00:13::/48No route object for it. Add a route object with origin AS17490 in the RIR database for the space.548 of 636

Route objects not announced

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

61.28.0.0/18NTTCOM, RADBNo ROA
61.28.0.0/20NTTCOM, RADBNo ROA
61.28.0.0/21NTTCOM, RADBNo ROA
61.28.16.0/20NTTCOM, RADBNo ROA
61.28.24.0/22NTTCOM, RADBNo ROA
61.28.28.0/22NTTCOM, RADBNo ROA
61.28.32.0/20NTTCOM, RADBNo ROA
61.28.32.0/22NTTCOM, RADBNo ROA
61.28.36.0/22NTTCOM, RADBNo ROA
61.28.40.0/21NTTCOM, RADBNo ROA
61.28.40.0/22NTTCOM, RADBNo ROA
61.28.48.0/20NTTCOM, RADBNo ROA
61.28.48.0/21NTTCOM, RADBNo ROA
61.28.56.0/21NTTCOM, RADBNo ROA
61.28.64.0/19NTTCOM, RADBNo ROA
61.28.96.0/20NTTCOM, RADBNo ROA
61.28.104.0/21NTTCOM, RADBNo ROA
211.156.32.0/20NTTCOM, RADBNo ROA

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.