ixreport

Rapidnet Pvt Ltd: PeeringDB fix list

AS135799 · peeringdb.com/net/12175

PeeringDB

3 things to fix in Rapidnet Pvt Ltd's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Rapidnet 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 Delhi Delhi, India · PeeringDB 2587
    ProblemPeeringDB hasThe export has
    Port speed differs3G10G + 10M
    • In the entry with IPv4 103.27.168.55: set Speed to 10 (10M) (now 3000).
  2. ProblemPeeringDB hasThe export has
    Port speed differs10G100G + 10G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Rapidnet Pvt Ltd 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 Delhi Delhi, India · PeeringDB 1323Not on its IX-F export
    IPv445.120.248.32
    IPv62001:df2:1900:1::32
    Speed100000 Mbps (100G)

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