Tata Teleservices: PeeringDB fix list

AS45820 · peeringdb.com/net/14387

PeeringDB

4 things to fix in Tata Teleservices's PeeringDB record, from what its exchanges publish: 4 to add. As of 2026-10-08 20:58 UTC.

Make the changes on Tata Teleservices'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 (4)

On the exchange's own member list, but not in Tata Teleservices's PeeringDB record. Add one entry per connection with these values.

  1. India DE-CIX Chennai Chennai, India · PeeringDB 2588From its IX-F export
    IPv4103.228.174.68
    IPv62400:d180:68::68
    Speed1000 Mbps (1G)
    RS peerYes
  2. India DE-CIX Delhi Delhi, India · PeeringDB 2587From 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.

  3. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From its IX-F export
    IPv4103.27.171.168
    IPv6–
    Speed10000 Mbps (10G)
    RS peerYes
  4. 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.

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