SPEED LINK COMMUNICATIONS: PeeringDB fix list

AS147285 · peeringdb.com/net/43021

PeeringDB

One thing to fix in SPEED LINK COMMUNICATIONS's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on SPEED LINK COMMUNICATIONS'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 Extreme IX Chennai Chennai, India · PeeringDB 1786
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G
    • The entry with IPv4 45.120.251.151, IPv6 – isn't in the export: delete it if that connection is gone.

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