Retelit Spa
AS28716
Tools: Where can I peer with Retelit Spa? · Where should Retelit Spa peer next? · Compare Retelit Spa with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
7 things to fix in Retelit Spa's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct, 2 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Retelit Spa'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 Retelit Spa's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.97.19 IPv6 2001:7f8:b9::19:1 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 185.1.124.10 IPv6 2001:7f8:cf::10 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
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.
-
Problem PeeringDB has The export has Port speed differs 10G 20G - In the entry with IPv4 80.81.193.33: set Speed to 20000 (20G) (now 10000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 217.29.66.44 217.29.66.44 217.29.66.53 IPv6 address missing from PeeringDB 2001:7f8:b:100:1d1:a5d2:8716:44 2001:7f8:b:100:1d1:a5d2:8716:44 2001:7f8:b:100:1d1:a5d2:8716:53 Port speed differs 60G 100G + 10G - In the entry with IPv4 217.29.66.44: set Speed to 100000 (100G) (now 60000).
- Add an entry: IPv4 217.29.66.53, IPv6 2001:7f8:b:100:1d1:a5d2:8716:53, speed 10000 (10G), RS peer yes.
-
Problem PeeringDB has The export has Port speed differs 2G 10G - In the entry with IPv4 185.1.115.7: set Speed to 10000 (10G) (now 2000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If Retelit Spa has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.227.25 IPv6 2001:7f8:4::702c:1 Speed 10000 Mbps (10G) -
IPv4 195.66.239.25 IPv6 2001:7f8:4:1::702c:1 Speed 1000 Mbps (1G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 11 |
| Nov 3, 2026 | 11 |
| Nov 2, 2026 | 11 |
| Nov 1, 2026 | 11 |
| Oct 31, 2026 | 11 |
| Oct 30, 2026 | 11 |
| Oct 29, 2026 | 11 |
| Oct 28, 2026 | 11 |
| Oct 27, 2026 | 11 |
| Oct 26, 2026 | 11 |
| Oct 25, 2026 | 11 |
| Oct 24, 2026 | 11 |
| Oct 23, 2026 | 11 |
| Oct 22, 2026 | 11 |
| Oct 21, 2026 | 11 |
| Oct 20, 2026 | 11 |
| Oct 19, 2026 | 11 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 11 |
| Oct 3, 2026 | 11 |
Map
Where Retelit Spa'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.
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both Speed differs | |
| Ge-DIX Genova, Italy | 10G | Both | |
| LINX LON1 London, United Kingdom | 10G | PeeringDB only | |
| LINX LON2 London, United Kingdom | 1G | PeeringDB only | |
| MIX-IT Milan, Italy | 60G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| Namex Rome Rome, Italy | 10G | Both | |
| PCIX Piacenza, Italy | 10G | Not in PeeringDB | |
| STIX Bozen/Bolzano, Italy | 10G | Not in PeeringDB | |
| TOP-IX Turin, Italy | 10G | Both | |
| VSIX Padova, Italy | 2G | Both Speed differs |
These exchanges have a switch in a facility where Retelit Spa lists itself in PeeringDB, but don't have Retelit Spa 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.
| NetIXSofia, Bulgaria | 204 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| MINAP MilanMilan, Italy | 118 | |
| Equinix MilanMilan, Italy | 35 | |
| MIX PalermoPalermo, Italy | 25 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (10)
The buildings Retelit Spa lists in PeeringDB, and how many of the exchanges in each it's on.
| MIX DC CALDERAMilan | 1 of 6 | |
| Retelit Avalon 1Milan | 3 of 6 | |
| Aruba IT3 - Milan PSPPonte San Pietro | 2 of 3 | |
| Equinix ML2 - Milan, SavonaMilan | 2 of 3 | |
| VSIXPadova | 2 of 3 | |
| DATA4 Milan-Cornaredo - MIL1Cornaredo (MI) | 2 of 2 | |
| Namex Datacenter RomeRome | 1 of 2 | |
| Open Hub MedCarini | 1 of 2 | |
| Naquadria Datacenter PiacenzaPiacenza | 1 of 1 | |
| Vaultica Data Centers | MIL01Siziano | 1 of 1 |