Reliance Jio Infocomm Singapore: PeeringDB fix list
AS64049 · peeringdb.com/net/6758
4 things to fix in Reliance Jio Infocomm Singapore's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Reliance Jio Infocomm Singapore'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 (3)
On the exchange's own member list, but not in Reliance Jio Infocomm Singapore's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.72.211.123 IPv6 2001:504:13::211:123 Speed Not published RS peer Not published -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members listIPv4 185.0.20.206 IPv6 2001:7f8:7f::206 Speed 12500 Mbps (12.5G) RS peer No
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 185.1.47.23 185.1.47.23 185.1.47.50 IPv6 address missing from PeeringDB 2001:7f8:36::fa31:0:1 2001:7f8:36::fa31:0:1 2001:7f8:36::fa31:0:2 - Add an entry: IPv4 185.1.47.50, IPv6 2001:7f8:36::fa31:0:2, speed 100000 (100G), RS peer yes.
From ixreport.com/net/64049/: 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.