ixreport

Skylink Fibernet Private Limited: PeeringDB fix list

AS135139 · peeringdb.com/net/17242

PeeringDB

3 things to fix in Skylink Fibernet Private Limited's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Skylink Fibernet Private Limited'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 (3)

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 Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2400:d180:68::83
    Port speed differs10G1G
    • In the entry with IPv4 103.228.174.83: set IPv6 to 2400:d180:68::83 (now empty); set Speed to 1000 (1G) (now 10000).
  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2401:7500:fff6::b9
    Port speed differs10G10G + 3G
    • In the entry with IPv4 103.27.171.183: set IPv6 to 2401:7500:fff6::b9 (now empty); set Speed to 3000 (3G) (now 10000).
  3. India Extreme IX Delhi Delhi, India · PeeringDB 1323
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 45.120.248.175: set Speed to 10000 (10G) (now 1000).

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