ixreport

Allnet Broadband Network Pvt Ltd: PeeringDB fix list

AS135724 · peeringdb.com/net/11501

PeeringDB

2 things to fix in Allnet Broadband Network Pvt Ltd's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Allnet Broadband Network 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.

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
    IPv4 address in PeeringDB, not in the export103.27.170.84 103.27.171.64103.27.170.84
    IPv6 address in PeeringDB, not in the export2401:7500:fff6::84 2401:7500:fff6::9b2401:7500:fff6::84
    Port speed differs10G + 2G2G
    • In the entry with IPv4 103.27.170.84: set Speed to 2000 (2G) (now 10000).
    • The entry with IPv4 103.27.171.64, IPv6 2401:7500:fff6::9b isn't in the export: delete it if that connection is gone.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Allnet Broadband Network 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.114
    IPv62001:df2:1900:2::114
    Speed3000 Mbps (3G)

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