Network · data from 2026-11-12

AS38915 Solido

Registry name: Solido-AS Solido Gemeenschappelijk Regeling, NL · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

34IPv6 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

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

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

Announced routes

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


178.21.216.0/22	Valid	RIR databaseRIPE	673 100%	66
178.21.220.0/23	Valid	RIR databaseRIPE	673 100%	66
193.203.220.0/23	Valid	RIR databaseRIPE	673 100%	66
194.104.157.0/24	Valid	RIR databaseRIPE	673 100%	66
2a00:1de0::/32	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:1200::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:1998::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19a0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19a8::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19b0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19b8::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19d8::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19e0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19e8::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19f0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:19f8::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3500:1a00::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3502:1040::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3502:1070::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3502:1090::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3502:11d0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3502:11e0::/48	Valid	RIR databaseRIPE	635 100%	67
2a07:3502:11f0::/48	Valid	RIR databaseRIPE	635 100%	67
178.21.222.0/23	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:1201::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:1999::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19b1::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19b9::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19d9::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19e1::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19e9::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19f1::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:19f9::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3500:1a01::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3502:1041::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3502:1071::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3502:1091::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3502:11e1::/48	Valid	RIR databaseRIPE	1 0%low visibility	4
2a07:3502:11f1::/48	Valid	RIR databaseRIPE	1 0%low visibility	4

178.21.216.0/22

Valid

RIR databaseRIPE

673 100%

178.21.220.0/23

Valid

RIR databaseRIPE

673 100%

193.203.220.0/23

Valid

RIR databaseRIPE

673 100%

194.104.157.0/24

Valid

RIR databaseRIPE

673 100%

2a00:1de0::/32

Valid

RIR databaseRIPE

635 100%

2a07:3500:1200::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:1998::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19a0::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19a8::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19b0::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19b8::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19d8::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19e0::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19e8::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19f0::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:19f8::/48

Valid

RIR databaseRIPE

635 100%

2a07:3500:1a00::/48

Valid

RIR databaseRIPE

635 100%

2a07:3502:1040::/48

Valid

RIR databaseRIPE

635 100%

2a07:3502:1070::/48

Valid

RIR databaseRIPE

635 100%

2a07:3502:1090::/48

Valid

RIR databaseRIPE

635 100%

2a07:3502:11d0::/48

Valid

RIR databaseRIPE

635 100%

2a07:3502:11e0::/48

Valid

RIR databaseRIPE

635 100%

2a07:3502:11f0::/48

Valid

RIR databaseRIPE

635 100%

178.21.222.0/23

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:1201::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:1999::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19b1::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19b9::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19d9::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19e1::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19e9::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19f1::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:19f9::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3500:1a01::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3502:1041::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3502:1071::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3502:1091::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3502:11e1::/48

Valid

RIR databaseRIPE

1 0%low visibility

2a07:3502:11f1::/48

Valid

RIR databaseRIPE

1 0%low visibility

AS-SET

PeeringDB's irr_as_set for AS38915: AS38915:AS-SOLIDO-IT. 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 (AS38915 isn't in the set, or no route object for AS38915 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	AS38915 in it	Not covered
AS38915:AS-SOLIDO-IT	RIPE	2	2	42	Yes	0

Name

Database

ASNs

Sets

Route objects

AS38915 in it

Not covered

AS38915:AS-SOLIDO-IT

RIPE

Yes

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 AS38915 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.