ixreport

ICONIC SERVERS

AS214271 · Iconic Pro

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

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

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

PeeringDB fix list Printable page · CSV

3 things to fix in ICONIC SERVERS's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on ICONIC SERVERS'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 (3)

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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::3:44ff:1
    Port speed differs10G100G
    • In the entry with IPv4 195.66.227.183: set IPv6 to 2001:7f8:4::3:44ff:1 (now empty); set Speed to 100000 (100G) (now 10000).
  2. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:17::3:44ff:1
    • In the entry with IPv4 5.57.82.206: set IPv6 to 2001:7f8:17::3:44ff:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:13::a521:4271:1 2001:7f8:13::a521:4271:2
    • In the entry with IPv4 193.239.116.11: set IPv6 to 2001:7f8:13::a521:4271:2 (now empty).
    • In the entry with IPv4 193.239.116.43: set IPv6 to 2001:7f8:13::a521:4271:1 (now empty).

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Exchanges over time

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

Map

Where ICONIC SERVERS'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 220G across 3 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.227.183 10G 2 routes Both IPv6 not in PeeringDBSpeed differs
United Kingdom LONAP London, United Kingdom 5.57.82.206 10G 2 routes Both IPv6 not in PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.116.11
193.239.116.43
2 × 100G Yes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where ICONIC SERVERS lists itself in PeeringDB, but don't have ICONIC SERVERS 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.

Germany DE-CIX FrankfurtFrankfurt, Germany 1,075 Equinix FR8 - Frankfurt, West
Netherlands AMS-IXAmsterdam, Netherlands 920 Iron Mountain Data Center - Amsterdam (AMS-1); Equinix AM6 - Amsterdam, Duivendrechtsekade
Netherlands GNM-IXAmsterdam, Netherlands 741 Telehouse - London (Docklands North); Equinix AM6 - Amsterdam, Duivendrechtsekade
United States Equinix AshburnAshburn, United States 347 Equinix DC1-DC15,DC21-DC22 - Ashburn
Netherlands Frys-IXFryslân, Netherlands 338 Equinix AM6 - Amsterdam, Duivendrechtsekade
United Kingdom LINX LON2London, United Kingdom 315 Telehouse - London (Docklands North)
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix FR8 - Frankfurt, West
Netherlands INTERIXAmsterdam, Netherlands 262 Equinix AM6 - Amsterdam, Duivendrechtsekade
Netherlands ERA-IX AmsterdamAmsterdam, Netherlands 244 Iron Mountain Data Center - Amsterdam (AMS-1); Equinix AM6 - Amsterdam, Duivendrechtsekade
France Equinix ParisParis, France 239 Equinix PA5 - Paris, Victor Hugo
Germany LOCIX FRANKFURTFrankfurt am Main, Germany 205 Iron Mountain Data Center - Amsterdam (AMS-1)
Bulgaria NetIXSofia, Bulgaria 204 Equinix DC1-DC15,DC21-DC22 - Ashburn; Telehouse - London (Docklands North); Iron Mountain Data Center - Amsterdam (AMS-1) and 1 more
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North); Equinix PA5 - Paris, Victor Hugo; Equinix FR8 - Frankfurt, West
Netherlands Global-IXAmsterdam, Netherlands 138 Equinix AM6 - Amsterdam, Duivendrechtsekade
Ireland INEX LAN1Dublin, Ireland 118 Equinix DB2 - Dublin, Kilcarbery
Netherlands LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands 105 Equinix AM6 - Amsterdam, Duivendrechtsekade
United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Telehouse - London (Docklands North)
Germany ERA-IX FrankfurtFrankfurt, Germany 85 Equinix FR8 - Frankfurt, West
Germany Equinix FrankfurtFrankfurt, Germany 78 Equinix FR8 - Frankfurt, West
United States NVIXAshburn, United States 78 Equinix DC1-DC15,DC21-DC22 - Ashburn
Ireland INEX LAN2Dublin, Ireland 71 Equinix DB2 - Dublin, Kilcarbery
Netherlands 1-NL FREEAmsterdam, Netherlands 60 Equinix AM6 - Amsterdam, Duivendrechtsekade
United States LINX NoVAAshburn, Reston, Manassas, United States 57 Equinix DC1-DC15,DC21-DC22 - Ashburn
United States MegaIX AshburnAshburn, United States 49 Equinix DC1-DC15,DC21-DC22 - Ashburn
Netherlands Clue-IXAmsterdam, Netherlands 36 Iron Mountain Data Center - Amsterdam (AMS-1)
United States CIX-NoVAAshburn, Reston, Washington DC, United States 34 Equinix DC1-DC15,DC21-DC22 - Ashburn
Romania Balcan-IXBucharest, Romania 29 Telehouse - London (Docklands North)
Germany 1-DE FREEFrankfurt, Germany 27 Equinix FR8 - Frankfurt, West
France nine - six in ParisParis, France 24 Equinix PA5 - Paris, Victor Hugo
United States DACS-IX EastWashington DC, United States 15 Equinix DC1-DC15,DC21-DC22 - Ashburn
Ireland Equinix DublinDublin, Ireland 15 Equinix DB2 - Dublin, Kilcarbery
Sweden KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden 11 Iron Mountain Data Center - Amsterdam (AMS-1)
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Telehouse - London (Docklands North)
United States Global Peer ExchangeWashington, United States 6 Equinix DC1-DC15,DC21-DC22 - Ashburn; Telehouse - London (Docklands North); Iron Mountain Data Center - Amsterdam (AMS-1)
Germany TMW-iXFrankfurt am Main, Germany 5 Iron Mountain Data Center - Amsterdam (AMS-1)
United States GNM-IX USNew York, United States 4 Equinix DC1-DC15,DC21-DC22 - Ashburn
Australia ixFabricGlobal, Australia 2 Iron Mountain Data Center - Amsterdam (AMS-1)
Facilities (8)

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