Network · data from 2026-11-12
AS206636 dk-eniig-as Norlys a.m.b.a.
Registry name: dk-eniig-as Norlys a.m.b.a., DK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206636, 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.
| 139.45.121.0/24 | Invalid: origin | None | 1 0%low visibility |
| 2a02:25c8:d5f0::/48 | Invalid: origin | None | 1 0%low visibility |
| 185.179.96.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS206636 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 139.45.121.0/24 | ROAs covering it name AS39642, not AS206636. If AS206636 should announce it, add a ROA for AS206636. |
| Route object: none | 139.45.121.0/24 | No route object for it. Add a route object with origin AS206636 in the RIR database for the space. |
| ROA: origin | 2a02:25c8:d5f0::/48 | ROAs covering it name AS39642, not AS206636. If AS206636 should announce it, add a ROA for AS206636. |
| Route object: none | 2a02:25c8:d5f0::/48 | No route object for it. Add a route object with origin AS206636 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS206636 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.