ixreport

SHERIE PLEXUS ISP: PeeringDB fix list

AS135234 · peeringdb.com/net/14082

PeeringDB

2 things to fix in SHERIE PLEXUS ISP's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on SHERIE PLEXUS ISP's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in SHERIE PLEXUS ISP's PeeringDB record. Add one entry per connection with these values.

  1. India AMS-IX Mumbai Mumbai, India · PeeringDB 1623From its IX-F export
    IPv4223.31.200.72
    IPv6–
    Speed1000 Mbps (1G)
    RS peerYes

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

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
    Port speed differs1G1.5G
    • In the entry with IPv4 103.27.170.98: set Speed to 1500 (1.5G) (now 1000).

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