Verizon - EMEA
AS702 · MCI, UUNET, Verizon, VZB
Verizon Communications, Inc.
Tools: Where can I peer with Verizon - EMEA? · Where should Verizon - EMEA peer next? · Compare Verizon - EMEA with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in Verizon - EMEA's PeeringDB record, from what its exchanges publish: 4 to add, 4 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Verizon - EMEA'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 (4)
On the exchange's own member list, but not in Verizon - EMEA's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 194.68.128.81 IPv6 2001:7f8:d:fe::81 Speed Not published RS peer No -
IPv4 195.69.119.81 IPv6 2001:7f8:d:fb::81 Speed Not published RS peer No -
IPv4 195.245.240.81 IPv6 2001:7f8:d:fc::81 Speed Not published RS peer No
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 IPv6 address missing from PeeringDB none 2001:7f8:26::a500:702:1 - In the entry with IPv4 194.53.172.78: set IPv6 to 2001:7f8:26::a500:702:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 200G - In the entry with IPv4 80.81.193.1: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:7f8:6e::12 none Port speed differs 300M 1G - In the entry with IPv4 176.126.38.12: set IPv6 to (empty) (now 2001:7f8:6e::12); set Speed to 1000 (1G) (now 300).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:14::66:1 - In the entry with IPv4 91.210.16.25: set IPv6 to 2001:7f8:14::66:1 (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 | 19 |
| Nov 18, 2026 | 19 |
| Nov 17, 2026 | 19 |
| Nov 16, 2026 | 19 |
| Nov 15, 2026 | 19 |
| Nov 14, 2026 | 19 |
| Nov 13, 2026 | 19 |
| Nov 12, 2026 | 19 |
| Nov 11, 2026 | 19 |
| Nov 10, 2026 | 19 |
| Nov 9, 2026 | 19 |
| Nov 8, 2026 | 19 |
| Nov 7, 2026 | 19 |
| Nov 6, 2026 | 19 |
| Nov 5, 2026 | 19 |
| Nov 4, 2026 | 19 |
| Nov 3, 2026 | 19 |
| Nov 2, 2026 | 19 |
| Nov 1, 2026 | 19 |
| Oct 31, 2026 | 19 |
| Oct 30, 2026 | 19 |
| Oct 29, 2026 | 19 |
| Oct 28, 2026 | 19 |
| Oct 27, 2026 | 19 |
| Oct 26, 2026 | 19 |
| Oct 25, 2026 | 19 |
| Oct 24, 2026 | 19 |
| Oct 23, 2026 | 19 |
| Oct 22, 2026 | 19 |
| Oct 21, 2026 | 19 |
| Oct 20, 2026 | 20 |
| Oct 19, 2026 | 20 |
| Oct 18, 2026 | 20 |
| Oct 17, 2026 | 20 |
| Oct 16, 2026 | 20 |
| Oct 15, 2026 | 20 |
| Oct 14, 2026 | 20 |
| Oct 13, 2026 | 20 |
| Oct 12, 2026 | 20 |
| Oct 11, 2026 | 20 |
| Oct 10, 2026 | 20 |
| Oct 9, 2026 | 20 |
| Oct 8, 2026 | 20 |
| Oct 7, 2026 | 20 |
| Oct 6, 2026 | 17 |
| Oct 5, 2026 | 17 |
| Oct 4, 2026 | 17 |
| Oct 3, 2026 | 17 |
In the last 30 days Verizon - EMEA joined 0 exchanges and left 1. Growing networks
Left
- NIX1 Oslo Oct 21, 2026 PeeringDB only
Map
Where Verizon - EMEA'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 | 100G | Both | |
| BNIX Brussels, Belgium | 10G | Both IPv6 not in PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 100G | Both Speed differs | |
| DE-CIX Madrid Madrid, Spain | 10G | Both | |
| Equinix Zurich Zurich, Switzerland | 10G | PeeringDB | |
| ESpanix Madrid Lower LAN Madrid, Spain | 10G | PeeringDB | |
| FICIX 2 (Helsinki) Helsinki, Finland | Not in PeeringDB | ||
| France-IX Paris Paris, France | 30G | PeeringDB | |
| GR-IX::Athens Athens, Greece | 300M | Both IPv6 not in exportSpeed differs | |
| INEX LAN1 Dublin, Ireland | 30G | Both | |
| LINX LON1 London, United Kingdom | 100G | Both | |
| MIX-IT Milan, Italy | 100G | Both | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | Not in PeeringDB | ||
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 20G | Both | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| NIX.CZ Prague, Czechia | 10G | Both IPv6 not in PeeringDB | |
| SwissIX Zurich, Switzerland | 100G | Both | |
| VIX Vienna, Austria | 3G | Both |
These exchanges have a switch in a facility where Verizon - EMEA lists itself in PeeringDB, but don't have Verizon - EMEA 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.
| GNM-IXAmsterdam, Netherlands | 741 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| FogIXPAvers, Switzerland | 532 | |
| TPIX PLWarsaw, Poland | 480 | |
| KleyReXFrankfurt, Germany | 471 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| Giganet IXNAmsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 268 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| THINX WarsawWarsaw, Poland | 194 | |
| PITER-IX FrankfurtFrankfurt, Germany | 172 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| InterLAN-IXBucharest, Romania | 149 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| BIXBudapest, Hungary | 122 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| Equinix FrankfurtFrankfurt, Germany | 78 | |
| B-IXSofia, Bulgaria | 77 | |
| BALT-IXVilnius, Lithuania | 77 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| 91-IXFrankfurt, Germany | 53 | |
| Giganet IXN FrankfurtFrankfurt, Germany | 50 | |
| PyramIXCairo, Egypt | 48 | |
| RoNIXBucharest, Romania | 43 | |
| Balcan-IXBucharest, Romania | 29 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| OpenCarrier OCIXDuesseldorf, Germany | 20 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| AKIXZurich, Switzerland | 11 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| TievoluIXFrankfurt, Germany | 4 |
Facilities (7)
The buildings Verizon - EMEA lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix FR5 - Frankfurt, KleyerStrasseFrankfurt | 2 of 33 | |
| Digital Realty Frankfurt FRA1-27Frankfurt | 2 of 30 | |
| Equinix FR7 - Frankfurt, GutleutstrasseFrankfurt | 1 of 12 | |
| Equinix FR6 - Frankfurt, WestFrankfurt | 1 of 9 | |
| NTT Frankfurt 1 Data Center (FRA1)Frankfurt | 1 of 8 | |
| ITENOS Frankfurt (FRA1)Frankfurt | 1 of 5 | |
| Telehouse - FrankfurtFrankfurt | 1 of 5 |
Recent changes Search them
- Oct 21, 2026 [PDB] AS702 Verizon - EMEA left NIX1