Network · data from 2026-11-12
AS38524 Laxo Global Akses
Registry name: LAXONET-AS-ID - Laxo Global Akses, PT, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38524, 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.191.153.0/24 | Valid | Nonecovered by 103.191.152.0/23 | 673 100% |
| 103.191.152.0/24 | Valid | Nonecovered by 103.191.152.0/23 | 255 38% |
| 103.38.100.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.2.46.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 673 100% |
| 103.38.100.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 103.38.101.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 103.38.102.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 103.38.103.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.40.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.41.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.42.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.43.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.44.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.45.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 119.2.47.0/24 | Valid | Other IRR onlyNTTCOM, RADB, REACH | 35 5%low visibility |
| 2401:de80::/32 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 103.191.152.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 119.2.40.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS38524: AS38524:AS-LAXONET-ID. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS38524 isn't in the set, or no route object for AS38524 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS38524 in it | Not covered |
|---|---|---|---|---|---|
| AS38524:AS-LAXONET-ID | RADB | 10 | 1 | Yes | 0 |
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.
- Route object: none2
- Route object: RIR14
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.191.153.0/24 | No route object for it. A route object for 103.191.152.0/23 with origin AS38524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38524 in the RIR database for the space. |
| Route object: none | 103.191.152.0/24 | No route object for it. A route object for 103.191.152.0/23 with origin AS38524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38524 in the RIR database for the space. |
| Route object: RIR | 103.38.100.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.46.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.38.100.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.38.101.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.38.102.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.38.103.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.40.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.41.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.42.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.43.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.44.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.45.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.47.0/24 | Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 2401:de80::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38524 whose prefix no peer sees AS38524 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.250.100.0/22 | NTTCOM | No ROA |
| 45.250.100.0/23 | NTTCOM, RADB | No ROA |
| 45.250.102.0/23 | NTTCOM, RADB | No ROA |
| 103.38.100.0/23 | NTTCOM, RADB | Valid |
| 103.38.102.0/23 | NTTCOM, RADB | Valid |
| 119.2.40.0/22 | NTTCOM, RADB | Valid |
| 119.2.40.0/23 | NTTCOM, RADB | Valid |
| 119.2.42.0/23 | NTTCOM, RADB | Valid |
| 119.2.44.0/22 | NTTCOM, RADB | Valid |
| 119.2.44.0/23 | NTTCOM, RADB | Valid |
| 119.2.46.0/23 | NTTCOM, RADB | Valid |
| 202.180.43.0/24 | NTTCOM, RADB | No ROA |
| 202.180.48.0/21 | RADB | No ROA |
| 202.180.50.0/23 | RADB | No ROA |
| 202.180.52.0/22 | RADB | No ROA |
| 202.180.52.0/23 | RADB | No ROA |
| 202.180.54.0/23 | RADB | No ROA |
| 202.180.56.0/23 | NTTCOM, RADB | No ROA |
| 202.180.56.0/24 | NTTCOM, RADB | No ROA |
| 202.180.57.0/24 | NTTCOM, RADB | No ROA |
| 2401:de80:a::/48 | RADB | Valid |
| 2401:de80:b::/48 | RADB | Valid |
| 2401:de80:c::/48 | RADB | Valid |
| 2401:de80:d::/48 | RADB | 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.