Time-Net AS51580
AS51580 · TIMENET
Timenet S.p.A.
Tools: Where can I peer with Time-Net AS51580? · Where should Time-Net AS51580 peer next? · Compare Time-Net AS51580 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 Time-Net AS51580's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Time-Net AS51580'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 (2)
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 IPv4 address in PeeringDB, not in the export 217.29.66.170 217.29.68.170 217.29.66.170 IPv6 address in PeeringDB, not in the export 2001:7f8:b:100:1d1:a5d5:1580:170 2001:7f8:b:101:1d1:a5d5:1580:170 2001:7f8:b:100:1d1:a5d5:1580:170 - The entry with IPv4 217.29.68.170, IPv6 2001:7f8:b:101:1d1:a5d5:1580:170 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:10::5:1580 - In the entry with IPv4 193.201.29.27: set IPv6 to 2001:7f8:10::5:1580 (now empty).
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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
Map
Where Time-Net AS51580'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.
| Equinix Milan Milan, Italy | 10G | PeeringDB | |
| MINAP Milan Milan, Italy | 10G | Both | |
| MIX-IT Milan, Italy | 2 × 10G | Both IPv4 not in exportIPv6 not in export | |
| Namex Rome Rome, Italy | 20G | Both IPv6 not in PeeringDB | |
| TOP-IX Turin, Italy | 10G | Both | |
| VSIX Padova, Italy | 10G | Both |
These exchanges have a switch in a facility where Time-Net AS51580 lists itself in PeeringDB, but don't have Time-Net AS51580 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 | |
| PCIXPiacenza, Italy | 34 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (5)
The buildings Time-Net AS51580 lists in PeeringDB, and how many of the exchanges in each it's on.
| MIX DC CALDERAMilan | 2 of 6 | |
| Retelit Avalon 1Milan | 5 of 6 | |
| Equinix ML2 - Milan, SavonaMilan | 3 of 3 | |
| VSIXPadova | 1 of 3 | |
| Namex Datacenter RomeRome | 1 of 2 |