Network · data from 2026-11-12
AS131630 Lazco Global
Registry name: LAZCO - Lazco Corporation, TW · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131630, 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.
| 2602:f2b1::/40 | Invalid: origin | Other origin only | 1 0%low visibility |
| 2a14:7580:8000::/36 | Invalid: origin | None | 1 0%low visibility |
| 160.30.99.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 151.158.224.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 151.158.224.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 2a0f:85c1:390::/48 | Valid | RIR databaseRADB, RIPE | 636 100% |
| 2402:4f20::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2402:4f20:10::/48 | Valid | RIR databaseAPNIC | 635 100% |
| 2a14:7580:f300::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2402:4f20::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2402:4f20:1::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2402:4f20:3::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2402:4f20:4::/48 | Valid | RIR databaseAPNIC | 633 100% |
| 2402:6420::/32 | Valid | RIR databaseAPNIC | 632 99% |
| 2a14:7580:6000::/36 | Valid | RIR databaseRIPE | 632 99% |
| 162.4.236.0/23 | Valid | RIR databaseAPNIC | 161 24% |
| 103.51.88.0/23 | Valid | RIR databaseAPNIC | 160 24% |
| 103.196.172.0/23 | Valid | RIR databaseAPNIC | 159 24% |
| 202.5.10.0/23 | Valid | RIR databaseAPNIC | 159 24% |
AS-SET
PeeringDB's irr_as_set for AS131630: AS131630:AS-LAZCO. 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 (AS131630 isn't in the set, or no route object for AS131630 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 | AS131630 in it | Not covered |
|---|---|---|---|---|---|
| AS131630:AS-LAZCO | APNIC | 17 | 3 | Yes | 2 |
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 8 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2602:f2b1::/40 | ROAs covering it name AS403050, not AS131630. If AS131630 should announce it, add a ROA for AS131630. |
| Route object: none | 2602:f2b1::/40 | Route objects for it name AS403050. Add a route object with origin AS131630 in the RIR database for the space. |
| ROA: origin | 2a14:7580:8000::/36 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS131630 should announce it, add a ROA for AS131630. |
| Route object: none | 2a14:7580:8000::/36 | No route object for it. Add a route object with origin AS131630 in the RIR database for the space. |
| Route object: RIR | 160.30.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131630 whose prefix no peer sees AS131630 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.130.28.0/22 | RADB | No ROA |
| 151.158.225.0/24 | APNIC | Invalid: maxLength |
| 162.4.236.0/24 | APNIC | Invalid: maxLength |
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.