Network · data from 2026-11-12
AS151858 INTERDIGI-VN - INTERDIGI JOINT STOCK COMPANY
Registry name: INTERDIGI-VN - INTERDIGI JOINT STOCK COMPANY, VN · not in PeeringDB
33IPv4 routes
81.8% RPKI valid · 81.8% with a route object
5IPv6 routes
80.0% RPKI valid · 80.0% with a route object
5RPKI invalid
0 origin · 5 maxLength
2No ROA
7 with no route object for this origin
11Low visibility
seen by under 10% of full-table peers
31Route objects not announced
registered with origin AS151858, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS151858, 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.20.96.241/32 | Invalid: maxLength | Nonecovered by 103.20.96.0/23 | 4 1%low visibility |
| 103.20.96.251/32 | Invalid: maxLength | Nonecovered by 103.20.96.0/23 | 4 1%low visibility |
| 160.191.89.2/32 | Invalid: maxLength | Nonecovered by 160.191.88.0/23 | 4 1%low visibility |
| 160.191.89.24/32 | Invalid: maxLength | Nonecovered by 160.191.88.0/23 | 4 1%low visibility |
| 160.191.89.25/32 | Invalid: maxLength | Nonecovered by 160.191.88.0/23 | 4 1%low visibility |
| 161.248.82.0/23 | No ROA | None | 672 100% |
| 2001:df4:da40::/48 | No ROA | None | 1 0%low visibility |
| 103.171.90.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.175.249.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.180.136.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.180.140.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.182.22.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.245.236.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.106.104.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.106.105.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.118.28.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.173.226.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.175.248.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.186.64.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.187.146.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 157.10.52.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 157.20.82.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 160.25.166.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 36.50.176.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.20.96.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.167.88.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.195.236.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.195.238.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 160.191.88.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 163.52.144.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 36.50.54.0/23 | Valid | RIR databaseAPNIC | 668 99% |
| 2401:2b20::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2407:f140::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 103.75.180.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 103.75.182.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 103.195.236.0/22 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 2400:6ea0::/48 | Valid | RIR databaseAPNIC | 1 0%low visibility |
| 2401:8260::/48 | Valid | RIR databaseAPNIC | 1 0%low visibility |
AS-SET
AS151858 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 45 are in fix.csv.
- ROA: maxLength5
- ROA: none2
- Route object: none7
- Route object: not announced31
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.20.96.241/32 | ROA 103.20.96.0/23 AS151858 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.20.96.241/32. |
| Route object: none | 103.20.96.241/32 | No route object for it. A route object for 103.20.96.0/23 with origin AS151858 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS151858 in the RIR database for the space. |
| ROA: maxLength | 103.20.96.251/32 | ROA 103.20.96.0/23 AS151858 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.20.96.251/32. |
| Route object: none | 103.20.96.251/32 | No route object for it. A route object for 103.20.96.0/23 with origin AS151858 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS151858 in the RIR database for the space. |
| ROA: maxLength | 160.191.89.2/32 | ROA 160.191.88.0/23 AS151858 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 160.191.89.2/32. |
| Route object: none | 160.191.89.2/32 | No route object for it. A route object for 160.191.88.0/23 with origin AS151858 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS151858 in the RIR database for the space. |
| ROA: maxLength | 160.191.89.24/32 | ROA 160.191.88.0/23 AS151858 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 160.191.89.24/32. |
| Route object: none | 160.191.89.24/32 | No route object for it. A route object for 160.191.88.0/23 with origin AS151858 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS151858 in the RIR database for the space. |
| ROA: maxLength | 160.191.89.25/32 | ROA 160.191.88.0/23 AS151858 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 160.191.89.25/32. |
| Route object: none | 160.191.89.25/32 | No route object for it. A route object for 160.191.88.0/23 with origin AS151858 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS151858 in the RIR database for the space. |
| ROA: none | 161.248.82.0/23 | No ROA covers it. Add a ROA for AS151858, maxLength 23. |
| Route object: none | 161.248.82.0/23 | No route object for it. Add a route object with origin AS151858 in the RIR database for the space. |
| ROA: none | 2001:df4:da40::/48 | No ROA covers it. Add a ROA for AS151858, maxLength 48. |
| Route object: none | 2001:df4:da40::/48 | No route object for it. Add a route object with origin AS151858 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS151858 whose prefix no peer sees AS151858 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.14.48.0/23 | APNIC | Valid |
| 103.20.102.0/23 | APNIC | Valid |
| 103.75.180.0/22 | APNIC | Valid |
| 103.77.208.0/23 | APNIC | Valid |
| 103.106.104.0/23 | APNIC | Valid |
| 103.116.8.0/23 | APNIC | Valid |
| 103.169.34.0/23 | APNIC | Valid |
| 103.169.34.0/24 | APNIC | Valid |
| 103.169.35.0/24 | APNIC | Valid |
| 103.175.248.0/23 | APNIC | Valid |
| 103.188.166.0/23 | APNIC | Valid |
| 103.240.6.0/23 | APNIC | Valid |
| 160.191.86.0/23 | APNIC | Valid |
| 160.250.180.0/23 | APNIC | Valid |
| 202.158.248.0/23 | APNIC | Valid |
| 2001:df3:53c0::/48 | APNIC | Valid |
| 2001:df4:e40::/48 | APNIC | Valid |
| 2001:df4:5740::/48 | APNIC | Valid |
| 2001:df4:7dc0::/48 | APNIC | Valid |
| 2001:df7:79c0::/48 | APNIC | Valid |
| 2400:1da0::/48 | APNIC | Valid |
| 2400:82a0::/32 | APNIC | Valid |
| 2400:e6e0::/48 | APNIC | Valid |
| 2400:eea0::/48 | APNIC | Valid |
| 2401:1e60::/48 | APNIC | Valid |
| 2401:4120::/48 | APNIC | Valid |
| 2401:44e0::/48 | APNIC | Valid |
| 2401:4660::/48 | APNIC | Valid |
| 2401:5ce0::/48 | APNIC | Valid |
| 2407:66c0::/48 | APNIC | Valid |
| 2407:9940::/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.