Oracle Cloud Infrastructure: PeeringDB fix list
AS31898 · peeringdb.com/net/1905
3 things to fix in Oracle Cloud Infrastructure's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Oracle Cloud Infrastructure'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 (1)
On the exchange's own member list, but not in Oracle Cloud Infrastructure's PeeringDB record. Add one entry per connection with these values.
-
IPv4 91.210.17.28 IPv6 2001:7f8:14::20:1 Speed 10000 Mbps (10G) RS peer No 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 IPv6 address in PeeringDB, not in the export 2001:7f8:b:100:1d1:a5d3:1898:27 none - In the entry with IPv4 217.29.66.27: set IPv6 to (empty) (now 2001:7f8:b:100:1d1:a5d3:1898:27).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Oracle Cloud Infrastructure has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 101.203.89.147 IPv6 2001:de8:c::3:1898:1 Speed 200000 Mbps (200G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/31898/: 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.