Network · data from 2026-11-12

AS25693 VIRMACH

Registry name: VIRMACH - Virtual Machine Solutions LLC, US · PeeringDB

24IPv4 routes 95.8% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS25693, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25693, 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.


8.43.33.0/24	No ROA	Other IRR onlyALTDB, RADB	668 99%	67
59.152.124.0/22	Valid	RIR databaseRIPE	673 100%	67
85.8.149.0/24	Valid	RIR databaseRIPE	673 100%	67
85.8.151.0/24	Valid	RIR databaseRIPE	673 100%	67
172.98.13.0/24	Valid	RIR databaseARIN	673 100%	67
172.98.14.0/24	Valid	RIR databaseARIN	673 100%	67
185.118.133.0/24	Valid	RIR databaseRIPE	673 100%	67
185.118.134.0/24	Valid	RIR databaseRIPE	673 100%	67
185.147.156.0/24	Valid	RIR databaseRIPE	673 100%	67
185.147.158.0/24	Valid	RIR databaseRIPE	673 100%	67
185.213.17.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.143.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.241.0/24	Valid	RIR databaseRIPE	673 100%	67
185.214.242.0/24	Valid	RIR databaseRIPE	673 100%	67
62.3.10.0/24	Valid	RIR databaseRIPE	672 100%	67
62.106.64.0/24	Valid	RIR databaseRIPE	672 100%	67
62.192.173.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
85.209.17.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
89.33.192.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
91.242.232.0/24	Valid	RIR databaseRIPE	672 100%	67
146.19.197.0/24	Valid	RIR databaseRIPE	672 100%	67
23.136.108.0/24	Valid	RIR databaseALTDB, ARIN, RADB	668 99%	67
172.98.15.0/24	Valid	RIR databaseALTDB, ARIN, RADB	668 99%	67
193.58.147.0/24	Valid	RIR databaseALTDB, RADB, RIPE	668 99%	67
2602:f6b0::/40	Valid	RIR databaseALTDB, ARIN, RADB	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS25693: AS25693:AS-CONE. 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 (AS25693 isn't in the set, or no route object for AS25693 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	Route objects	AS25693 in it
AS25693:AS-CONE	RADB	1	1	25	Yes
	ALTDB (also)	1	1	25	Yes
	ARIN (also)	1	1	25	Yes

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 2 are in fix.csv.

ROA: none1
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	8.43.33.0/24	No ROA covers it. Add a ROA for AS25693, maxLength 24.	668 of 673
Route object: RIR	8.43.33.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	668 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

8.43.33.0/24

No ROA covers it. Add a ROA for AS25693, maxLength 24.

668 of 673

Route object: RIR

8.43.33.0/24

Route object only in ALTDB, RADB. Add it in the RIR database for the space.

668 of 673

Route objects not announced

Every route object with origin AS25693 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.