Network · data from 2026-11-12

AS47178 Soluzioni Potenza

Registry name: SOLPOT-AS Soluzioni Potenza Srl, IT · PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.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 2 with no route object for this origin

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

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

Announced routes

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


93.188.119.0/24	Valid	Nonecovered by 93.188.112.0/21	673 100%	67
185.99.227.0/24	Valid	Nonecovered by 185.99.224.0/22	671 100%	67
185.99.224.0/22	Valid	RIR databaseRIPE	673 100%	67
93.188.112.0/21	Valid	RIR databaseRIPE	672 100%	67
2a05:ba80::/29	Valid	RIR databaseRIPE	635 100%	67

AS-SET

AS47178's PeeringDB record names no 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 10 are in fix.csv.

Route object: none2
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
Route object: none	93.188.119.0/24	No route object for it. A route object for 93.188.112.0/21 with origin AS47178 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47178 in the RIR database for the space.	673 of 673
Route object: none	185.99.227.0/24	No route object for it. A route object for 185.99.224.0/22 with origin AS47178 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47178 in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

93.188.119.0/24

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

673 of 673

Route object: none

185.99.227.0/24

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

671 of 673

Route objects not announced

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


2a05:ba80::/32	RIPE	Valid
2a05:ba81::/32	RIPE	Valid
2a05:ba82::/32	RIPE	Valid
2a05:ba83::/32	RIPE	Valid
2a05:ba84::/32	RIPE	Valid
2a05:ba85::/32	RIPE	Valid
2a05:ba86::/32	RIPE	Valid
2a05:ba87::/32	RIPE	Valid

2a05:ba80::/32

RIPE

Valid

2a05:ba81::/32

RIPE

Valid

2a05:ba82::/32

RIPE

Valid

2a05:ba83::/32

RIPE

Valid

2a05:ba84::/32

RIPE

Valid

2a05:ba85::/32

RIPE

Valid

2a05:ba86::/32

RIPE

Valid

2a05:ba87::/32

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.