asn.dev

Internet exchange

Dresden Internet Exchange

active Dresden, Germany DRS

Recorded members 27 addresses on file
Connected ports 12 across all participants
Peak traffic 1.8 Mbps peak, as recorded
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Dresden, Germany
Region
Europe
Airport code
DRS
Status
Active
PCH record updated
2026-08-08

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
193.201.151.64/26IPv4Active12
2001:7f8:79::/64IPv6Active11

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

27 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS42WoodyNet, Inc.2001:7f8:79::2a:1pch.c2.peer.dd-ix.netOpen
AS42WoodyNet, Inc.193.201.151.77pch.c2.peer.dd-ix.netOpen
AS9136Wobcom GmbH2001:7f8:79::23b0:1wobcom.c2.peer.dd-ix.netOpen
AS9136Wobcom GmbH193.201.151.81wobcom.c2.peer.dd-ix.netOpen
AS16097HL komm Telekommunikations GmbH193.201.151.75hlkomm.cc.peer.dd-ix.net
AS16097HL komm Telekommunikations GmbH2001:7f8:79::3ee1:1
AS3856Packet Clearing House, Inc.193.201.151.78pchas3856.c2.peer.dd-ix.netOpen
AS3856Packet Clearing House, Inc.2001:7f8:79::1f0:1pchas3856.c2.peer.dd-ix.netOpen
AS112DNS-OARC193.201.151.70dnsoarc112.c2.peer.dd-ix.netOpen
AS112DNS-OARC2001:7f8:79::70:1dnsoarc112.c2.peer.dd-ix.netOpen
AS62365SachsenGigaBit GmbH193.201.151.73sgb.cc.peer.dd-ix.netSelective
AS62365SachsenGigaBit GmbH2001:7f8:79::f39d:1sgb.cc.peer.dd-ix.netSelective
AS16205DSI GmbH Daten Service Informationssysteme2001:7f8:79::3f4d:1dsinet.cc.peer.dd-ix.netOpen
AS16205DSI GmbH Daten Service Informationssysteme193.201.151.72dsinet.cc.peer.dd-ix.netOpen
AS15372IBH connect GmbH193.201.151.71ibh.c2.peer.dd-ix.netOpen
AS15372IBH connect GmbH193.201.151.91ibh.cc.peer.dd-ix.netOpen
AS15372IBH connect GmbH2001:7f8:79::3c0c:1ibh.c2.peer.dd-ix.netOpen
AS15372IBH connect GmbH2001:7f8:79::3c0c:3ibh.cc.peer.dd-ix.netOpen
AS213973BCIX Management GmbH2001:7f8:79::3:43d5:1bcix-or.c2.peer.dd-ix.netSelective
AS213973BCIX Management GmbH193.201.151.76bcix-or.c2.peer.dd-ix.netSelective
AS203592CLOUD & HEAT Technologies GmbH2001:7f8:79::3:1b48:1cnh.c2.peer.dd-ix.netOpen
AS203592CLOUD & HEAT Technologies GmbH193.201.151.80cnh.c2.peer.dd-ix.netOpen
AS208508Landeshauptstadt Dresden, EB IT Dienstleistungen Dresden193.201.151.79lhdd.c2.peer.dd-ix.netOpen
AS57328BCIX MGMT G.M.B.H.193.201.151.65ddix.cc.peer.dd-ix.netOpen
AS57328BCIX MGMT G.M.B.H.2001:7f8:79::dff0:2ddix.c2.peer.dd-ix.netOpen
AS57328BCIX MGMT G.M.B.H.2001:7f8:79::dff0:1ddix.cc.peer.dd-ix.netOpen
AS57328BCIX MGMT G.M.B.H.193.201.151.66ddix.c2.peer.dd-ix.netOpen

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.