Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group): PeeringDB fix list
AS64597
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-10-08 18:53 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.
From ixreport.com/net/64597/: 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.