Network · data from 2026-11-12
AS138538 VPSOR-GLOBAL
Registry name: NANBIAN-VPSORGLOBAL-AS - VPSOR-GLOBAL, CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138538, 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.153.139.237/32 | Invalid: maxLength | Nonecovered by 103.153.139.0/24 | 0 0%low visibility |
| 103.99.40.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.113.92.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.132.234.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.133.176.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.140.228.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.145.38.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.150.181.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.151.216.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.152.170.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.153.36.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.153.100.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.153.138.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 103.155.110.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 2402:b940::/40 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 605 95% |
| 2402:b940:200::/39 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 605 95% |
AS-SET
AS138538'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 43 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced41
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.153.139.237/32 | ROA 103.153.138.0/23 AS138538 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.153.139.237/32. |
| Route object: none | 103.153.139.237/32 | No route object for it. A route object for 103.153.139.0/24 with origin AS138538 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS138538 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138538 whose prefix no peer sees AS138538 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.99.40.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.99.41.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.113.92.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.113.92.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.113.93.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.113.94.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.113.94.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.113.95.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.132.234.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.132.235.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.133.176.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.133.176.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.133.177.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.133.178.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.133.178.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.133.179.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.140.228.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.140.229.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.145.38.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.145.39.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.151.216.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.151.217.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.152.132.0/23 | NTTCOM, RADB | No ROA |
| 103.152.132.0/24 | NTTCOM, RADB | No ROA |
| 103.152.133.0/24 | NTTCOM, RADB | No ROA |
| 103.152.170.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.152.171.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.153.36.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.153.37.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.153.100.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.153.101.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.153.138.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.153.139.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.155.110.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.155.111.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.155.120.0/23 | NTTCOM, RADB | No ROA |
| 103.155.120.0/24 | NTTCOM, RADB | No ROA |
| 103.155.121.0/24 | NTTCOM, RADB | No ROA |
| 103.157.138.0/23 | NTTCOM, RADB | No ROA |
| 103.157.138.0/24 | NTTCOM, RADB | No ROA |
| 103.157.139.0/24 | NTTCOM, RADB | No ROA |
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.