Network · data from 2026-11-12

AS203172 Qupra B.V.

Registry name: QUPRA-AS Qupra B.V., NL · PeeringDB

10IPv4 routes 100.0% 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

0No 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 AS203172, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203172, 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.129.144.0/22	Valid	RIR databaseRIPE	673 100%	67
123.253.212.0/23	Valid	RIR databaseRIPE	673 100%	67
185.167.253.0/24	Valid	RIR databaseRIPE	673 100%	67
185.188.143.0/24	Valid	RIR databaseRIPE	673 100%	67
185.249.41.0/24	Valid	RIR databaseRIPE	673 100%	67
185.249.42.0/24	Valid	RIR databaseRIPE	673 100%	67
193.110.153.0/24	Valid	RIR databaseRIPE	673 100%	67
194.87.20.0/23	Valid	RIR databaseRIPE	673 100%	67
194.87.223.0/24	Valid	RIR databaseRIPE	673 100%	67
45.129.147.0/24	Valid	RIR databaseRIPE	672 100%	67
2a0e:5b44::/30	Valid	RIR databaseRIPE	633 100%	67

AS-SET

AS203172's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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