ixreport

Airnet Cable And Datacom Pvt Ltd: PeeringDB fix list

AS133001 · peeringdb.com/net/13000

PeeringDB

3 things to fix in Airnet Cable And Datacom Pvt Ltd's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Airnet Cable And Datacom 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 Airnet Cable And Datacom Pvt Ltd's PeeringDB record. Add one entry per connection with these values.

  1. India Extreme IX Delhi Delhi, India · PeeringDB 1323From 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.

    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.

  1. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    Port speed differs10G10G + 2G
    • In the entry with IPv4 103.27.170.160: set Speed to 2000 (2G) (now 10000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Airnet Cable And Datacom Pvt Ltd has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. India Extreme IX Mumbai Mumbai, India · PeeringDB 1627Not on its IX-F export
    IPv4103.77.108.223
    IPv6–
    Speed30000 Mbps (30G)

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