ixreport

AlpineDC

AS198385 · AlpineDC

AlpineDC SA

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
4Using the route servers
1To fix in PeeringDB
4Facilities in PeeringDB

Tools: Where can I peer with AlpineDC? · Where should AlpineDC peer next? · Compare AlpineDC with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in AlpineDC's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on AlpineDC's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 80.81.193.121: set Speed to 200000 (200G) (now 10000).

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where AlpineDC's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 50G across 4 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.121 2001:7f8::3:6f1:0:1 10G 29 routes Both Speed differs
France France-IX Paris Paris, France 37.49.237.156 2001:7f8:54::1:156 10G Yes PeeringDB
Switzerland RomandIX Lausanne, Switzerland 185.1.93.7 2001:7f8:b5::7 10G Yes PeeringDB
Switzerland SwissIX Zurich, Switzerland 91.206.52.109
91.206.53.109
2001:7f8:24::6d
2001:7f8:24::16d
2 × 10G 60 routes Both

Exchanges in its buildings that it isn't on (7)

These exchanges have a switch in a facility where AlpineDC lists itself in PeeringDB, but don't have AlpineDC as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Switzerland FogIXPAvers, Switzerland 532 colozueri.ch Zurich
Switzerland CHIX-CHFrauenfeld, Switzerland 66 colozueri.ch Zurich
France HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France 58 colozueri.ch Zurich
Switzerland Community-IX.chZurich, Switzerland 18 colozueri.ch Zurich
Switzerland FogIXP ZurichZurich, Switzerland 9 colozueri.ch Zurich
Switzerland Exchange7Winterthur, Switzerland 8 Brainserve
United States Global Peer ExchangeWashington, United States 6 Brainserve
Facilities (4)

The buildings AlpineDC lists in PeeringDB, and how many of the exchanges in each it's on.

Switzerland colozueri.ch ZurichZurich 1 of 6
Switzerland BrainserveCrissier 1 of 3
Switzerland AlpineDCLausanne 1 of 1
Switzerland colobern.ch BernBern 1 of 1