ixreport

Sampath Venkateswara Communications: PeeringDB fix list

AS134305 · peeringdb.com/net/16113

PeeringDB

2 things to fix in Sampath Venkateswara Communications's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Sampath Venkateswara 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. ProblemPeeringDB hasThe export has
    Port speed differs3G2 × 10G
    • In the entry with IPv4 45.120.251.121: set Speed to 10000 (10G) (now 3000).

    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 Sampath Venkateswara Communications 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 Hyderabad Hyderabad, India · PeeringDB 1785Not on its IX-F export
    IPv4103.77.110.21
    IPv62001:df2:1900:4::21
    Speed10000 Mbps (10G)

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