Network · data from 2026-11-12

AS210876 SERPAIO Invermae Solutions SL

Registry name: SERPAIO Invermae Solutions SL, ES · not in PeeringDB

16IPv4 routes 100.0% RPKI valid · 87.5% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

5Route objects not announced registered with origin AS210876, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210876, 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.159.76.0/22	Valid	None	673 100%	67
193.57.164.0/23	Valid	None	672 100%	67
45.134.84.0/22	Valid	RIR databaseRIPE	673 100%	67
45.147.116.0/22	Valid	RIR databaseRIPE	673 100%	67
93.189.123.0/24	Valid	RIR databaseRIPE	673 100%	67
109.107.149.0/24	Valid	RIR databaseRIPE	673 100%	67
181.174.184.0/22	Valid	RIR databaseLACNIC	673 100%	67
185.204.102.0/24	Valid	RIR databaseRIPE	673 100%	67
185.247.6.0/24	Valid	RIR databaseRIPE	673 100%	67
194.35.40.0/24	Valid	RIR databaseRIPE	673 100%	67
217.67.161.0/24	Valid	RIR databaseRIPE	673 100%	67
217.67.162.0/23	Valid	RIR databaseRIPE	673 100%	67
217.67.166.0/23	Valid	RIR databaseRIPE	673 100%	67
217.67.168.0/22	Valid	RIR databaseRIPE	673 100%	67
46.226.151.0/24	Valid	RIR databaseRIPE	672 100%	67
193.57.164.0/24	Valid	RIR databaseRIPE	672 100%	67

AS-SET

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

Route object: none2
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	45.159.76.0/22	No route object for it. Add a route object with origin AS210876 in the RIR database for the space.	673 of 673
Route object: none	193.57.164.0/23	No route object for it. Add a route object with origin AS210876 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

45.159.76.0/22

No route object for it. Add a route object with origin AS210876 in the RIR database for the space.

673 of 673

Route object: none

193.57.164.0/23

No route object for it. Add a route object with origin AS210876 in the RIR database for the space.

672 of 673

Route objects not announced

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


45.134.84.0/23	RIPE	Valid
45.159.76.0/24	RIPE	Valid
185.216.30.0/24	RIPE	Valid
185.216.31.0/24	RIPE	Valid
185.226.8.0/24	RIPE	Valid

45.134.84.0/23

RIPE

Valid

45.159.76.0/24

RIPE

Valid

185.216.30.0/24

RIPE

Valid

185.216.31.0/24

RIPE

Valid

185.226.8.0/24

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.