SREEDEVI COMMUNICATIONS: PeeringDB fix list
AS142470 · peeringdb.com/net/27512
2 things to fix in SREEDEVI COMMUNICATIONS's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on SREEDEVI COMMUNICATIONS'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 SREEDEVI COMMUNICATIONS's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.115.147.112 IPv6 2001:de8:c000::112 Speed 1000 Mbps (1G) RS peer Not published 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.
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.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 103.228.174.230 103.228.174.231 103.228.174.232 103.228.174.230 103.228.174.232 IPv6 address in PeeringDB, not in the export 2400:d180:68::d 2400:d180:68::e 2400:d180:68::f 2400:d180:68::d 2400:d180:68::e Port speed differs 10G + 3G + 1G 2 × 11G + 3G - In the entry with IPv4 103.228.174.230: set Speed to 11000 (11G) (now 10000).
- The entry with IPv4 103.228.174.231, IPv6 2400:d180:68::f isn't in the export: delete it if that connection is gone.
From ixreport.com/net/142470/: 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.