Netnod
AS8674 · Autonomica
Netnod AB
Tools: Where can I peer with Netnod? · Where should Netnod peer next? · Compare Netnod with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
19 things to fix in Netnod's PeeringDB record, from what its exchanges publish: 2 to add, 14 to correct, 3 to check. As of 2026-11-19 12:40 UTC.
Make the changes on Netnod'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 Netnod'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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (14)
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 192.65.185.235 192.65.185.236 192.65.185.235 IPv6 address in PeeringDB, not in the export 2001:7f8:1c:24a::21e2:1 2001:7f8:1c:24a::21e2:2 2001:7f8:1c:24a::21e2:1 Port speed differs 2 × 1G 1G - The entry with IPv4 192.65.185.236, IPv6 2001:7f8:1c:24a::21e2:2 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 80.81.192.160 80.81.192.160 80.81.193.160 IPv6 address missing from PeeringDB 2001:7f8::21e2:0:1 2001:7f8::21e2:0:1 2001:7f8::21e2:0:2 Port speed differs 1G 2 × 1G - Add an entry: IPv4 80.81.193.160, IPv6 2001:7f8::21e2:0:2, speed 1000 (1G), RS peer yes.
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 206.83.136.15: set Speed to 1000 (1G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 100G - In the entry with IPv4 27.106.192.67: set Speed to 100000 (100G) (now 20000).
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 20G 100G - In the entry with IPv4 218.100.52.147: set Speed to 100000 (100G) (now 20000).
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 in PeeringDB, not in the export 2001:43f8:6d0::9:160 none - In the entry with IPv4 196.60.9.160: set IPv6 to (empty) (now 2001:43f8:6d0::9:160).
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 IPv4 address in PeeringDB, not in the export 212.237.192.74 212.237.192.75 212.237.192.75 IPv6 address in PeeringDB, not in the export 2001:7f8:d:202::74 2001:7f8:d:202::75 2001:7f8:d:202::75 - The entry with IPv4 212.237.192.74, IPv6 2001:7f8:d:202::74 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 212.237.193.74 212.237.193.75 212.237.193.75 IPv6 address in PeeringDB, not in the export 2001:7f8:d:203::74 2001:7f8:d:203::75 2001:7f8:d:203::75 - The entry with IPv4 212.237.193.74, IPv6 2001:7f8:d:203::74 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 194.68.130.72 is AS39871 Netnod Gothenburg 194.68.130.72 Address belongs to another network in PeeringDB 2001:7f8:d:100::72 is AS39871 Netnod Gothenburg 2001:7f8:d:100::72 IPv4 address in PeeringDB, not in the export 194.68.130.74 194.68.130.72 IPv6 address in PeeringDB, not in the export 2001:7f8:d:100::74 2001:7f8:d:100::72 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 194.68.130.74: set IPv4 to (empty) (now 194.68.130.74); set IPv6 to (empty) (now 2001:7f8:d:100::74).
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 195.69.116.72 is AS39871 Netnod Gothenburg 195.69.116.72 Address belongs to another network in PeeringDB 2001:7f8:d:101::72 is AS39871 Netnod Gothenburg 2001:7f8:d:101::72 IPv4 address in PeeringDB, not in the export 195.69.116.74 195.69.116.72 IPv6 address in PeeringDB, not in the export 2001:7f8:d:101::74 2001:7f8:d:101::72 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 195.69.116.74: set IPv4 to (empty) (now 195.69.116.74); set IPv6 to (empty) (now 2001:7f8:d:101::74).
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 194.68.131.72 is AS20943 Netnod Lulea 194.68.131.72 Address belongs to another network in PeeringDB 2001:7f8:d:400::72 is AS20943 Netnod Lulea 2001:7f8:d:400::72 IPv4 address in PeeringDB, not in the export 194.68.131.74 194.68.131.72 IPv6 address in PeeringDB, not in the export 2001:7f8:d:400::74 2001:7f8:d:400::72 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 194.68.131.74: set IPv4 to (empty) (now 194.68.131.74); set IPv6 to (empty) (now 2001:7f8:d:400::74).
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 194.68.128.73 is AS39870 Netnod Services 194.68.128.73 Address belongs to another network in PeeringDB 2001:7f8:d:fe::73 is AS39870 Netnod Services 2001:7f8:d:fe::73 IPv4 address in PeeringDB, not in the export 194.68.128.172 194.68.128.73 IPv6 address in PeeringDB, not in the export 2001:7f8:d:fe::172 2001:7f8:d:fe::73 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 194.68.128.172: set IPv4 to (empty) (now 194.68.128.172); set IPv6 to (empty) (now 2001:7f8:d:fe::172).
-
Problem PeeringDB has The export has IPv4 address differs 194.68.123.73 194.68.123.172 IPv6 address differs 2001:7f8:d:ff::73 2001:7f8:d:ff::172 - In the entry with IPv4 194.68.123.73: set IPv4 to 194.68.123.172 (now 194.68.123.73); set IPv6 to 2001:7f8:d:ff::172 (now 2001:7f8:d:ff::73).
-
Problem PeeringDB has The export has IPv4 address differs 195.245.240.73 195.245.240.172 IPv6 address differs 2001:7f8:d:fc::73 2001:7f8:d:fc::172 - In the entry with IPv4 195.245.240.73: set IPv4 to 195.245.240.172 (now 195.245.240.73); set IPv6 to 2001:7f8:d:fc::172 (now 2001:7f8:d:fc::73).
Check these entries (3)
In PeeringDB, but on none of the exchange's own lists. If Netnod has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 91.218.7.105 IPv6 2001:7f8:94::105 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 218.100.44.132 IPv6 2001:de8:10::25 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 195.69.119.172 IPv6 2001:7f8:d:fb::172 Speed 100000 Mbps (100G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 102 |
| Nov 18, 2026 | 102 |
| Nov 17, 2026 | 102 |
| Nov 16, 2026 | 102 |
| Nov 15, 2026 | 102 |
| Nov 14, 2026 | 102 |
| Nov 13, 2026 | 102 |
| Nov 12, 2026 | 102 |
| Nov 11, 2026 | 102 |
| Nov 10, 2026 | 102 |
| Nov 9, 2026 | 102 |
| Nov 8, 2026 | 102 |
| Nov 7, 2026 | 102 |
| Nov 6, 2026 | 102 |
| Nov 5, 2026 | 102 |
| Nov 4, 2026 | 102 |
| Nov 3, 2026 | 102 |
| Nov 2, 2026 | 102 |
| Nov 1, 2026 | 102 |
| Oct 31, 2026 | 102 |
| Oct 30, 2026 | 102 |
| Oct 29, 2026 | 102 |
| Oct 28, 2026 | 101 |
| Oct 27, 2026 | 101 |
| Oct 26, 2026 | 101 |
| Oct 25, 2026 | 100 |
| Oct 24, 2026 | 100 |
| Oct 23, 2026 | 100 |
| Oct 22, 2026 | 100 |
| Oct 21, 2026 | 100 |
| Oct 20, 2026 | 100 |
| Oct 19, 2026 | 100 |
| Oct 18, 2026 | 100 |
| Oct 17, 2026 | 100 |
| Oct 16, 2026 | 100 |
| Oct 15, 2026 | 100 |
| Oct 14, 2026 | 100 |
| Oct 13, 2026 | 100 |
| Oct 12, 2026 | 100 |
| Oct 11, 2026 | 100 |
| Oct 10, 2026 | 100 |
| Oct 9, 2026 | 100 |
| Oct 8, 2026 | 100 |
| Oct 7, 2026 | 100 |
| Oct 6, 2026 | 100 |
| Oct 5, 2026 | 100 |
| Oct 4, 2026 | 100 |
| Oct 3, 2026 | 100 |
In the last 30 days Netnod joined 1 exchange and left 0. Growing networks
Joined
- VSIX Padova Oct 29, 2026
Map
Where Netnod'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.
| Amaravati IX Amaravati, India | 10G | Both | |
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| ArmIX Yerevan, Armenia | 10G | PeeringDB only | |
| BALT-IX Vilnius, Lithuania | 10G | Both | |
| BCIX Berlin, Germany | 10G | Both | |
| BIX.BG Sofia, Bulgaria | 10G | Both | |
| BNIX Brussels, Belgium | 1G | Both | |
| CANIX Montreal Montreal, Canada | 10G | Both | |
| CitraIX Yogyakarta Yogyakarta, Indonesia | 10G | Both | |
| CIXP Geneva, Switzerland | 2 × 1G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| CNX Phnom Penh, Cambodia | 10G | Both | |
| CSIX Vancouver, Canada | 10G | PeeringDB | |
| CXC Denpasar Denpasar, Indonesia | 10G | PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 1G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| DIX-IE Tokyo, Japan | 10G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 10G | PeeringDB | |
| Equinix Miami Miami, United States | 10G | PeeringDB | |
| Equinix Palo Alto Palo Alto, United States | 10G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 1G | PeeringDB | |
| FCIX Fremont, United States | 10G | Both | |
| FICIX 1 (Espoo) Espoo, Finland | 10G | PeeringDB | |
| FICIX 2 (Helsinki) Helsinki, Finland | 10G | Both | |
| France-IX AURA Lyon and Grenoble, France | 10G | PeeringDB | |
| France-IX Lille Lille, France | 10G | PeeringDB | |
| France-IX Marseille Marseille, France | 10G | PeeringDB | |
| France-IX Paris Paris, France | 10G | PeeringDB | |
| France-IX Toulouse Toulouse, France | 10G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 10G | PeeringDB | |
| Giganet IXN Amsterdam, Frankfurt am Main, Kharkiv, Kyiv, Lviv, Odesa, Warsaw, Zaporizhzhia, Zhytomyr, Ukraine | 20G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 10G | Both | |
| HOUIX Houston, United States | 10G | Both Speed differs | |
| InteRed Panama Panama, Panama | 10G | Both | |
| IX Australia Perth (WA-IX) Perth, Australia | 20G | Both Speed differs | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 20G | Both Speed differs | |
| IX-Denver Denver, United States | 10G | Both | |
| IX.br (PTT.br) Porto Alegre Porto Alegre/RS, Brazil | 10G | Both | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 10G | Both | |
| JINX Johannesburg, South Africa | 1G | Both | |
| JPIX TOKYO Tokyo, Japan | 10G | Both | |
| JPNAP Tokyo Tokyo, Japan | 10G | PeeringDB | |
| JXIX Jacksonville, United States | 10G | PeeringDB | |
| KazNIX Semey, Kazakhstan | 10G | Both | |
| KCIX Kansas City, United States | 10G | Both | |
| LINX LON1 London, United Kingdom | 2 × 10G | Both | |
| LONAP London, United Kingdom | 2 × 10G | Both | |
| LU-CIX Luxembourg, Luxembourg | 1G | Both | |
| MICE Minneapolis, MN, United States | 10G | Both | |
| MIX-IT Milan, Italy | 2 × 10G | Both | |
| MSK-IX Moscow Moscow, Russia | Website list only | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 2 × 1G | Both | |
| MyIX Kuala Lumpur, Malaysia | 1G | PeeringDB only | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Both IPv6 not in export | |
| Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark | 100G + 10G | Both IPv4 not in exportIPv6 not in export | |
| Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark | 100G + 10G | Both IPv4 not in exportIPv6 not in export | |
| Netnod Gothenburg -- MTU1500 Gothenburg, Sweden | 1G | Both Address takenIPv4 not in exportIPv6 not in export | |
| Netnod Gothenburg -- MTU4470 Gothenburg, Sweden | 1G | Both Address takenIPv4 not in exportIPv6 not in export | |
| Netnod Helsinki BLUE -- MTU9K Helsinki, Finland | 10G | Both | |
| Netnod Helsinki GREEN -- MTU9K Helsinki, Finland | 10G | Both | |
| Netnod Lulea -- MTU9K Lulea, Sweden | 1G | Both Address takenIPv4 not in exportIPv6 not in export | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 100G | Both Address takenIPv4 not in exportIPv6 not in export | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | 100G | PeeringDB only | |
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 100G | Both IPv4 differsIPv6 differs | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | 100G | Both IPv4 differsIPv6 differs | |
| Netnod Sundsvall -- MTU1500 Sundsvall / Gavle, Sweden | 1G | Both | |
| Netnod Sundsvall -- MTU4470 Sundsvall / Gavle, Sweden | 1G | Both | |
| NIX.CZ Prague, Czechia | Website list only | ||
| NIX.SK Bratislava, Slovakia | 10G | Both | |
| NIX1 Oslo, Norway | 2 × 1G | PeeringDB | |
| NIXI Mumbai Mumbai, India | 2 × 1G | PeeringDB | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 10G | Both | |
| npIX DH Kathmandu, Nepal | 2 × 1G | Both | |
| ONIX Toronto, Canada | 10G | Both | |
| PCIX Piacenza, Italy | 10G | Both | |
| PIT - Peru - Lima Lima, Peru | 10G | PeeringDB | |
| PIT Santiago - PIT Chile Santiago, Chile | 1G | PeeringDB | |
| QCIX Davenport, United States | 10G | Both | |
| QIX Qatar Doha, Qatar | 1G | PeeringDB | |
| Rheintal IX Eschen, Liechtenstein | 10G | Both | |
| RINEX Kigali, Rwanda | 2 × 1G | Both | |
| RIX Reykjavik, Iceland | 10G | Both | |
| RoNIX Bucharest, Romania | 10G | PeeringDB | |
| RTIX Tallinn, Estonia | 1G | PeeringDB | |
| SAIX Saudi Arabia Riyadh Riyadh, Saudi Arabia | 10G | Both | |
| SFINX Paris, France | 10G | PeeringDB | |
| SFMIX San Francisco, United States | 10G | Both | |
| SIX Seattle Seattle, United States | 10G | Both | |
| SIX SI Ljubljana, Slovenia | 10G | Both | |
| SOX Serbia Belgrade/Serbia, Serbia | 1G | PeeringDB | |
| SpringIX Springfield, MO, United States | 1G | Both | |
| STHIX - Stockholm Stockholm, Sweden | 1G | PeeringDB | |
| STLIX Saint Louis, MO, United States | 1G | Both | |
| SwissIX Zurich, Switzerland | 10G | Both | |
| TIX Tromsø Tromsø, Norway | 100G | PeeringDB | |
| TPIX-TW Taipei/Taiwan, Taiwan | 10G | PeeringDB | |
| TTIX2 Princes Town, Trinidad and Tobago | 10G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 1G | Both | |
| VANIX Vancouver, Canada | 10G | Both | |
| VIX Vienna, Austria | 10G | Both | |
| VIX.VU Port Vila, Vanuatu | 2 × 1G | Both | |
| VSIX Padova, Italy | 10G | Both | |
| WLG-IX (Wellington NZ) Wellington, New Zealand | 10G | Both | |
| YYCIX Calgary, Canada | 10G | Both |
These exchanges have a switch in a facility where Netnod lists itself in PeeringDB, but don't have Netnod 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.
| EVIXFremont, United States | 227 | |
| FREMIXFremont, United States | 141 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| ARIXFremont, Portland, Flagstaff, United States | 22 | |
| Lambda-IXFremont, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| DACS-IX WestSilicon Valley, United States | 14 | |
| Ninja-IX Bay AreaNorthern California, United States | 6 | |
| ixFabricGlobal, Australia | 2 |
Facilities (1)
The buildings Netnod lists in PeeringDB, and how many of the exchanges in each it's on.
| Hurricane Electric Fremont 2Fremont | 2 of 12 |
Recent changes Search them
- Nov 5, 2026 [IXF] AS8674 Netnod now on VSIX's IX-F list
- Oct 29, 2026 [PDB] AS8674 Netnod added to VSIX
- Oct 14, 2026 [IXF] AS8674 Netnod now on Netnod Stockholm BLUE -- MTU1500's IX-F list