Network · data from 2026-11-12
AS63737 VIETSERVER-AS-VN - VIETSERVER SERVICES TECHNOLOGY COMPANY LIMITED
Registry name: VIETSERVER-AS-VN - VIETSERVER SERVICES TECHNOLOGY COMPANY LIMITED, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63737, 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.232.52.240/32 | Invalid: maxLength | Nonecovered by 103.232.52.0/22 | 4 1%low visibility |
| 103.232.53.3/32 | Invalid: maxLength | Nonecovered by 103.232.52.0/22 | 4 1%low visibility |
| 103.15.94.3/32 | Invalid: maxLength | Nonecovered by 103.15.94.0/23 | 0 0%low visibility |
| 103.39.124.104/32 | Invalid: maxLength | Nonecovered by 103.39.124.0/23 | 0 0%low visibility |
| 103.74.103.52/32 | Invalid: maxLength | Nonecovered by 103.74.103.0/24 | 0 0%low visibility |
| 103.140.250.3/32 | Invalid: maxLength | Nonecovered by 103.140.250.0/23 | 0 0%low visibility |
| 103.140.251.3/32 | Invalid: maxLength | Nonecovered by 103.140.250.0/23 | 0 0%low visibility |
| 103.149.136.3/32 | Invalid: maxLength | Nonecovered by 103.149.136.0/23 | 0 0%low visibility |
| 103.149.137.86/32 | Invalid: maxLength | Nonecovered by 103.149.136.0/23 | 0 0%low visibility |
| 103.14.154.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.14.224.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.15.94.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.30.10.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.39.124.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.57.128.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.57.130.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.122.140.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.140.250.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.149.136.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.209.60.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.231.248.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.253.22.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 144.79.12.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 157.10.48.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 157.10.50.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 157.66.156.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 157.66.158.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 160.25.168.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 160.25.234.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 160.30.204.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 36.50.52.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 42.96.10.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.74.104.0/22 | Valid | RIR databaseAPNIC | 669 99% |
| 103.167.84.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.167.90.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.167.92.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.170.254.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.171.0.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.176.110.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.176.112.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.177.108.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.180.150.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.180.152.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.182.18.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.183.114.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.183.118.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.186.66.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.187.4.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.190.80.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 103.232.52.0/22 | Valid | RIR databaseAPNIC, RADB | 669 99% |
| 160.25.76.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 202.55.132.0/22 | Valid | RIR databaseAPNIC, RADB | 669 99% |
AS-SET
AS63737 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 40 are in fix.csv.
- ROA: maxLength9
- Route object: none9
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.232.52.240/32 | ROA 103.232.52.0/22 AS63737 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 103.232.52.240/32. |
| Route object: none | 103.232.52.240/32 | No route object for it. A route object for 103.232.52.0/22 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.232.53.3/32 | ROA 103.232.52.0/22 AS63737 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 103.232.53.3/32. |
| Route object: none | 103.232.53.3/32 | No route object for it. A route object for 103.232.52.0/22 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.15.94.3/32 | ROA 103.15.94.0/23 AS63737 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.15.94.3/32. |
| Route object: none | 103.15.94.3/32 | No route object for it. A route object for 103.15.94.0/23 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.39.124.104/32 | ROA 103.39.124.0/23 AS63737 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.39.124.104/32. |
| Route object: none | 103.39.124.104/32 | No route object for it. A route object for 103.39.124.0/23 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.74.103.52/32 | ROA 103.74.100.0/22 AS63737 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.74.103.52/32. |
| Route object: none | 103.74.103.52/32 | No route object for it. A route object for 103.74.103.0/24 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.140.250.3/32 | ROA 103.140.250.0/23 AS63737 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.140.250.3/32. |
| Route object: none | 103.140.250.3/32 | No route object for it. A route object for 103.140.250.0/23 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.140.251.3/32 | ROA 103.140.250.0/23 AS63737 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.140.251.3/32. |
| Route object: none | 103.140.251.3/32 | No route object for it. A route object for 103.140.250.0/23 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.149.136.3/32 | ROA 103.149.136.0/23 AS63737 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.149.136.3/32. |
| Route object: none | 103.149.136.3/32 | No route object for it. A route object for 103.149.136.0/23 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
| ROA: maxLength | 103.149.137.86/32 | ROA 103.149.136.0/23 AS63737 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 103.149.137.86/32. |
| Route object: none | 103.149.137.86/32 | No route object for it. A route object for 103.149.136.0/23 with origin AS63737 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS63737 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63737 whose prefix no peer sees AS63737 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.57.130.0/24 | APNIC | Valid |
| 103.57.131.0/24 | APNIC | Valid |
| 103.74.100.0/22 | APNIC, RADB | Valid |
| 103.74.100.0/23 | APNIC | Valid |
| 103.74.100.0/24 | APNIC | Valid |
| 103.74.101.0/24 | APNIC | Valid |
| 103.74.102.0/23 | APNIC | Valid |
| 103.74.102.0/24 | APNIC | Valid |
| 103.74.103.0/24 | APNIC | Valid |
| 103.207.36.0/22 | APNIC, NTTCOM | No ROA |
| 103.207.36.0/24 | NTTCOM | No ROA |
| 103.207.37.0/24 | NTTCOM | No ROA |
| 103.207.38.0/24 | NTTCOM | No ROA |
| 103.207.39.0/24 | NTTCOM | No ROA |
| 103.253.22.0/24 | APNIC | Valid |
| 103.253.23.0/24 | APNIC | Valid |
| 144.79.12.0/24 | APNIC | Valid |
| 144.79.13.0/24 | APNIC | Valid |
| 160.25.168.0/24 | APNIC | Valid |
| 160.25.169.0/24 | APNIC | Valid |
| 160.30.204.0/24 | APNIC | Valid |
| 160.30.205.0/24 | 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.