Network · data from 2026-11-12
AS140815 HTTVSERVER-VN - HTTVSERVER TECHNOLOGY COMPANY LIMITED
Registry name: HTTVSERVER-VN - HTTVSERVER TECHNOLOGY COMPANY LIMITED, VN · not in PeeringDB
37IPv4 routes
97.3% RPKI valid · 97.3% with a route object
21IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
0 origin · 1 maxLength
0No ROA
1 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
73Route objects not announced
registered with origin AS140815, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS140815, 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.182.16.137/32 | Invalid: maxLength | Nonecovered by 103.182.16.0/24 | 5 1%low visibility |
| 103.6.248.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.10.68.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.16.160.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.16.214.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.16.224.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.29.0.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.29.2.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.131.56.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.170.120.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.182.16.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.184.96.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.186.148.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.189.202.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.190.36.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.190.106.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.196.144.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.250.78.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.253.16.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 113.192.8.0/23 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 157.10.170.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 157.10.196.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 157.10.202.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 157.20.224.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 157.66.162.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 157.66.194.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 157.66.196.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.22.158.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.25.82.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.25.84.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.25.206.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.30.48.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.191.34.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.191.112.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 160.250.62.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 163.61.180.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 203.145.44.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df0:5bc0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df0:aac0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df0:d9c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df0:e3c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df0:eac0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df3:41c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df3:b640::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df3:edc0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:540::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:5c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:11c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:7040::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:8240::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df4:aa40::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:4b20::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:4ba0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:50e0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:7420::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:7560::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:7620::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:8aa0::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS140815 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 75 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced73
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.182.16.137/32 | ROA 103.182.16.0/23 AS140815 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.182.16.137/32. |
| Route object: none | 103.182.16.137/32 | No route object for it. A route object for 103.182.16.0/24 with origin AS140815 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS140815 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140815 whose prefix no peer sees AS140815 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.6.248.0/24 | APNIC | Valid |
| 103.6.249.0/24 | APNIC | Valid |
| 103.10.68.0/24 | APNIC | Valid |
| 103.10.69.0/24 | APNIC | Valid |
| 103.16.160.0/24 | APNIC | Valid |
| 103.16.161.0/24 | APNIC | Valid |
| 103.16.214.0/24 | APNIC | Valid |
| 103.16.215.0/24 | APNIC | Valid |
| 103.16.224.0/24 | APNIC | Valid |
| 103.16.225.0/24 | APNIC | Valid |
| 103.29.0.0/24 | APNIC | Valid |
| 103.29.1.0/24 | APNIC | Valid |
| 103.29.2.0/24 | APNIC | Valid |
| 103.29.3.0/24 | APNIC | Valid |
| 103.131.56.0/24 | APNIC | Valid |
| 103.131.57.0/24 | APNIC | Valid |
| 103.170.120.0/24 | APNIC | Valid |
| 103.170.121.0/24 | APNIC | Valid |
| 103.182.16.0/24 | APNIC | Valid |
| 103.182.17.0/24 | APNIC | Valid |
| 103.184.96.0/24 | APNIC | Valid |
| 103.184.97.0/24 | APNIC | Valid |
| 103.186.148.0/24 | APNIC | Valid |
| 103.186.149.0/24 | APNIC | Valid |
| 103.189.202.0/24 | APNIC | Valid |
| 103.189.203.0/24 | APNIC | Valid |
| 103.190.36.0/24 | APNIC | Valid |
| 103.190.37.0/24 | APNIC | Valid |
| 103.190.106.0/24 | APNIC | Valid |
| 103.190.107.0/24 | APNIC | Valid |
| 103.196.144.0/24 | APNIC | Valid |
| 103.196.145.0/24 | APNIC | Valid |
| 103.250.78.0/24 | APNIC | Valid |
| 103.250.79.0/24 | APNIC | Valid |
| 103.253.16.0/24 | APNIC | Valid |
| 103.253.17.0/24 | APNIC | Valid |
| 113.192.8.0/24 | APNIC | Valid |
| 113.192.9.0/24 | APNIC | Valid |
| 157.10.170.0/24 | APNIC | Valid |
| 157.10.171.0/24 | APNIC | Valid |
| 157.10.196.0/24 | APNIC | Valid |
| 157.10.197.0/24 | APNIC | Valid |
| 157.10.202.0/24 | APNIC | Valid |
| 157.10.203.0/24 | APNIC | Valid |
| 157.20.224.0/24 | APNIC | Valid |
| 157.20.225.0/24 | APNIC | Valid |
| 157.66.162.0/24 | APNIC | Valid |
| 157.66.163.0/24 | APNIC | Valid |
| 157.66.194.0/24 | APNIC | Valid |
| 157.66.195.0/24 | APNIC | Valid |
| 157.66.196.0/24 | APNIC | Valid |
| 157.66.197.0/24 | APNIC | Valid |
| 160.22.158.0/24 | APNIC | Valid |
| 160.22.159.0/24 | APNIC | Valid |
| 160.25.82.0/24 | APNIC | Valid |
| 160.25.83.0/24 | APNIC | Valid |
| 160.25.84.0/24 | APNIC | Valid |
| 160.25.85.0/24 | APNIC | Valid |
| 160.25.206.0/24 | APNIC | Valid |
| 160.25.207.0/24 | APNIC | Valid |
| 160.30.48.0/24 | APNIC | Valid |
| 160.30.49.0/24 | APNIC | Valid |
| 160.191.34.0/24 | APNIC | Valid |
| 160.191.35.0/24 | APNIC | Valid |
| 160.191.112.0/24 | APNIC | Valid |
| 160.191.113.0/24 | APNIC | Valid |
| 160.250.62.0/24 | APNIC | Valid |
| 160.250.63.0/24 | APNIC | Valid |
| 163.61.180.0/24 | APNIC | Valid |
| 163.61.181.0/24 | APNIC | Valid |
| 203.145.44.0/24 | APNIC | Valid |
| 203.145.45.0/24 | APNIC | Valid |
| 2001:df5:1ac0::/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.