Network · data from 2026-11-12

AS203779 Nordfiber

Registry name: Nordfiber NORDFIBER AS, NO · PeeringDB

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

5IPv6 routes 100.0% RPKI valid · 80.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

2Route objects not announced registered with origin AS203779, seen from no peer

Announced routes

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


2a06:b040:8000::/33	Valid	Nonecovered by 2a06:b040::/32	350 55%	64
2.58.24.0/23	Valid	RIR databaseRIPE	673 100%	67
185.124.52.0/22	Valid	RIR databaseRIPE	673 100%	67
185.124.52.0/23	Valid	RIR databaseRIPE	673 100%	67
2.58.24.0/24	Valid	RIR databaseRIPE	671 100%	66
2.58.25.0/24	Valid	RIR databaseRIPE	671 100%	67
185.124.53.0/24	Valid	RIR databaseRIPE	671 100%	67
2a06:b046::/32	Valid	RIR databaseRIPE	635 100%	67
2a06:b040::/32	Valid	RIR databaseRIPE	634 100%	67
2a06:b047::/32	Valid	RIR databaseRIPE	634 100%	67
2a06:b040::/29	Valid	RIR databaseRIPE	633 100%	67

AS-SET

PeeringDB's irr_as_set for AS203779: RIPE::AS-NORDFIBER. 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 (AS203779 isn't in the set, or no route object for AS203779 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	AS203779 in it	Not covered
RIPE::AS-NORDFIBER	RIPElists itself further down	7	2	96	Yes	0

Name

Database

ASNs

Sets

Route objects

AS203779 in it

Not covered

RIPE::AS-NORDFIBER

RIPElists itself further down

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

Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a06:b040:8000::/33	No route object for it. A route object for 2a06:b040::/32 with origin AS203779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203779 in the RIR database for the space.	350 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a06:b040:8000::/33

No route object for it. A route object for 2a06:b040::/32 with origin AS203779 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203779 in the RIR database for the space.

350 of 636

Route objects not announced

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


185.124.52.0/24	RIPE	Valid
2a00:ea0::/29	RIPE	Invalid: origin

185.124.52.0/24

RIPE

Valid

2a00:ea0::/29

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.