Network · data from 2026-11-12
AS135027 Virtual Platform
Registry name: VIRTUALPLATFORM-AS-AP - Virtualplatform Pty Ltd, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135027, 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.223.184.0/23 | Valid | None | 669 99% |
| 103.223.184.0/24 | Valid | None | 669 99% |
| 151.242.130.0/24 | Valid | Nonecovered by 151.242.130.0/23 | 669 99% |
| 151.242.131.0/24 | Valid | Nonecovered by 151.242.130.0/23 | 669 99% |
| 103.219.62.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
| 103.219.63.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.251.134.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.251.135.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 117.121.243.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 138.252.147.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 123.100.130.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 123.100.131.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 123.100.135.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 123.100.142.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 123.100.153.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 123.100.154.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 151.242.130.0/23 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS135027: AS135027:AS-VP. 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 (AS135027 isn't in the set, or no route object for AS135027 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 | AS135027 in it | Not covered |
|---|---|---|---|---|---|
| AS135027:AS-VP | APNIC | 2 | 1 | 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 20 are in fix.csv.
- Route object: none4
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.223.184.0/23 | No route object for it. Add a route object with origin AS135027 in the RIR database for the space. |
| Route object: none | 103.223.184.0/24 | No route object for it. Add a route object with origin AS135027 in the RIR database for the space. |
| Route object: none | 151.242.130.0/24 | No route object for it. A route object for 151.242.130.0/23 with origin AS135027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135027 in the RIR database for the space. |
| Route object: none | 151.242.131.0/24 | No route object for it. A route object for 151.242.130.0/23 with origin AS135027 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135027 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS135027 whose prefix no peer sees AS135027 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.219.62.0/23 | APNIC, RADB | Valid |
| 103.251.134.0/23 | RADB | No ROA |
| 123.100.128.0/21 | APNIC | Valid |
| 123.100.128.0/22 | APNIC | Valid |
| 123.100.128.0/23 | APNIC | Valid |
| 123.100.128.0/24 | APNIC | Valid |
| 123.100.129.0/24 | APNIC | Valid |
| 123.100.130.0/23 | APNIC | Valid |
| 123.100.132.0/22 | APNIC | Valid |
| 123.100.132.0/23 | APNIC | Valid |
| 123.100.132.0/24 | APNIC | Valid |
| 123.100.133.0/24 | APNIC | Valid |
| 123.100.134.0/23 | APNIC | Valid |
| 123.100.134.0/24 | APNIC | Valid |
| 123.100.154.0/23 | APNIC | Valid |
| 123.100.155.0/24 | APNIC | 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.