Network · data from 2026-11-12
AS205122 PLANISWARE US
Registry name: planisware2 Planisware SA, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205122, 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.
| 45.92.54.0/24 | Valid | Nonecovered by 45.92.52.0/22 | 671 100% |
| 2a0a:f742::/32 | Valid | None | 636 100% |
| 2a0a:f742:12::/48 | Valid | None | 636 100% |
| 2a0a:f742:13::/48 | Valid | None | 636 100% |
| 2a0a:f742:18::/48 | Valid | None | 636 100% |
| 2a0a:f742:19::/48 | Valid | None | 636 100% |
| 45.92.52.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.92.52.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.92.53.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS205122: AS205122:AS-PLANISWARE-US. 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 (AS205122 isn't in the set, or no route object for AS205122 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 | AS205122 in it | Not covered |
|---|---|---|---|---|---|
| AS205122:AS-PLANISWARE-US | RIPE | 1 | 1 | Yes | 5 |
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 6 are in fix.csv.
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.92.54.0/24 | No route object for it. A route object for 45.92.52.0/22 with origin AS205122 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205122 in the RIR database for the space. |
| Route object: none | 2a0a:f742::/32 | No route object for it. Add a route object with origin AS205122 in the RIR database for the space. |
| Route object: none | 2a0a:f742:12::/48 | No route object for it. Add a route object with origin AS205122 in the RIR database for the space. |
| Route object: none | 2a0a:f742:13::/48 | No route object for it. Add a route object with origin AS205122 in the RIR database for the space. |
| Route object: none | 2a0a:f742:18::/48 | No route object for it. Add a route object with origin AS205122 in the RIR database for the space. |
| Route object: none | 2a0a:f742:19::/48 | No route object for it. Add a route object with origin AS205122 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS205122 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.