ixreport

Renesys Corporation (a.k.a. Oracle/Renesys Internet Intelligence Group)

AS64597

2Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
1Using the route servers
4To fix in PeeringDB

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.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export
    IPv480.81.194.211
    IPv62001:7f8::fc55:0:1
    Speed1000 Mbps (1G)
    RS peerYes
  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export
    IPv4195.66.225.224
    IPv62001:7f8:4::fc55:1
    Speed10000 Mbps (10G)
    RS peerNo

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB80.81.194.211 is AS34135 Renesys80.81.194.211
    Address belongs to another network in PeeringDB2001:7f8::fc55:0:1 is AS34135 Renesys2001: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.

  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB195.66.225.224 is AS34135 Renesys195.66.225.224
    Address belongs to another network in PeeringDB2001:7f8:4::fc55:1 is AS34135 Renesys2001: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

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

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.

Exchanges

Total port capacity 11G across 2 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.194.211 2001:7f8::fc55:0:1 1G Yes Not in PeeringDB Address taken
United Kingdom LINX LON1 London, United Kingdom 195.66.225.224 2001:7f8:4::fc55:1 10G Not in PeeringDB Address taken