Network · data from 2026-11-12
AS31732 PARSUN NETWORK SOLUTIONS
Registry name: Parsun-Network-Solutions Parsun Network Solutions PTY LTD, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31732, 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.
| 196.3.91.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2001:16c0::/48 | Valid | Nonecovered by 2001:16c0::/32 | 633 100% |
| 2001:16c0::/29 | Valid | None | 632 99% |
| 188.209.155.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.90.100.0/22 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS31732: RIPE::AS-PARSUN. 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 (AS31732 isn't in the set, or no route object for AS31732 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 | AS31732 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-PARSUN | RIPE | 9 | 1 | Yes | 1 |
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 12 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.3.91.0/24 | No ROA covers it. Add a ROA for AS31732, maxLength 24. |
| Route object: RIR | 196.3.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2001:16c0::/48 | No route object for it. A route object for 2001:16c0::/32 with origin AS31732 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31732 in the RIR database for the space. |
| Route object: none | 2001:16c0::/29 | No route object for it. Add a route object with origin AS31732 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31732 whose prefix no peer sees AS31732 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.92.80.0/22 | RIPE | No ROA |
| 82.115.0.0/22 | RADB | No ROA |
| 185.207.196.0/22 | RADB | No ROA |
| 188.209.144.0/21 | RADB | No ROA |
| 2001:16c0::/32 | RIPE | Invalid: maxLength |
| 2001:16c0:2::/48 | RIPE | Invalid: maxLength |
| 2001:16c0:50::/48 | RIPE | Invalid: maxLength |
| 2001:16c0:1234::/48 | RIPE | 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.