ixreport

INTERCONN

AS60530 · Alconn S.r.l.

Interconn S.r.l.

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

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

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

PeeringDB fix list Printable page · CSV

2 things to fix in INTERCONN's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-11-19 12:40 UTC.

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

Add these exchanges (2)

On the exchange's own member list, but not in INTERCONN's PeeringDB record. Add one entry per connection with these values.

  1. Italy MIX Roma Rome, Italy · PeeringDB 4377From its IX-F export
    IPv4185.188.83.12
    IPv62001:7f8:101:14::12
    Speed10000 Mbps (10G)
    RS peerYes
  2. Italy MIX-IT Milan, Italy · PeeringDB 35From its IX-F export
    IPv4217.29.67.230
    IPv62001:7f8:b:100:1d1:a5d6:530:230
    Speed10000 Mbps (10G)
    RS peerYes

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 INTERCONN'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 30G across 3 exchanges.

Italy MIX Roma Rome, Italy 185.188.83.12 2001:7f8:101:14::12 10G Yes Not in PeeringDB
Italy MIX-IT Milan, Italy 217.29.67.230 2001:7f8:b:100:1d1:a5d6:530:230 10G Yes Not in PeeringDB
Italy Namex Rome Rome, Italy 193.201.28.80 2001:7f8:10::6:530 10G Yes Both

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

These exchanges have a switch in a facility where INTERCONN lists itself in PeeringDB, but don't have INTERCONN 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 Namex Datacenter Rome
Facilities (1)

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

Italy Namex Datacenter RomeRome 1 of 2