Network · data from 2026-11-12
AS151872 EDIGI-VN - CLOUD DATA TECHNOLOGY AND COMMUNICATION COMPANY LIMITED
Registry name: EDIGI-VN - CLOUD DATA TECHNOLOGY AND COMMUNICATION COMPANY LIMITED, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS151872, 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:9920::/48 | No ROA | None | 636 100% |
| 157.66.198.0/23 | No ROA | None | 631 94% |
| 160.30.10.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.30.11.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 192.227.201.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 2001:df3:e4c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df3:e8c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:9760::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS151872 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 21 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2401:9920::/48 | No ROA covers it. Add a ROA for AS151872, maxLength 48. |
| Route object: none | 2401:9920::/48 | No route object for it. Add a route object with origin AS151872 in the RIR database for the space. |
| ROA: none | 157.66.198.0/23 | No ROA covers it. Add a ROA for AS151872, maxLength 23. |
| Route object: none | 157.66.198.0/23 | No route object for it. Add a route object with origin AS151872 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS151872 whose prefix no peer sees AS151872 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 72.14.137.0/24 | ARIN, RADB | Valid |
| 107.173.8.0/24 | ARIN, RADB | Valid |
| 157.66.220.0/24 | APNIC, NTTCOM, RADB | Valid |
| 157.66.221.0/24 | APNIC, NTTCOM, RADB | Valid |
| 160.22.80.0/24 | APNIC | Valid |
| 160.22.81.0/24 | APNIC | Valid |
| 160.22.118.0/24 | APNIC | Valid |
| 160.22.119.0/24 | APNIC | Valid |
| 160.30.22.0/24 | APNIC | Valid |
| 160.30.23.0/24 | APNIC | Valid |
| 212.104.131.0/24 | NTTCOM | No ROA |
| 2001:470:338::/48 | ARIN | Valid |
| 2001:470:48c::/48 | ARIN | Valid |
| 2001:df4:19c0::/48 | APNIC | Valid |
| 2001:df4:1cc0::/48 | APNIC | Valid |
| 2401:8ce0::/48 | APNIC | Valid |
| 2401:9a60::/48 | APNIC | 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.