Network · data from 2026-11-12
AS402020 AS402020 Planisys
Registry name: ASN-PLANISYS - Planisys Corp, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402020, 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.
| 131.108.40.0/24 | Valid | Other origin onlycovered by 131.108.40.0/22 | 667 99% |
| 131.108.41.0/24 | Valid | Other origin onlycovered by 131.108.40.0/22 | 667 99% |
| 131.108.42.0/24 | Valid | Other origin onlycovered by 131.108.40.0/22 | 667 99% |
| 131.108.43.0/24 | Valid | Other origin onlycovered by 131.108.40.0/22 | 667 99% |
| 179.63.248.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.63.249.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.63.250.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.63.251.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 185.180.8.0/22 | Valid | Other IRR onlyRADB | 667 99% |
| 190.185.104.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.185.105.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.185.106.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 190.185.107.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 194.34.167.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 38.83.73.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 154.57.159.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 209.127.217.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 2604:22e0::/32 | Valid | RIR databaseARIN, RADB | 631 99% |
| 2803:bc00::/32 | Valid | RIR databaseLACNIC, RADB | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS402020: AS40202. 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 (AS402020 isn't in the set, or no route object for AS402020 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 | AS402020 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS40202 | A single AS number, not a set: AS40202, 3 route objects. | |||||
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 17 are in fix.csv.
- Route object: none4
- Route object: RIR10
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.108.40.0/24 | Route objects for it name AS52438. A route object for 131.108.40.0/22 with origin AS402020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402020 in the RIR database for the space. |
| Route object: none | 131.108.41.0/24 | Route objects for it name AS52438. A route object for 131.108.40.0/22 with origin AS402020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402020 in the RIR database for the space. |
| Route object: none | 131.108.42.0/24 | Route objects for it name AS52438. A route object for 131.108.40.0/22 with origin AS402020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402020 in the RIR database for the space. |
| Route object: none | 131.108.43.0/24 | Route objects for it name AS52438. A route object for 131.108.40.0/22 with origin AS402020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402020 in the RIR database for the space. |
| Route object: RIR | 179.63.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.63.249.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.63.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.63.251.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 185.180.8.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.185.104.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.185.105.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.185.106.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.185.107.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.34.167.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402020 whose prefix no peer sees AS402020 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.108.40.0/22 | LACNIC | Valid |
| 179.63.248.0/22 | LACNIC | Valid |
| 190.185.104.0/22 | LACNIC | 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.