ixreport

Gigantic Infotel Pvt Ltd: PeeringDB fix list

AS133275 · peeringdb.com/net/11729

PeeringDB

2 things to fix in Gigantic Infotel Pvt Ltd's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Gigantic Infotel 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 (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
    IPv4 address in PeeringDB, not in the export103.27.170.213 103.27.171.2103.27.170.213
    IPv6 address in PeeringDB, not in the export2401:7500:fff6::2c 2401:7500:fff6::2132401:7500:fff6::213
    Port speed differs2 × 10G3G
    • In the entry with IPv4 103.27.170.213: set Speed to 3000 (3G) (now 10000).
    • The entry with IPv4 103.27.171.2, IPv6 2401:7500:fff6::2c isn't in the export: delete it if that connection is gone.
  2. India Extreme IX Delhi Delhi, India · PeeringDB 1323
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 45.120.248.22: set Speed to 100000 (100G) (now 10000).

    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/133275/: 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.