ixreport

Krishiinet Infocom: PeeringDB fix list

AS135845 · peeringdb.com/net/15367

PeeringDB

One thing to fix in Krishiinet Infocom's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Krishiinet Infocom'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
    IPv6 address missing from PeeringDBnone2401:7500:fff6::2
    Port speed differs1.024G3G
    • In the entry with IPv4 103.27.170.2: set IPv6 to 2401:7500:fff6::2 (now empty); set Speed to 3000 (3G) (now 1024).

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