NetNext
AS215212
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.
-
IPv4 – IPv6 2602:fa3d:f4:1::c0 Speed 1000 Mbps (1G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 – IPv6 2001:504:125:e2::b Speed Not published RS peer Not 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.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - 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.
-
Problem PeeringDB has The export has Port speed differs 1G 100G - 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.
-
Problem PeeringDB has The export has IPv6 address differs 2001:504:125:e1::bcb 2001:504:125:e1::155 IPv4 address missing from PeeringDB none 149.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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 10 |
| Nov 3, 2026 | 10 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 9 |
| Oct 24, 2026 | 9 |
| Oct 23, 2026 | 9 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
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.
| 4b42 Internet Exchange Point Zurich, Switzerland | 1G | Both | |
| Barcelona-IX Barcelona, Spain | 1G | Both | |
| F4IX MCI Kansas City, United States | 1G | Not in PeeringDB | |
| FogIXP Avers, Switzerland | 1G | Both | |
| FREMIX Fremont, United States | 1G | Both | |
| Frys-IX Fryslân, Netherlands | 1G | Both Speed differs | |
| INTERIX Amsterdam, Netherlands | 1G | Both Speed differs | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 100M | Both | |
| NVIX Ashburn, United States | Not in PeeringDB | ||
| ONIX Toronto, Canada | 1G | Both IPv6 differsIPv4 not in PeeringDB |
NetNext lists no facilities in PeeringDB.