ixreport

Datapark

AS21040 · formerly Datapark AG

Datapark AG

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Datapark? · Where should Datapark peer next? · Compare Datapark 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 Datapark's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Datapark'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.192.56: set Speed to 200000 (200G) (now 10000).

Exchanges over time

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

Map

Where Datapark'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 2 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.56 2001:7f8::5230:0:1 10G 11 routes Both Speed differs
Switzerland SwissIX Zurich, Switzerland 91.206.52.72
91.206.52.146
2001:7f8:24::48
2001:7f8:24::92
2 × 20G 22 routes Both

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

These exchanges have a switch in a facility where Datapark lists itself in PeeringDB, but don't have Datapark 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 Digital Realty Zurich ZUR1
Bulgaria NetIXSofia, Bulgaria 204 Equinix ZH2 - Zurich; Digital Realty Zurich ZUR1
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Equinix ZH2 - Zurich
Switzerland CHIX-CHFrauenfeld, Switzerland 66 Equinix ZH2 - Zurich; Digital Realty Zurich ZUR1
France HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France 58 Equinix ZH2 - Zurich
Switzerland Equinix ZurichZurich, Switzerland 40 Equinix ZH2 - Zurich
Switzerland FogIXP ZurichZurich, Switzerland 9 Digital Realty Zurich ZUR1
Switzerland Exchange7Winterthur, Switzerland 8 Digital Realty Zurich ZUR1
Facilities (2)

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

Switzerland Digital Realty Zurich ZUR1Glattbrugg 1 of 6
Switzerland Equinix ZH2 - ZurichZurich 1 of 6