B-Tel Internet pvt Ltd: PeeringDB fix list

AS58765 · peeringdb.com/net/10635

PeeringDB

3 things to fix in B-Tel Internet pvt Ltd's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on B-Tel Internet pvt 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 B-Tel Internet pvt 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 (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. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs10G7G
    • In the entry with IPv4 103.27.170.79: set Speed to 7000 (7G) (now 10000).
  2. ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:df2:1900:1::68none
    • In the entry with IPv4 45.120.248.68: set IPv6 to (empty) (now 2001:df2:1900:1::68).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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