ixreport

CONNECTIVIA

AS207594 · Connectivia

Connectivia

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

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

Make the changes on CONNECTIVIA'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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G3G
    • In the entry with IPv4 195.66.231.55: set Speed to 3000 (3G) (now 10000).

Exchanges over time

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

Map

Where CONNECTIVIA'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 83G across 8 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.210.200 2001:7f8:1:0:a500:20:7594:1 3G 45 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.242 2001:7f8::3:2ae:0:1 10G 43 routes Both
United Kingdom LINX LON1 London, United Kingdom 195.66.231.55 2001:7f8:4::3:2aea:1 10G 44 routes Both Speed differs
Italy MINAP Milan Milan, Italy 185.1.114.98 2001:7f8:c5::a520:7594:1 10G 44 routes Both
Italy MIX-IT Milan, Italy 217.29.67.119 2001:7f8:b:100:1d1:a520:7594:119 20G Yes Both
Italy Namex Bari Bari, Italy 185.1.218.8 2001:7f8:11b::20:7594 10G Yes PeeringDB
Italy Namex Napoli Napoli, Italy 185.0.9.16 2001:7f8:13f::20:7594 10G Yes PeeringDB
Italy Namex Rome Rome, Italy 193.201.28.144 2001:7f8:10::20:7594 10G Yes Both

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

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

Bulgaria NetIXSofia, Bulgaria 204 MIX DC CALDERA; Namex Datacenter Rome
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 MIX DC CALDERA
Italy Equinix MilanMilan, Italy 35 MIX DC CALDERA
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 MIX DC CALDERA
United States Global Peer ExchangeWashington, United States 6 MIX DC CALDERA
Facilities (3)

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

Italy MIX DC CALDERAMilan 1 of 6
Italy Namex Datacenter RomeRome 1 of 2
Italy Namex Bari DatacenterBari 1 of 1