Network · data from 2026-11-12

AS38930 FiberRing

Registry name: FIBERRING LeaseWeb Network B.V., NL · PeeringDB

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

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

1Route objects not announced registered with origin AS38930, seen from no peer

Announced routes

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


87.255.32.0/19	Valid	RIR databaseRIPE	673 100%	67
87.255.33.0/24	Valid	RIR databaseRIPE	672 100%	67
87.255.62.0/23	Valid	RIR databaseRIPE	672 100%	67
185.175.4.0/22	Valid	RIR databaseRIPE	672 100%	67
217.194.16.0/24	Valid	RIR databaseRIPE	672 100%	67
217.194.20.0/24	Valid	RIR databaseRIPE	672 100%	67
2a00:ec8::/32	Valid	RIR databaseRIPE	636 100%	67
2a00:ec8:c00::/44	Valid	RIR databaseRIPE	636 100%	67

AS-SET

PeeringDB's irr_as_set for AS38930: AS-FIBERRING. 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 (AS38930 isn't in the set, or no route object for AS38930 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	AS38930 in it	Not covered
AS-FIBERRING	RIPElists itself further down4 member sets in no database: AS-IQIP, AS-PHOENIXNAP, AS214988:AS-MCCLOUD, AS41996:AS-THVMH	266	93	7,067	Yes	0

Name

Database

ASNs

Sets

Route objects

AS38930 in it

Not covered

AS-FIBERRING

RIPElists itself further down4 member sets in no database: AS-IQIP, AS-PHOENIXNAP, AS214988:AS-MCCLOUD, AS41996:AS-THVMH

266

7,067

Yes

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

AS-SET: missing member4
Route object: not announced1

Change	Prefix or set	Detail
AS-SET: missing member	AS-FIBERRING	AS-FIBERRING (RIPE) lists AS-IQIP; no IRR database read has it.
AS-SET: missing member	AS-FIBERRING	AS-FIBERRING (RIPE) lists AS-PHOENIXNAP; no IRR database read has it.
AS-SET: missing member	AS-FIBERRING	AS-FIBERRING (RIPE) lists AS214988:AS-MCCLOUD; no IRR database read has it.
AS-SET: missing member	AS-FIBERRING	AS-FIBERRING (RIPE) lists AS41996:AS-THVMH; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

AS-SET: missing member

AS-FIBERRING

AS-FIBERRING (RIPE) lists AS-IQIP; no IRR database read has it.

AS-SET: missing member

AS-FIBERRING

AS-FIBERRING (RIPE) lists AS-PHOENIXNAP; no IRR database read has it.

AS-SET: missing member

AS-FIBERRING

AS-FIBERRING (RIPE) lists AS214988:AS-MCCLOUD; no IRR database read has it.

AS-SET: missing member

AS-FIBERRING

AS-FIBERRING (RIPE) lists AS41996:AS-THVMH; no IRR database read has it.

Route objects not announced

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


91.224.122.0/23	RIPE	Invalid: origin

91.224.122.0/23

RIPE

Invalid: origin

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.