Network · data from 2026-11-12

AS197288 NORLYS-DIGITAL Norlys Telco A/S

Registry name: NORLYS-DIGITAL Norlys Telco A/S, DK · not in PeeringDB

7IPv4 routes 14.3% RPKI valid · 14.3% with a route object

5IPv6 routes 20.0% RPKI valid · 20.0% with a route object

9RPKI invalid 9 origin · 0 maxLength

1No ROA 10 with no route object for this origin

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

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

Announced routes

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


89.184.137.64/27	Invalid: origin	None	1 0%low visibility	1
89.184.137.94/32	Invalid: origin	None	1 0%low visibility	1
89.184.137.96/27	Invalid: origin	None	1 0%low visibility	1
89.184.140.252/32	Invalid: origin	None	1 0%low visibility	1
212.10.40.0/24	Invalid: origin	None	1 0%low visibility	1
2a03:7405:100::/40	Invalid: origin	None	1 0%low visibility	1
2a03:7405:300::/40	Invalid: origin	None	1 0%low visibility	1
2a03:7405:f000:101::/64	Invalid: origin	None	1 0%low visibility	1
2a03:7405:f000:103::/64	Invalid: origin	None	1 0%low visibility	1
100.71.252.252/32 bogon	No ROA	None	1 0%low visibility	1
85.27.172.0/24	Valid	RIR databaseRIPE	671 100%	67
2a13:8a07::/32	Valid	RIR databaseRIPE	630 99%	67

89.184.137.64/27

Invalid: origin

None

1 0%low visibility

89.184.137.94/32

Invalid: origin

None

1 0%low visibility

89.184.137.96/27

Invalid: origin

None

1 0%low visibility

89.184.140.252/32

Invalid: origin

None

1 0%low visibility

212.10.40.0/24

Invalid: origin

None

1 0%low visibility

2a03:7405:100::/40

Invalid: origin

None

1 0%low visibility

2a03:7405:300::/40

Invalid: origin

None

1 0%low visibility

2a03:7405:f000:101::/64

Invalid: origin

None

1 0%low visibility

2a03:7405:f000:103::/64

Invalid: origin

None

1 0%low visibility

100.71.252.252/32 bogon

No ROA

None

1 0%low visibility

85.27.172.0/24

Valid

RIR databaseRIPE

671 100%

2a13:8a07::/32

Valid

RIR databaseRIPE

630 99%

AS-SET

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

ROA: origin9
Bogon prefix1
Route object: none9

Change	Prefix or set	Detail	Full-table peers
ROA: origin	89.184.137.64/27	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 673
Route object: none	89.184.137.64/27	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 673
ROA: origin	89.184.137.94/32	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 673
Route object: none	89.184.137.94/32	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 673
ROA: origin	89.184.137.96/27	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 673
Route object: none	89.184.137.96/27	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 673
ROA: origin	89.184.140.252/32	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 673
Route object: none	89.184.140.252/32	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 673
ROA: origin	212.10.40.0/24	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 673
Route object: none	212.10.40.0/24	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 673
ROA: origin	2a03:7405:100::/40	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 636
Route object: none	2a03:7405:100::/40	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 636
ROA: origin	2a03:7405:300::/40	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 636
Route object: none	2a03:7405:300::/40	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 636
ROA: origin	2a03:7405:f000:101::/64	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 636
Route object: none	2a03:7405:f000:101::/64	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 636
ROA: origin	2a03:7405:f000:103::/64	ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.	1 of 636
Route object: none	2a03:7405:f000:103::/64	No route object for it. Add a route object with origin AS197288 in the RIR database for the space.	1 of 636
Bogon prefix	100.71.252.252/32	In IANA's special-purpose registry: Shared Address Space (RFC 6598).	1 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

89.184.137.64/27

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 673

Route object: none

89.184.137.64/27

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 673

ROA: origin

89.184.137.94/32

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 673

Route object: none

89.184.137.94/32

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 673

ROA: origin

89.184.137.96/27

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 673

Route object: none

89.184.137.96/27

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 673

ROA: origin

89.184.140.252/32

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 673

Route object: none

89.184.140.252/32

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 673

ROA: origin

212.10.40.0/24

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 673

Route object: none

212.10.40.0/24

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 673

ROA: origin

2a03:7405:100::/40

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 636

Route object: none

2a03:7405:100::/40

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 636

ROA: origin

2a03:7405:300::/40

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 636

Route object: none

2a03:7405:300::/40

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 636

ROA: origin

2a03:7405:f000:101::/64

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 636

Route object: none

2a03:7405:f000:101::/64

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 636

ROA: origin

2a03:7405:f000:103::/64

ROAs covering it name AS39642, not AS197288. If AS197288 should announce it, add a ROA for AS197288.

1 of 636

Route object: none

2a03:7405:f000:103::/64

No route object for it. Add a route object with origin AS197288 in the RIR database for the space.

1 of 636

Bogon prefix

100.71.252.252/32

In IANA's special-purpose registry: Shared Address Space (RFC 6598).

1 of 673

Route objects not announced

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