ONEOTT iNTERTAINMENT LTD: PeeringDB fix list

AS17665 · peeringdb.com/net/5167

PeeringDB

4 things to fix in ONEOTT iNTERTAINMENT LTD's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on ONEOTT iNTERTAINMENT LTD'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 ONEOTT iNTERTAINMENT LTD's PeeringDB record. Add one entry per connection with these values.

  1. India Extreme IX Pune Pune, India · PeeringDB 4805From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (3)

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. India DE-CIX Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    Port speed differs30G20G + 2 × 10G
    • In the entry with IPv4 103.27.168.84: set Speed to 20000 (20G) (now 30000).
  2. India DE-CIX Kolkata Kolkata, India · PeeringDB 2589
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 103.228.172.32: set Speed to 1000 (1G) (now 10000).
  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs20G30G
    • In the entry with IPv4 103.27.170.132: set Speed to 30000 (30G) (now 20000).

From ixreport.com/net/17665/: 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.