asn.dev

Internet exchange

ERA-IX Vienna

active Vienna, Austria

Recorded members 35 addresses on file
Connected ports 15 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
Vienna, Austria
Region
Europe
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
91.213.211.128/26IPv4Active15
2001:7f8:17e::/64IPv6Active15

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

35 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 LLC2001:7f8:17e::136
AS6939Hurricane Electric LLC91.213.211.136
AS13335Cloudflare, Inc.2001:7f8:17e::134
AS13335Cloudflare, Inc.91.213.211.134
AS20764CJSC RASCOM91.213.211.172Selective
AS16276OVH SAS91.213.211.133
AS16276OVH SAS2001:7f8:17e::133
AS29504Freenet Liberec, z.s.91.213.211.185Open
AS6204INTERKVM HOST SRL2001:7f8:17e::135
AS6204INTERKVM HOST SRL91.213.211.135
AS396986Bytedance Inc.91.213.211.137
AS396986Bytedance Inc.2001:7f8:17e::137
AS24940Hetzner Online GmbH2001:7f8:17e::132
AS24940Hetzner Online GmbH91.213.211.132
AS30058FDCservers.net91.213.211.138
AS30058FDCservers.net2001:7f8:17e::138
AS35133Eranium B.V.91.213.211.130
AS35133Eranium B.V.2001:7f8:17e::130
AS216265ARISTO NETWORKS LTD2001:7f8:17e::139
AS216265ARISTO NETWORKS LTD91.213.211.139
AS215120Evolus IT Solutions GmbH91.213.211.131
AS215120Evolus IT Solutions GmbH2001:7f8:17e::131
AS40994Hohl IT e.U.2001:7f8:17e::140
AS40994Hohl IT e.U.91.213.211.140
AS51265Mass Response Service GmbH91.213.211.143
AS51265Mass Response Service GmbH2001:7f8:17e::143
AS24641FASTER CZ spol. s r.o.91.213.211.173Open
AS64457Matteo Fruhwald trading as PipeHost e.U.91.213.211.141
AS64457Matteo Fruhwald trading as PipeHost e.U.2001:7f8:17e::141
AS208024Ronald Agorsah trading as Alpenhost e.U.2001:7f8:17e::142
AS208024Ronald Agorsah trading as Alpenhost e.U.91.213.211.142
AS219540ERANIUM B.V.2001:7f8:17e::190
AS219540ERANIUM B.V.91.213.211.190
AS219540ERANIUM B.V.2001:7f8:17e::129
AS219540ERANIUM B.V.91.213.211.129

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.