Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group)
AS64597
This network has no PeeringDB record; it was found on exchanges' own member lists.
Tools: Where can I peer with Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group)? · Where should Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group) peer next? · Compare Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group) with another network
PeeringDB fix list Printable page · CSV
4 things to fix in Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group)'s PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-11-19 12:40 UTC.
AS64597 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (2)
On the exchange's own member list, but not in Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group)'s PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.81.194.211 IPv6 2001:7f8::fc55:0:1 Speed 1000 Mbps (1G) RS peer Yes -
IPv4 195.66.225.224 IPv6 2001:7f8:4::fc55:1 Speed 10000 Mbps (10G) RS peer No
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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 80.81.194.211 is AS34135 Renesys 80.81.194.211 Address belongs to another network in PeeringDB 2001:7f8::fc55:0:1 is AS34135 Renesys 2001:7f8::fc55:0:1 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 195.66.225.224 is AS34135 Renesys 195.66.225.224 Address belongs to another network in PeeringDB 2001:7f8:4::fc55:1 is AS34135 Renesys 2001:7f8:4::fc55:1 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 2 |
| Nov 18, 2026 | 2 |
| Nov 17, 2026 | 2 |
| Nov 16, 2026 | 2 |
| Nov 15, 2026 | 2 |
| Nov 14, 2026 | 2 |
| Nov 13, 2026 | 2 |
| Nov 12, 2026 | 2 |
| Nov 11, 2026 | 2 |
| Nov 10, 2026 | 2 |
| Nov 9, 2026 | 2 |
| Nov 8, 2026 | 2 |
| Nov 7, 2026 | 2 |
| Nov 6, 2026 | 2 |
| Nov 5, 2026 | 2 |
| Nov 4, 2026 | 2 |
| Nov 3, 2026 | 2 |
| Nov 2, 2026 | 2 |
| Nov 1, 2026 | 2 |
| Oct 31, 2026 | 2 |
| Oct 30, 2026 | 2 |
| Oct 29, 2026 | 2 |
| Oct 28, 2026 | 2 |
| Oct 27, 2026 | 2 |
| Oct 26, 2026 | 2 |
| Oct 25, 2026 | 2 |
| Oct 24, 2026 | 2 |
| Oct 23, 2026 | 2 |
| Oct 22, 2026 | 2 |
| Oct 21, 2026 | 1 |
| Oct 20, 2026 | 2 |
| Oct 19, 2026 | 2 |
| Oct 18, 2026 | 2 |
| Oct 17, 2026 | 2 |
| Oct 16, 2026 | 2 |
| Oct 15, 2026 | 2 |
| Oct 14, 2026 | 2 |
| Oct 13, 2026 | 2 |
| Oct 12, 2026 | 2 |
| Oct 11, 2026 | 2 |
| Oct 10, 2026 | 2 |
| Oct 9, 2026 | 2 |
| Oct 8, 2026 | 2 |
| Oct 7, 2026 | 2 |
| Oct 6, 2026 | 2 |
| Oct 5, 2026 | 2 |
| Oct 4, 2026 | 2 |
| Oct 3, 2026 | 2 |
Map
Where Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group)'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.
| DE-CIX Frankfurt Frankfurt, Germany | 1G | Not in PeeringDB Address taken | |
| LINX LON1 London, United Kingdom | 10G | Not in PeeringDB Address taken |