4ALL
AS50316 · 4ALL
Net Global srl
Tools: Where can I peer with 4ALL? · Where should 4ALL peer next? · Compare 4ALL with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
3 things to fix in 4ALL's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on 4ALL'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.
-
Problem PeeringDB has The export has Port speed differs 4G 1.2T - In the entry with IPv4 80.81.193.99: set Speed to 1200000 (1.2T) (now 4000).
-
Problem PeeringDB has The export has Port speed differs 20G 2 × 20G - Add an entry: IPv4 –, IPv6 2001:7f8:b:100:1d1:a5d5:316:110, speed 20000 (20G), RS peer yes.
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:7f8:5f:ffff::22 none Port speed differs 20G 40G - In the entry with IPv4 185.1.115.22: set IPv6 to (empty) (now 2001:7f8:5f:ffff::22); set Speed to 40000 (40G) (now 20000).
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 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 8 |
| Nov 2, 2026 | 8 |
| Nov 1, 2026 | 8 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 8 |
| Oct 29, 2026 | 8 |
| Oct 28, 2026 | 8 |
| Oct 27, 2026 | 8 |
| Oct 26, 2026 | 8 |
| Oct 25, 2026 | 8 |
| Oct 24, 2026 | 8 |
| Oct 23, 2026 | 8 |
| Oct 22, 2026 | 8 |
| Oct 21, 2026 | 8 |
| Oct 20, 2026 | 8 |
| Oct 19, 2026 | 8 |
| Oct 18, 2026 | 8 |
| Oct 17, 2026 | 8 |
| Oct 16, 2026 | 8 |
| Oct 15, 2026 | 8 |
| Oct 14, 2026 | 8 |
| Oct 13, 2026 | 8 |
| Oct 12, 2026 | 8 |
| Oct 11, 2026 | 8 |
| Oct 10, 2026 | 8 |
| Oct 9, 2026 | 8 |
| Oct 8, 2026 | 8 |
| Oct 7, 2026 | 8 |
| Oct 6, 2026 | 8 |
| Oct 5, 2026 | 8 |
| Oct 4, 2026 | 8 |
| Oct 3, 2026 | 8 |
Map
Where 4ALL'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.
| AMS-IX Amsterdam, Netherlands | 3G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 4G | Both Speed differs | |
| LINX LON1 London, United Kingdom | 3G | Both | |
| MINAP Milan Milan, Italy | 20G | Both | |
| MIX-IT Milan, Italy | 20G | Both Speed differs | |
| Namex Rome Rome, Italy | 10G | Both | |
| TOP-IX Turin, Italy | 20G | Both | |
| VSIX Padova, Italy | 20G | Both IPv6 not in exportSpeed differs |
These exchanges have a switch in a facility where 4ALL lists itself in PeeringDB, but don't have 4ALL 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 | |
| Equinix MilanMilan, Italy | 35 | |
| PCIXPiacenza, Italy | 34 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (6)
The buildings 4ALL lists in PeeringDB, and how many of the exchanges in each it's on.
| MIX DC CALDERAMilan | 1 of 6 | |
| VSIXPadova | 1 of 3 | |
| Namex Datacenter RomeRome | 1 of 2 | |
| FEIXFerrara | No exchange | |
| Net Global DCPadua | No exchange | |
| NS3 - PD02Padova | No exchange |