Network · data from 2026-11-12
AS59045 SUNHONGS - Guangzhou navigation information technology co., LTD
Registry name: SUNHONGS - Guangzhou navigation information technology co., LTD, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59045, 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.
| 43.231.171.0/24 | Valid | None | 5 1%low visibility |
| 118.191.248.0/24 | Valid | Nonecovered by 118.191.248.0/21 | 5 1%low visibility |
| 118.191.249.0/24 | Valid | Nonecovered by 118.191.248.0/21 | 5 1%low visibility |
| 118.191.250.0/24 | Valid | Nonecovered by 118.191.248.0/21 | 5 1%low visibility |
| 118.191.248.0/22 | Valid | Nonecovered by 118.191.248.0/21 | 2 0%low visibility |
| 43.231.164.0/24 | Valid | None | 1 0%low visibility |
| 43.231.165.0/24 | Valid | None | 1 0%low visibility |
| 43.231.166.0/24 | Valid | None | 1 0%low visibility |
| 118.191.128.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.129.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.130.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.131.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.152.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.192.0/23 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 118.191.208.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.216.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.223.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.224.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.240.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 118.191.241.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
AS59045 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 136 are in fix.csv.
- Route object: none8
- Route object: RIR12
- Route object: not announced116
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 43.231.171.0/24 | No route object for it. Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 118.191.248.0/24 | No route object for it. A route object for 118.191.248.0/21 with origin AS59045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 118.191.249.0/24 | No route object for it. A route object for 118.191.248.0/21 with origin AS59045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 118.191.250.0/24 | No route object for it. A route object for 118.191.248.0/21 with origin AS59045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 118.191.248.0/22 | No route object for it. A route object for 118.191.248.0/21 with origin AS59045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 43.231.164.0/24 | No route object for it. Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 43.231.165.0/24 | No route object for it. Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: none | 43.231.166.0/24 | No route object for it. Add a route object with origin AS59045 in the RIR database for the space. |
| Route object: RIR | 118.191.128.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.129.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.130.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.131.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.152.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.192.0/23 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.208.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.216.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.223.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.224.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.240.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 118.191.241.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59045 whose prefix no peer sees AS59045 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 118.191.128.0/19 | NTTCOM, RADB | No ROA |
| 118.191.128.0/20 | RADB | No ROA |
| 118.191.128.0/21 | RADB | No ROA |
| 118.191.128.0/22 | RADB | No ROA |
| 118.191.128.0/23 | RADB | No ROA |
| 118.191.130.0/23 | RADB | No ROA |
| 118.191.132.0/22 | RADB | No ROA |
| 118.191.132.0/23 | RADB | No ROA |
| 118.191.132.0/24 | NTTCOM, RADB | Valid |
| 118.191.133.0/24 | NTTCOM, RADB | Valid |
| 118.191.134.0/23 | RADB | No ROA |
| 118.191.134.0/24 | NTTCOM, RADB | Valid |
| 118.191.135.0/24 | NTTCOM, RADB | Valid |
| 118.191.136.0/21 | RADB | No ROA |
| 118.191.136.0/22 | RADB | No ROA |
| 118.191.136.0/23 | RADB | No ROA |
| 118.191.136.0/24 | NTTCOM, RADB | Valid |
| 118.191.137.0/24 | NTTCOM, RADB | Valid |
| 118.191.138.0/23 | RADB | No ROA |
| 118.191.138.0/24 | NTTCOM, RADB | Valid |
| 118.191.139.0/24 | NTTCOM, RADB | Valid |
| 118.191.140.0/22 | RADB | No ROA |
| 118.191.140.0/23 | RADB | No ROA |
| 118.191.140.0/24 | NTTCOM, RADB | Valid |
| 118.191.141.0/24 | NTTCOM, RADB | Valid |
| 118.191.142.0/23 | RADB | No ROA |
| 118.191.142.0/24 | NTTCOM, RADB | Valid |
| 118.191.143.0/24 | NTTCOM, RADB | Valid |
| 118.191.144.0/20 | RADB | No ROA |
| 118.191.144.0/21 | RADB | No ROA |
| 118.191.144.0/22 | RADB | No ROA |
| 118.191.144.0/23 | RADB | No ROA |
| 118.191.144.0/24 | NTTCOM, RADB | Valid |
| 118.191.145.0/24 | NTTCOM, RADB | Valid |
| 118.191.146.0/23 | RADB | No ROA |
| 118.191.146.0/24 | NTTCOM, RADB | Valid |
| 118.191.147.0/24 | NTTCOM, RADB | Valid |
| 118.191.148.0/22 | RADB | No ROA |
| 118.191.148.0/23 | RADB | No ROA |
| 118.191.148.0/24 | NTTCOM, RADB | Valid |
| 118.191.149.0/24 | NTTCOM, RADB | Valid |
| 118.191.150.0/23 | RADB | No ROA |
| 118.191.150.0/24 | NTTCOM, RADB | Valid |
| 118.191.151.0/24 | NTTCOM, RADB | Valid |
| 118.191.152.0/21 | RADB | No ROA |
| 118.191.152.0/22 | RADB | No ROA |
| 118.191.152.0/23 | RADB | No ROA |
| 118.191.153.0/24 | NTTCOM, RADB | Valid |
| 118.191.154.0/23 | RADB | No ROA |
| 118.191.154.0/24 | NTTCOM, RADB | Valid |
| 118.191.155.0/24 | NTTCOM, RADB | Valid |
| 118.191.156.0/22 | RADB | No ROA |
| 118.191.156.0/23 | RADB | No ROA |
| 118.191.156.0/24 | NTTCOM, RADB | Valid |
| 118.191.157.0/24 | NTTCOM, RADB | Valid |
| 118.191.158.0/23 | RADB | No ROA |
| 118.191.158.0/24 | NTTCOM, RADB | Valid |
| 118.191.159.0/24 | NTTCOM, RADB | Valid |
| 118.191.216.0/21 | NTTCOM, RADB | No ROA |
| 118.191.216.0/22 | NTTCOM, RADB | No ROA |
| 118.191.216.0/23 | NTTCOM, RADB | No ROA |
| 118.191.217.0/24 | NTTCOM, RADB | Valid |
| 118.191.218.0/23 | NTTCOM, RADB | No ROA |
| 118.191.218.0/24 | NTTCOM, RADB | Valid |
| 118.191.219.0/24 | NTTCOM, RADB | Valid |
| 118.191.220.0/22 | NTTCOM, RADB | No ROA |
| 118.191.220.0/23 | NTTCOM, RADB | No ROA |
| 118.191.220.0/24 | RADB | No ROA |
| 118.191.221.0/24 | RADB | No ROA |
| 118.191.222.0/23 | NTTCOM, RADB | No ROA |
| 118.191.222.0/24 | RADB | No ROA |
| 118.191.224.0/20 | NTTCOM, RADB | No ROA |
| 118.191.224.0/21 | NTTCOM, RADB | No ROA |
| 118.191.224.0/22 | RADB | No ROA |
| 118.191.224.0/23 | RADB | No ROA |
| 118.191.225.0/24 | RADB | No ROA |
| 118.191.226.0/23 | RADB | No ROA |
| 118.191.226.0/24 | RADB | No ROA |
| 118.191.227.0/24 | RADB | No ROA |
| 118.191.228.0/22 | RADB | No ROA |
| 118.191.228.0/23 | RADB | No ROA |
| 118.191.228.0/24 | RADB | No ROA |
| 118.191.229.0/24 | RADB | No ROA |
| 118.191.230.0/23 | RADB | No ROA |
| 118.191.230.0/24 | RADB | No ROA |
| 118.191.231.0/24 | RADB | No ROA |
| 118.191.232.0/21 | RADB | No ROA |
| 118.191.232.0/22 | RADB | No ROA |
| 118.191.232.0/23 | RADB | No ROA |
| 118.191.232.0/24 | RADB | No ROA |
| 118.191.233.0/24 | RADB | No ROA |
| 118.191.234.0/23 | RADB | No ROA |
| 118.191.234.0/24 | RADB | No ROA |
| 118.191.235.0/24 | RADB | No ROA |
| 118.191.236.0/22 | RADB | No ROA |
| 118.191.236.0/23 | RADB | No ROA |
| 118.191.236.0/24 | RADB | No ROA |
| 118.191.237.0/24 | RADB | No ROA |
| 118.191.238.0/23 | RADB | No ROA |
| 118.191.238.0/24 | RADB | No ROA |
| 118.191.239.0/24 | RADB | No ROA |
| 118.191.240.0/21 | NTTCOM, RADB | No ROA |
| 118.191.240.0/22 | NTTCOM, RADB | No ROA |
| 118.191.240.0/23 | NTTCOM, RADB | No ROA |
| 118.191.242.0/23 | NTTCOM, RADB | No ROA |
| 118.191.242.0/24 | NTTCOM, RADB | Valid |
| 118.191.243.0/24 | NTTCOM, RADB | Valid |
| 118.191.244.0/22 | NTTCOM, RADB | No ROA |
| 118.191.244.0/23 | NTTCOM, RADB | No ROA |
| 118.191.244.0/24 | NTTCOM, RADB | Valid |
| 118.191.245.0/24 | NTTCOM, RADB | Valid |
| 118.191.246.0/23 | NTTCOM, RADB | No ROA |
| 118.191.246.0/24 | NTTCOM, RADB | Valid |
| 118.191.247.0/24 | NTTCOM, RADB | Valid |
| 118.191.248.0/21 | NTTCOM | No ROA |
| 2001:df1:6b80::/48 | NTTCOM | No 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.