Network · data from 2026-11-12

AS197445 NSC NSC Sh.p.k

Registry name: NSC NSC Sh.p.k, AL · not in PeeringDB

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

6IPv6 routes 100.0% RPKI valid · 16.7% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 5 with no route object for this origin

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

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

Announced routes

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


2001:3800:1a::/48	Valid	Nonecovered by 2001:3800::/29	635 100%	69
2001:3800:8::/48	Valid	Nonecovered by 2001:3800::/29	634 100%	69
2001:3800:c::/48	Valid	Nonecovered by 2001:3800::/29	634 100%	69
2001:3800:d1::/48	Valid	Nonecovered by 2001:3800::/29	634 100%	67
2001:3800:45::/48	Valid	Nonecovered by 2001:3800::/29	605 95%	67
45.141.216.0/24	Valid	RIR databaseRIPE	672 100%	67
2001:3800::/29	Valid	RIR databaseRIPE	605 95%	67

AS-SET

AS197445 isn't in PeeringDB, where networks name their AS-SET.

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.

Route object: none5

Change	Prefix or set	Detail	Full-table peers
Route object: none	2001:3800:1a::/48	No route object for it. A route object for 2001:3800::/29 with origin AS197445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197445 in the RIR database for the space.	635 of 636
Route object: none	2001:3800:8::/48	No route object for it. A route object for 2001:3800::/29 with origin AS197445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197445 in the RIR database for the space.	634 of 636
Route object: none	2001:3800:c::/48	No route object for it. A route object for 2001:3800::/29 with origin AS197445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197445 in the RIR database for the space.	634 of 636
Route object: none	2001:3800:d1::/48	No route object for it. A route object for 2001:3800::/29 with origin AS197445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197445 in the RIR database for the space.	634 of 636
Route object: none	2001:3800:45::/48	No route object for it. A route object for 2001:3800::/29 with origin AS197445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197445 in the RIR database for the space.	605 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2001:3800:1a::/48

No route object for it. A route object for 2001:3800::/29 with origin AS197445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197445 in the RIR database for the space.

635 of 636

Route object: none

2001:3800:8::/48

634 of 636

Route object: none

2001:3800:c::/48

634 of 636

Route object: none

2001:3800:d1::/48

634 of 636

Route object: none

2001:3800:45::/48

605 of 636

Route objects not announced

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