ixreport

Tier 4 Cloud Services: PeeringDB fix list

AS146943 · peeringdb.com/net/39621

PeeringDB

2 things to fix in Tier 4 Cloud Services'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 Tier 4 Cloud Services'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. ProblemPeeringDB hasThe export has
    Port speed differs10G3 × 10G

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Tier 4 Cloud Services 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.5
    IPv62001:df2:1900:2::5
    Speed10000 Mbps (10G)

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