asn.dev

Internet exchange

Staclar Internet Exchange

active Frankfurt, Germany FRA

Recorded members 22 addresses on file
Connected ports 9 across all participants
Peak traffic Not reported no figure on file
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
Frankfurt, Germany
Region
Europe
Airport code
FRA
Status
Active

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
185.1.180.0/24IPv4Active9
2001:7f8:fd::/64IPv6Active9

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

22 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
AS6939Hurricane Electric LLC185.1.180.13as6939.stacix.netOpen
AS6939Hurricane Electric LLC2001:7f8:fd::13as6939.stacix.netOpen
AS34927iFog GmbH2001:7f8:fd::17as34927.stacix.netOpen
AS34927iFog GmbH185.1.180.17as34927.stacix.netOpen
AS42WoodyNet, Inc.2001:7f8:fd::15as42.stacix.netOpen
AS42WoodyNet, Inc.185.1.180.15as42.stacix.netOpen
AS212508Lowhosting services of Davide Gennari185.1.180.23Open
AS212508Lowhosting services of Davide Gennari2001:7f8:fd::23Open
AS25394MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG2001:7f8:fd::19as25394.stacix.netOpen
AS25394MK Netzdienste Verwaltungs GmbH trading as MK Netzdienste GmbH & Co. KG185.1.180.19as25394.stacix.netOpen
AS3856Packet Clearing House, Inc.2001:7f8:fd::16as3856.stacix.netOpen
AS3856Packet Clearing House, Inc.185.1.180.16as3856.stacix.netOpen
AS41051Openfactory GmbH in Liquidation185.1.180.5as41051.stacix.net
AS207960AS207960 Cyfyngedig185.1.180.18as207960.stacix.netOpen
AS207960AS207960 Cyfyngedig2001:7f8:fd::18as207960.stacix.netOpen
AS57183iFog GmbH185.1.180.14as57183.stacix.net
AS61020RIPE NETWORK COORDINATION CENTRE2001:7f8:fd::100Open
AS61020RIPE NETWORK COORDINATION CENTRE185.1.180.100Open
AS61020RIPE NETWORK COORDINATION CENTRE2001:7f8:fd::1Open
AS61020RIPE NETWORK COORDINATION CENTRE185.1.180.1Open
AS213189RIPE NETWORK COORDINATION CENTRE185.1.180.11Open
AS213189RIPE NETWORK COORDINATION CENTRE2001:7f8:fd::11Open

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-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 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.