ixreport

ALPSiX Ghost IX

ALPSiX powered by DE-CIX

Klagenfurt/Villach, Austria · Europe

Operated by BIK Breitbandinitiative Kärnten GmbH · 1 ghost exchange

Who's on ALPSiX, by source

1 of 3 match: 1 in every source2 in PeeringDB, not on the exchange's own lists

IX-F export: https://portal.de-cix.net/customer_klu, read 2026-11-19 12:22 UTC.

Ports and fees

We couldn't find ALPSiX's port fees on its website.

Ghost exchange. Already a ghost when tracking began (Oct 2, 2026). Only one outside network: AS61438. With fewer than two outside networks connected (in PeeringDB, the IX-F export, the website's members list or on its route servers), there's nobody to peer with except the operator. What counts as a ghost

How members connect

Virtual IX
No: per its IX-F export, 0 of 1 members whose connection its IX-F export describes connect by tunnel.
In its IX-F export
0 by tunnel, 1 on a physical port, 0 not given
Facilities it lists
2 in PeeringDB
Members with a building in Austria
1 of the 1 members that list any building in PeeringDB (3 members in all)
Members' countries
2 (where their organizations are, in PeeringDB)

How a Virtual IX is decided

Members over time

IX-FPeeringDB
0123Oct 2, 2026Nov 19, 202613
Show as a table
DateIX-FPeeringDB
Nov 19, 202613
Nov 18, 202613
Nov 17, 202613
Nov 16, 202613
Nov 15, 202613
Nov 14, 202613
Nov 13, 202613
Nov 12, 202613
Nov 11, 202613
Nov 10, 202613
Nov 9, 202613
Nov 8, 202613
Nov 7, 202613
Nov 6, 202613
Nov 5, 202613
Nov 4, 2026–2
Nov 3, 2026–2
Nov 2, 2026–2
Nov 1, 2026–1
Oct 31, 2026–1
Oct 30, 2026–1
Oct 29, 2026–1
Oct 28, 2026–1
Oct 27, 2026–1
Oct 26, 2026–1
Oct 25, 2026–1
Oct 24, 2026–1
Oct 23, 2026–1
Oct 22, 2026–0
Oct 21, 2026–0
Oct 20, 2026–0
Oct 19, 2026–0
Oct 18, 2026–0
Oct 17, 2026–0
Oct 16, 2026–0
Oct 15, 2026–0
Oct 14, 2026–0
Oct 13, 2026–0
Oct 12, 2026–0
Oct 11, 2026–0
Oct 10, 2026–0
Oct 9, 2026–0
Oct 8, 2026–0
Oct 7, 2026–0
Oct 6, 2026–0
Oct 5, 2026–0
Oct 4, 2026–0
Oct 3, 2026–0
Oct 2, 2026–0

Exchange details

Media
Ethernet
Protocols
Unicast IPv4, IPv6
MTU
1500
Technical
info@alpsix.net
Policy
info@alpsix.net
Sales
info@alpsix.net
PeeringDB record
Updated 2026-11-02

Peering LAN prefixes

  • 195.60.85.192/26IPv4
  • 2001:7f8:170::/64IPv6

Facilities (2)

Route servers

1Sessions up
0Sending routes
0%Of 3 peers send routes
0Routes accepted

1 network has a session up with ALPSiX's route servers, and 0 of them send routes: evidence they're really connected and peering, not just listed. Networks that only peer directly (bilaterally) don't show here. The routes column in the table below has each network's count.

From the public looking glass at lg.de-cix.net (rs1.alpsix.net (IPv4), rs1.alpsix.net (IPv6)), read 2026-11-18 18:37 UTC; one route server per address family, IPv4 and IPv6 counted together. How this is read

Data status

What the last update (every 6 hours) found for ALPSiX, step by step.

  1. IX-F export in PeeringDB The exchange hasn't published an IX-F export URL in PeeringDB.
  2. IX-F database (IXPDB) https://portal.de-cix.net/customer_klu
  3. Website search No member list found on the website (checked 2026-11-17).
  4. Member list Read 2026-11-19 12:22 UTC from the IX-F export.
  5. Port fees No fees page found on the exchange's website yet (searched weekly).
  6. Route server looking glass 1 session up on rs1.alpsix.net (IPv4), rs1.alpsix.net (IPv6), read 2026-11-18 18:37 UTC from https://lg.de-cix.net.

Embed this badge

ALPSiX on IX Report

For ALPSiX's website, a wiki or a README: it links back to this page and updates with the site, every 6 hours. The share is of the networks on ALPSiX's own member lists that PeeringDB lists here; it's left off when there's no list to compare. This page's data is also available as JSON: /api/ix/5054.json (about the API).

HTML
<a href="https://ixreport.com/ix/5054/"><img src="https://ixreport.com/ix/5054/badge.svg" alt="ALPSiX on IX Report" height="20"></a>
Markdown
[![ALPSiX on IX Report](https://ixreport.com/ix/5054/badge.svg)](https://ixreport.com/ix/5054/)

Fix list

Networks where PeeringDB and what ALPSiX publishes (its IX-F export and its website's members list) disagree. Download CSV Operator report with contacts

Published by the exchange, missing from PeeringDB (0)

These networks could add ALPSiX to their PeeringDB record.

  • None

Only in PeeringDB (2)

Either the exchange's lists are missing them, or their PeeringDB record is out of date.

Addresses and port speeds

Each network's IP addresses and port speed in PeeringDB, against ALPSiX's IX-F export, for the 1 networks in both. 1 has differences. Download CSV Operator report with contacts

PeeringDB's IX-F import is off for ALPSiX. With it on, PeeringDB would suggest these corrections to the networks.

Address belongs to another network in PeeringDB (2)
IPv4 address missing from PeeringDB (1)
AS199813 ALPSiX Route Servers 195.60.85.252
195.60.85.253
195.60.85.249
195.60.85.252
195.60.85.253
195.60.85.254
IPv6 address missing from PeeringDB (1)
AS199813 ALPSiX Route Servers 2001:7f8:170:0:3:c85:a:1
2001:7f8:170:0:3:c85:a:2
2001:7f8:170:0:3:c85:a:1
2001:7f8:170:0:3:c85:a:2
2001:7f8:170:0:3:c85:b:dead
2001:7f8:170:0:3:c85:c:1
Port speed differs (1)
AS199813 ALPSiX Route Servers 2 × 20G 4 × 20G

Recent changes Search them

  • Nov 5, 2026 IXFMember list now reading ALPSiX's IX-F list (1 members)
  • Nov 5, 2026 PDBAS205529 DE-CIX Monitoring added to ALPSiX
  • Nov 5, 2026 IXFList fixed ALPSiX's IX-F export can be read again
  • Nov 2, 2026 PDBAS199813 ALPSiX Route Servers added to ALPSiX
  • Oct 23, 2026 PDBAS61438 ip-it consult GmbH added to ALPSiX

3 networks

AS61438 ip-it consult GmbH 195.60.85.193 2001:7f8:170::1 1G Yes PeeringDB IX-F
AS199813 ALPSiX Route ServersExchange lists it as “ALPSiX” 195.60.85.252
195.60.85.253
2001:7f8:170:0:3:c85:a:1
2001:7f8:170:0:3:c85:a:2
2 × 20G PeeringDB IX-F
AS205529 DE-CIX Monitoring 195.60.85.249 2001:7f8:170:0:3:c85:c:1 20G Up, 0 PeeringDB IX-F