Network · data from 2026-11-12
AS55313 Hanel Communication JSC
Registry name: HANELCOM-AS-VN - Hanel Communication JSC, VN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55313, 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.2.220.0/24 | No ROA | Other origin only | 671 100% |
| 103.2.221.0/24 | No ROA | Other origin only | 671 100% |
| 103.2.222.0/24 | No ROA | Other origin only | 671 100% |
| 103.2.223.0/24 | No ROA | Other origin only | 671 100% |
| 27.118.18.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 45.126.92.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 45.126.92.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 45.126.93.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.245.148.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 27.118.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 27.118.16.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 27.118.16.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.17.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.19.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.20.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.21.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.22.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.23.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.24.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.25.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 27.118.26.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.27.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 27.118.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 45.126.95.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.245.149.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 45.126.94.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2400:9bc0::/32 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 635 100% |
| 2400:9bc0::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2400:9bc0:1::/48 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 2400:9bc0:2::/48 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 2400:9bc0:3::/48 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 634 100% |
| 27.118.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 1 0%low visibility |
AS-SET
AS55313'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 29 are in fix.csv.
- ROA: none4
- Route object: none4
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.2.220.0/24 | No ROA covers it. Add a ROA for AS55313, maxLength 24. |
| Route object: none | 103.2.220.0/24 | Route objects for it name AS9304, AS24088, AS45899, AS56145. Add a route object with origin AS55313 in the RIR database for the space. |
| ROA: none | 103.2.221.0/24 | No ROA covers it. Add a ROA for AS55313, maxLength 24. |
| Route object: none | 103.2.221.0/24 | Route objects for it name AS9304, AS24088, AS56145. Add a route object with origin AS55313 in the RIR database for the space. |
| ROA: none | 103.2.222.0/24 | No ROA covers it. Add a ROA for AS55313, maxLength 24. |
| Route object: none | 103.2.222.0/24 | Route objects for it name AS9304, AS24088, AS56145. Add a route object with origin AS55313 in the RIR database for the space. |
| ROA: none | 103.2.223.0/24 | No ROA covers it. Add a ROA for AS55313, maxLength 24. |
| Route object: none | 103.2.223.0/24 | Route objects for it name AS9304, AS24088, AS56145. Add a route object with origin AS55313 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55313 whose prefix no peer sees AS55313 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 27.118.16.0/21 | APNIC | Valid |
| 27.118.16.0/22 | APNIC, RADB | Valid |
| 27.118.16.0/23 | APNIC | Valid |
| 27.118.18.0/23 | APNIC | Valid |
| 27.118.20.0/22 | APNIC | Valid |
| 27.118.20.0/23 | APNIC, RADB | Valid |
| 27.118.22.0/23 | APNIC | Valid |
| 27.118.24.0/21 | APNIC, RADB | Valid |
| 27.118.24.0/22 | APNIC | Valid |
| 27.118.24.0/23 | APNIC | Valid |
| 27.118.26.0/23 | APNIC | Valid |
| 27.118.28.0/22 | APNIC | Valid |
| 27.118.28.0/23 | APNIC | Valid |
| 27.118.30.0/23 | APNIC | Valid |
| 45.126.92.0/23 | APNIC | Valid |
| 45.126.94.0/23 | APNIC | Valid |
| 103.245.148.0/23 | APNIC, NTTCOM | Valid |
| 103.245.148.0/24 | APNIC, NTTCOM | Valid |
| 103.245.150.0/23 | APNIC, NTTCOM | Valid |
| 103.245.150.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.245.151.0/24 | APNIC, NTTCOM | Valid |
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.