Florian Voit
AS218218
Tools: Where can I peer with Florian Voit? · Where should Florian Voit peer next? · Compare Florian Voit with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
4 things to fix in Florian Voit's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-11-12 18:41 UTC.
Make the changes on Florian Voit'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 (4)
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 missing from PeeringDB none 91.213.211.93 - In the entry with IPv6 2001:7f8:17d::93: set IPv4 to 91.213.211.93 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.1.185.19 - In the entry with IPv6 2001:7f8:134::110: set IPv4 to 185.1.185.19 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 195.60.92.116 - In the entry with IPv6 2602:f93b:1a35:1311::116: set IPv4 to 195.60.92.116 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.239.119.127 - In the entry with IPv6 2001:7f8:13::a521:8218:1: set IPv4 to 193.239.119.127 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Exchanges over time
Collecting since Nov 4, 2026: one point a day, so this fills in as the days go by.
Show as a table
| Date | Exchanges |
|---|---|
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 5 |
| Nov 8, 2026 | 1 |
| Nov 7, 2026 | 1 |
| Nov 6, 2026 | 1 |
| Nov 5, 2026 | 1 |
| Nov 4, 2026 | 1 |
In the last 30 days Florian Voit joined 7 exchanges and left 0. Growing networks
Joined
- FogIXP Avers Nov 11, 2026
- NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille Nov 11, 2026
- INTERIX Amsterdam Nov 10, 2026
- 3AM Network IX Amsterdam Nov 9, 2026
- ixFabric - Amsterdam Amsterdam Nov 9, 2026 PeeringDB only
- Kawaii IX AMS Amsterdam Nov 9, 2026
- LOCIX DUSSELDORF Dusseldorf Nov 4, 2026 PeeringDB only
Map
Where Florian Voit'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.
| 3AM Network IX Amsterdam, Netherlands | 10G | Both IPv4 not in PeeringDB | |
| EVIXVIX Fremont, United States | 1G | Both | |
| FogIXP Avers, Switzerland | 1G | Both | |
| INTERIX Amsterdam, Netherlands | 100G | Both IPv4 not in PeeringDB | |
| ixFabric - Amsterdam Amsterdam, Netherlands | 1G | PeeringDB | |
| Kawaii IX AMS Amsterdam, Netherlands | 1G | Both IPv4 not in PeeringDB | |
| LOCIX DUSSELDORF Dusseldorf, Germany | 1G | PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | Both IPv4 not in PeeringDB |
These exchanges have a switch in a facility where Florian Voit lists itself in PeeringDB, but don't have Florian Voit 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.
| Frys-IXFryslân, Netherlands | 335 | |
| FogIXP AmsterdamAmsterdam, Netherlands | 56 | |
| NSIX AmsterdamAmsterdam, Netherlands | 13 | |
| PeersIX AmsterdamAmsterdam, Netherlands | 11 |
Facilities (1)
The buildings Florian Voit lists in PeeringDB, and how many of the exchanges in each it's on.
| Qupra DCAmsterdam | 5 of 9 |
Recent changes Search them
- Nov 12, 2026 [PDB] AS218218 Florian Voit now in PeeringDB at NL-ix
- Nov 11, 2026 [IXF] [WEB] AS218218 Florian Voit added to NL-ix
- Nov 11, 2026 [PDB] AS218218 Florian Voit now in PeeringDB at FogIXP
- Nov 11, 2026 [IXF] [WEB] AS218218 Florian Voit added to FogIXP
- Nov 10, 2026 [IXF] AS218218 Florian Voit now on INTERIX's IX-F list
- Nov 10, 2026 [PDB] AS218218 Florian Voit added to INTERIX
- Nov 9, 2026 [PDB] AS218218 Florian Voit added to ixFabric - Amsterdam
- Nov 9, 2026 [PDB] AS218218 Florian Voit now in PeeringDB at Kawaii IX AMS
- Nov 9, 2026 [IXF] [WEB] AS218218 Florian Voit added to Kawaii IX AMS
- Nov 9, 2026 [WEB] AS218218 Florian Voit now on EVIX's website list
- Nov 9, 2026 [PDB] AS218218 Florian Voit now in PeeringDB at EVIX
- Nov 9, 2026 [PDB] AS218218 Florian Voit now in PeeringDB at 3AM Network IX
- Nov 9, 2026 [IXF] AS218218 Florian Voit added to EVIX
- Nov 9, 2026 [IXF] [WEB] AS218218 Florian Voit added to 3AM Network IX
- Nov 4, 2026 [PDB] AS218218 Florian Voit added to LOCIX DUSSELDORF