ixreport

ETO Networks

AS214731

ETO Networks Limited

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Educational/ResearchType
OpenPeering policy
6Using the route servers
2To fix in PeeringDB
1Facility in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

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

Make the changes on ETO Networks'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 (2)

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 Kawaii IX AMS Amsterdam, Netherlands · PeeringDB 4973
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone195.60.92.74
    • In the entry with IPv6 2602:f93b:1a35:1311::74: set IPv4 to 195.60.92.74 (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.

  2. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.0.24.216
    • In the entry with IPv6 2001:7f8:aa::216: set IPv4 to 185.0.24.216 (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

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

Map

Where ETO Networks'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 24G across 6 exchanges.

Germany 91-IX Frankfurt, Germany 2001:7f8:1a:91::102 10G Yes PeeringDB
United States FREMIX Fremont, United States 2001:504:125:e0::9e 1G Yes Both
Netherlands Kawaii IX AMS Amsterdam, Netherlands 2602:f93b:1a35:1311::74 1G Up, 0 routes Both IPv4 not in PeeringDB
United Kingdom Kent Internet Exchange Point Kent, United Kingdom 2001:7f8:aa::216 10G Yes Both IPv4 not in PeeringDB
United Kingdom LONAP London, United Kingdom 5.57.82.158 2001:7f8:17::3:46cb:1 1G 7 routes Both
Hong Kong ZXIX Hong Kong Hong Kong, Hong Kong 2406:840:1f:1000:0:21:4731:1 1G Yes PeeringDB
Facilities (1)

The buildings ETO Networks lists in PeeringDB, and how many of the exchanges in each it's on.

United Kingdom Vinters ConnectMaidstone 1 of 1