ixreport

AIRNET Italy

AS209301 · AIRNET S.R.L.S.

AIRNET S.R.L.S.

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

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

Make the changes on AIRNET Italy'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. Italy MIX Roma Rome, Italy · PeeringDB 4377
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:101:14::34
    Port speed differs1G100G
    • In the entry with IPv4 185.188.83.34: set IPv6 to 2001:7f8:101:14::34 (now empty); set Speed to 100000 (100G) (now 1000).
  2. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:b:100:1d1:a520:9301:141
    Port speed differs1G10G
    • In the entry with IPv4 217.29.67.141: set IPv6 to 2001:7f8:b:100:1d1:a520:9301:141 (now empty); set Speed to 10000 (10G) (now 1000).
  3. Italy Namex Rome Rome, Italy · PeeringDB 121
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:10::20:9301none
    Port speed differs1G10G
    • In the entry with IPv4 193.201.28.161: set IPv6 to (empty) (now 2001:7f8:10::20:9301); set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change 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 AIRNET Italy'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 3G across 3 exchanges.

Italy MIX Roma Rome, Italy 185.188.83.34 1G Yes Both IPv6 not in PeeringDBSpeed differs
Italy MIX-IT Milan, Italy 217.29.67.141 1G Yes Both IPv6 not in PeeringDBSpeed differs
Italy Namex Rome Rome, Italy 193.201.28.161 2001:7f8:10::20:9301 1G Yes Both IPv6 not in exportSpeed differs

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

These exchanges have a switch in a facility where AIRNET Italy lists itself in PeeringDB, but don't have AIRNET Italy 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 AIRNET Italy lists in PeeringDB, and how many of the exchanges in each it's on.

Italy Namex Datacenter RomeRome 1 of 2