Network · data from 2026-11-12
AS150901 NEXTPAY-VN - NEXTPAY DIGITAL TRANSFORMATION GROUP JOINT STOCK COMPANY
Registry name: NEXTPAY-VN - NEXTPAY DIGITAL TRANSFORMATION GROUP JOINT STOCK COMPANY, VN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150901, 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.77.244.40/32 | Invalid: maxLength | Nonecovered by 103.77.244.0/24 | 4 1%low visibility |
| 103.77.244.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
AS150901 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 2 are in fix.csv.
- ROA: maxLength1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.77.244.40/32 | ROA 103.77.244.0/24 AS150901 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 103.77.244.40/32. |
| Route object: none | 103.77.244.40/32 | No route object for it. A route object for 103.77.244.0/24 with origin AS150901 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS150901 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS150901 is announced.
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.