bgpreport

Network · data from 2026-11-12

AS42034 DN-SYSTEMS DN-Systems Enterprise Internet Solutions GmbH

Registry name: DN-SYSTEMS DN-Systems Enterprise Internet Solutions GmbH, DE · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% 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
1Route objects not announced registered with origin AS42034, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42034, 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.
45.135.105.0/24 No ROA RIR databaseRIPE 670 100% 67
2a0e:6b40:10::/48 No ROA RIR databaseRIPE 627 99% 67
185.135.32.0/22 Valid RIR databaseRIPE 671 100% 67
193.108.181.0/24 Valid RIR databaseRIPE 671 100% 67
2001:67c:274c::/48 Valid RIR databaseRIPE 627 99% 67
2a06:f140::/29 Valid RIR databaseRIPE 626 98% 67

AS-SET

AS42034 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 3 are in fix.csv.

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.135.105.0/24No ROA covers it. Add a ROA for AS42034, maxLength 24.670 of 673
ROA: none2a0e:6b40:10::/48No ROA covers it. Add a ROA for AS42034, maxLength 48.627 of 636

Route objects not announced

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

77.81.74.0/24RIPENo 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.