bgpreport

Network · data from 2026-11-12

AS42638 Coreconcept

Registry name: Netvaerkssmeden James Hansen trading as Netvaerkssmeden, DK · PeeringDB

5IPv4 routes 40.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS42638, seen from no peer

Announced routes

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

91.216.14.0/24 No ROA RIR databaseRIPE 671 100% 68
194.50.40.0/24 No ROA RIR databaseRIPE 671 100% 68
194.50.208.0/24 No ROA RIR databaseRIPE 671 100% 68
2001:67c:96c::/48 No ROA RIR databaseRIPE 635 100% 68
91.189.200.0/21 Valid RIR databaseRIPE 671 100% 68
193.104.83.0/24 Valid RIR databaseRIPE 671 100% 68
2a14:bb00::/29 Valid RIR databaseRIPE 632 99% 68

AS-SET

AS42638's PeeringDB record names no 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 6 are in fix.csv.

  • ROA: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none91.216.14.0/24No ROA covers it. Add a ROA for AS42638, maxLength 24.671 of 673
ROA: none194.50.40.0/24No ROA covers it. Add a ROA for AS42638, maxLength 24.671 of 673
ROA: none194.50.208.0/24No ROA covers it. Add a ROA for AS42638, maxLength 24.671 of 673
ROA: none2001:67c:96c::/48No ROA covers it. Add a ROA for AS42638, maxLength 48.635 of 636

Route objects not announced

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

91.216.103.0/24RIPENo ROA
185.157.84.0/22RIPENo ROA

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.