Eaton Kaye Ltd: PeeringDB fix list
AS34746 · peeringdb.com/net/500
3 things to fix in Eaton Kaye Ltd's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Eaton Kaye Ltd'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 Eaton Kaye Ltd's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.66.236.222 IPv6 2001:7f8:4:1::87ba:1 Speed 10000 Mbps (10G) RS peer Yes -
3 connections, so 3 entries:
IPv4 5.57.80.180 IPv6 – Speed 10000 Mbps (10G) RS peer Yes IPv4 5.57.80.181 IPv6 – Speed 10000 Mbps (10G) RS peer Yes IPv4 5.57.80.179 IPv6 – Speed 10000 Mbps (10G) 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.
Correct these entries (1)
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 missing from PeeringDB 195.66.224.222 195.66.224.222 195.66.227.232 IPv6 address missing from PeeringDB none 2001:7f8:4::87ba:1 2001:7f8:4::87ba:2 Port speed differs 100M 2 × 10G - In the entry with IPv4 195.66.224.222: set IPv6 to 2001:7f8:4::87ba:1 (now empty); set Speed to 10000 (10G) (now 100).
- Add an entry: IPv4 195.66.227.232, IPv6 2001:7f8:4::87ba:2, speed 10000 (10G), RS peer yes.
From ixreport.com/net/34746/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.