ixreport

SREEDEVI COMMUNICATIONS

AS142470 · SREEDEVI COMMUNICATION PVT LTD

SREEDEVI COMMUNICATIONS PRIVATE LIMITED

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with SREEDEVI COMMUNICATIONS? · Where should SREEDEVI COMMUNICATIONS peer next? · Compare SREEDEVI COMMUNICATIONS with another network

This network elsewhere: the registry history of AS142439-AS142538, the block AS142470 is in, on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in SREEDEVI COMMUNICATIONS's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 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.

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 Chennai Chennai, India · PeeringDB 2588
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export103.228.174.230 103.228.174.231 103.228.174.232103.228.174.230 103.228.174.232
    IPv6 address in PeeringDB, not in the export2400:d180:68::d 2400:d180:68::e 2400:d180:68::f2400:d180:68::d 2400:d180:68::e
    Port speed differs10G + 3G + 1G2 × 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.

Exchanges over time

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20262
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
Oct 30, 20262
Oct 29, 20262
Oct 28, 20262
Oct 27, 20262
Oct 26, 20262
Oct 25, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where SREEDEVI COMMUNICATIONS's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 15G across 2 exchanges.

India Amaravati IX Amaravati, India 103.115.147.112 2001:de8:c000::112 1G Both
India DE-CIX Chennai Chennai, India 103.228.174.230
103.228.174.231
103.228.174.232
2400:d180:68::d
2400:d180:68::e
2400:d180:68::f
10G + 3G + 1G Yes Both IPv4 not in exportIPv6 not in exportSpeed differs

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where SREEDEVI COMMUNICATIONS lists itself in PeeringDB, but don't have SREEDEVI COMMUNICATIONS as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

India Extreme IX ChennaiChennai, India 91 TATA Communications Chennai; STTGDC CHN1
India NIXI ChennaiChennai, India 56 STTGDC CHN1
India REDIX ChennaiChennai, India 2 TATA Communications Chennai; Netmagic Chennai
Facilities (3)

The buildings SREEDEVI COMMUNICATIONS lists in PeeringDB, and how many of the exchanges in each it's on.

India STTGDC CHN1Chennai 1 of 3
India TATA Communications ChennaiChennai 1 of 3
India Netmagic ChennaiChennai 1 of 2

Recent changes Search them

  • Nov 6, 2026 [PDB] AS142470 SREEDEVI COMMUNICATIONS now in PeeringDB at Amaravati IX