ixreport

NetNext

AS215212

10Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Network ServicesType
OpenPeering policy
9Using the route servers
5To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with NetNext? · Where should NetNext peer next? · Compare NetNext with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

5 things to fix in NetNext's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on NetNext'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 NetNext's PeeringDB record. Add one entry per connection with these values.

  1. United States F4IX MCI Kansas City, United States · PeeringDB 4378From its IX-F export
    IPv4–
    IPv62602:fa3d:f4:1::c0
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. United States NVIX Ashburn, United States · PeeringDB 4462From its website members list
    IPv4–
    IPv62001:504:125:e2::b
    SpeedNot published
    RS peerNot published

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.

  1. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.160.14: set Speed to 10000 (10G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.184.233: set Speed to 100000 (100G) (now 1000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  3. Canada ONIX Toronto, Canada · PeeringDB 4059
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:504:125:e1::bcb2001:504:125:e1::155
    IPv4 address missing from PeeringDBnone149.112.50.155
    • In the entry with IPv6 2001:504:125:e1::bcb: set IPv4 to 149.112.50.155 (now empty); set IPv6 to 2001:504:125:e1::155 (now 2001:504:125:e1::bcb).

    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

0246810Oct 3, 2026Nov 19, 202610
Show as a table
DateExchanges
Nov 19, 202610
Nov 18, 202610
Nov 17, 202610
Nov 16, 202610
Nov 15, 202610
Nov 14, 202610
Nov 13, 202610
Nov 12, 202610
Nov 11, 202610
Nov 10, 202610
Nov 9, 202610
Nov 8, 202610
Nov 7, 202610
Nov 6, 202610
Nov 5, 202610
Nov 4, 202610
Nov 3, 202610
Nov 2, 202610
Nov 1, 202610
Oct 31, 202610
Oct 30, 202610
Oct 29, 202610
Oct 28, 202610
Oct 27, 202610
Oct 26, 202610
Oct 25, 20269
Oct 24, 20269
Oct 23, 20269
Oct 22, 202610
Oct 21, 202610
Oct 20, 202610
Oct 19, 202610
Oct 18, 202610
Oct 17, 202610
Oct 16, 202610
Oct 15, 202610
Oct 14, 202610
Oct 13, 202610
Oct 12, 202610
Oct 11, 202610
Oct 10, 202610
Oct 9, 202610
Oct 8, 202610
Oct 7, 202610
Oct 6, 202610
Oct 5, 202610
Oct 4, 202610
Oct 3, 202610

Map

Where NetNext'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.

Exchanges

Total port capacity 8.1G, at the 9 of 10 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 2001:7f8:d0::3:48ac:1 1G Yes Both
Spain Barcelona-IX Barcelona, Spain 193.201.150.213 2001:7f8:93:1:0:21:5212:1 1G Yes Both
United States F4IX MCI Kansas City, United States 2602:fa3d:f4:1::c0 1G Yes Not in PeeringDB
Switzerland FogIXP Avers, Switzerland 185.1.147.13 2001:7f8:ca:1:0:21:5212:1 1G Yes Both
United States FREMIX Fremont, United States 149.112.29.73 2001:504:125:e0::73 1G Yes Both
Netherlands Frys-IX Fryslân, Netherlands 185.1.160.14 2001:7f8:10f::3:48ac:14 1G 7 routes Both Speed differs
Netherlands INTERIX Amsterdam, Netherlands 185.1.184.233 2001:7f8:134::e9 1G 7 routes Both Speed differs
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.116.78 2001:7f8:13::a521:5212:1 100M Yes Both
United States NVIX Ashburn, United States 2001:504:125:e2::b Not in PeeringDB
Canada ONIX Toronto, Canada 2001:504:125:e1::bcb 1G Yes Both IPv6 differsIPv4 not in PeeringDB

NetNext lists no facilities in PeeringDB.