Network · data from 2026-11-12

AS47605 FNE-Finland Oy

Registry name: FNE-AS FNE-Finland Oy, FI · PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

3Route objects not announced registered with origin AS47605, seen from no peer

Announced routes

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


185.31.68.0/23	No ROA	RIR databaseRIPE	673 100%	66
5.133.104.0/22	Valid	RIR databaseRIPE	673 100%	66
85.194.194.0/23	Valid	RIR databaseRIPE	673 100%	66
85.194.220.0/22	Valid	RIR databaseRIPE	673 100%	66
87.236.152.0/21	Valid	RIR databaseRIPE	673 100%	66
185.38.0.0/22	Valid	RIR databaseRIPE	673 100%	66
62.220.228.0/22	Valid	RIR databaseRIPE	671 100%	67
2a00:1d50::/32	Valid	RIR databaseRIPE	636 100%	67
80.208.240.0/21	Valid	RIR databaseRIPE	396 59%	61

AS-SET

PeeringDB's irr_as_set for AS47605: AS-SET-FNE. 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 (AS47605 isn't in the set, or no route object for AS47605 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	AS47605 in it	Not covered
AS-SET-FNE	RIPE2 member sets in no database: AS209186:AS-DOWNSTREAM, AS51765:AS-CREANOVA	295	40	8,233	Yes	0

Name

Database

ASNs

Sets

Route objects

AS47605 in it

Not covered

AS-SET-FNE

RIPE2 member sets in no database: AS209186:AS-DOWNSTREAM, AS51765:AS-CREANOVA

295

8,233

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

ROA: none1
AS-SET: missing member2
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.31.68.0/23	No ROA covers it. Add a ROA for AS47605, maxLength 23.	673 of 673
AS-SET: missing member	AS-SET-FNE	AS-SET-FNE (RIPE) lists AS209186:AS-DOWNSTREAM; no IRR database read has it.
AS-SET: missing member	AS-SET-FNE	AS-SET-FNE (RIPE) lists AS51765:AS-CREANOVA; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.31.68.0/23

No ROA covers it. Add a ROA for AS47605, maxLength 23.

673 of 673

AS-SET: missing member

AS-SET-FNE

AS-SET-FNE (RIPE) lists AS209186:AS-DOWNSTREAM; no IRR database read has it.

AS-SET: missing member

AS-SET-FNE

AS-SET-FNE (RIPE) lists AS51765:AS-CREANOVA; no IRR database read has it.

Route objects not announced

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


85.194.234.0/23	RIPE	Valid
2a00:1d50:3::/48	RIPE	Valid
2a00:89e0::/32	RIPE	Invalid: origin

85.194.234.0/23

RIPE

Valid

2a00:1d50:3::/48

RIPE

Valid

2a00:89e0::/32

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.