Interconnection

AS58717 SUMMITCOMMUNICATIONS-BD Summit Communications Ltd

Unclassified APNIC

Exchanges 9 9 active

Countries 6 most in Singapore

Regions 2

Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS58717, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.

Asia-Pacific 7 Europe 2

Exchange	Location	Their address	Policy	Member ports
DE-CIX Frankfurt	Frankfurt, Germany	80.81.192.208	Selective	1,078
Equinix Internet Exchange Singapore	Singapore, Singapore	27.111.228.8	Selective	496
BroadBand Internet eXchange Tokyo	Tokyo, Japan	101.203.91.13	Selective	361
Hong Kong Internet Exchange	Hong Kong, China	123.255.92.88	Selective	307
DE-CIX Mumbai	Mumbai, India	103.27.170.72	Selective	277
Singapore Internet Exchange	Singapore, Singapore	103.16.102.35	Selective	277
BroadBand Internet eXchange Singapore	Singapore, Singapore	103.231.152.149	Selective	157
DE-CIX Marseille	Marseille, France	185.1.47.82	Selective	112
BroadBand Internet eXchange Hong Kong	Hong Kong, China	103.203.158.133	Selective	101

Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.

From the exchange directory collected 2026-10-13 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,177 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.