Network · data from 2026-11-12

AS34373 XXLnet XXLnet B.V.

Registry name: XXLnet XXLnet B.V., NL · not in PeeringDB

22IPv4 routes 100.0% RPKI valid · 95.5% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

8Route objects not announced registered with origin AS34373, seen from no peer

Announced routes

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


185.82.153.0/24	Valid	Nonecovered by 185.82.152.0/23	673 100%	67
37.143.36.0/23	Valid	RIR databaseRIPE	673 100%	66
37.143.36.0/24	Valid	RIR databaseRIPE	673 100%	66
37.143.37.0/24	Valid	RIR databaseRIPE	673 100%	66
45.128.64.0/22	Valid	RIR databaseRIPE	673 100%	66
45.132.40.0/22	Valid	RIR databaseRIPE	673 100%	66
77.74.124.0/22	Valid	RIR databaseRADB, RIPE	673 100%	66
86.48.68.0/22	Valid	RIR databaseRIPE	673 100%	66
87.239.15.0/24	Valid	RIR databaseRIPE	673 100%	67
91.219.76.0/22	Valid	RIR databaseRIPE	673 100%	66
185.56.52.0/22	Valid	RIR databaseRIPE	673 100%	66
185.63.56.0/22	Valid	RIR databaseRIPE	673 100%	66
185.69.204.0/22	Valid	RIR databaseRIPE	673 100%	66
185.82.152.0/23	Valid	RIR databaseRIPE	673 100%	66
185.96.44.0/22	Valid	RIR databaseRIPE	673 100%	66
185.97.228.0/22	Valid	RIR databaseRIPE	673 100%	66
185.116.40.0/22	Valid	RIR databaseRIPE	673 100%	66
185.165.68.0/22	Valid	RIR databaseRIPE	673 100%	66
185.210.128.0/22	Valid	RIR databaseRIPE	673 100%	66
193.105.233.0/24	Valid	RIR databaseRIPE	673 100%	66
195.253.200.0/21	Valid	RIR databaseRIPE	673 100%	67
217.61.253.0/24	Valid	RIR databaseRIPE	673 100%	66
2a00:4140::/29	Valid	RIR databaseRIPE	633 100%	67
2a06:900::/29	Valid	RIR databaseRIPE	633 100%	67
2a06:7bc0::/29	Valid	RIR databaseRIPE	633 100%	67
2a0b:ec00::/29	Valid	RIR databaseRIPE	633 100%	67

AS-SET

AS34373 isn't in PeeringDB, where networks name their AS-SET.

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

Route object: none1
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
Route object: none	185.82.153.0/24	No route object for it. A route object for 185.82.152.0/23 with origin AS34373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34373 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

185.82.153.0/24

No route object for it. A route object for 185.82.152.0/23 with origin AS34373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34373 in the RIR database for the space.

673 of 673

Route objects not announced

Route objects with origin AS34373 whose prefix no peer sees AS34373 announce. Many are kept on purpose (backup routes, space announced only in some places).


93.190.186.0/24	RIPE	No ROA
185.116.40.0/23	RIPE	Valid
185.116.42.0/23	RIPE	Valid
185.171.163.0/24	RIPE	Valid
2a02:5160::/32	RIPE	No ROA
2a06:900::/36	RIPE	Valid
2a06:900:1000::/36	RIPE	Valid
2a0b:57c0:1000::/36	RIPE	Valid

93.190.186.0/24

RIPE

No ROA

185.116.40.0/23

RIPE

Valid

185.116.42.0/23

RIPE

Valid

185.171.163.0/24

RIPE

Valid

2a02:5160::/32

RIPE

No ROA

2a06:900::/36

RIPE

Valid

2a06:900:1000::/36

RIPE

Valid

2a0b:57c0:1000::/36

RIPE

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.