Network · data from 2026-11-12

AS202395 Fiberaccessbolaget i Sverige

Registry name: FAB-NET Fiberaccessbolaget i Sverige AB, SE · PeeringDB

7IPv4 routes 71.4% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

2No ROA 0 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202395, 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.242.208.0/22	No ROA	RIR databaseRIPE	672 100%	66
193.181.47.0/24	No ROA	RIR databaseRIPE	672 100%	66
185.254.80.0/22	Valid	RIR databaseRIPE	672 100%	66
192.165.252.0/24	Valid	RIR databaseRIPE	672 100%	66
193.181.45.0/24	Valid	RIR databaseRIPE	672 100%	66
193.183.224.0/22	Valid	RIR databaseRIPE	672 100%	66
195.226.220.0/24	Valid	RIR databaseRIPE	672 100%	66
2a02:2a48::/32	Valid	RIR databaseRIPE	636 100%	67
2a0b:680::/29	Valid	RIR databaseRIPE	635 100%	67
2a10:dd00::/29	Valid	RIR databaseRIPE	633 100%	67

AS-SET

PeeringDB's irr_as_set for AS202395: AS-ACCESSBOLAGET. 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 (AS202395 isn't in the set, or no route object for AS202395 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	AS202395 in it	Not covered
AS-ACCESSBOLAGET	RIPE1 member set in no database: AS199746:AS-NEXTSERV	241	68	9,007	Yes	0

Name

Database

ASNs

Sets

Route objects

AS202395 in it

Not covered

AS-ACCESSBOLAGET

RIPE1 member set in no database: AS199746:AS-NEXTSERV

241

9,007

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.

ROA: none2
AS-SET: missing member1

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.242.208.0/22	No ROA covers it. Add a ROA for AS202395, maxLength 22.	672 of 673
ROA: none	193.181.47.0/24	No ROA covers it. Add a ROA for AS202395, maxLength 24.	672 of 673
AS-SET: missing member	AS-ACCESSBOLAGET	AS-ACCESSBOLAGET (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.242.208.0/22

No ROA covers it. Add a ROA for AS202395, maxLength 22.

672 of 673

ROA: none

193.181.47.0/24

No ROA covers it. Add a ROA for AS202395, maxLength 24.

672 of 673

AS-SET: missing member

AS-ACCESSBOLAGET

AS-ACCESSBOLAGET (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

Every route object with origin AS202395 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.