Eaton Kaye Ltd
AS34746
Tools: Where can I peer with Eaton Kaye Ltd? · Where should Eaton Kaye Ltd peer next? · Compare Eaton Kaye Ltd with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
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-11-19 12:40 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.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
Map
Where Eaton Kaye Ltd'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.
| LINX LON1 London, United Kingdom | 100M | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| LINX LON2 London, United Kingdom | 10G | Not in PeeringDB | |
| LONAP London, United Kingdom | 3 × 10G | Not in PeeringDB |
These exchanges have a switch in a facility where Eaton Kaye Ltd lists itself in PeeringDB, but don't have Eaton Kaye Ltd 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.
Facilities (1)
The buildings Eaton Kaye Ltd lists in PeeringDB, and how many of the exchanges in each it's on.
| Telehouse - London (Docklands East)London | 3 of 6 |