asn.dev

Internet exchange

DE-CIX Hyderabad

active Hyderabad, India

Recorded members 28 addresses on file
Connected ports 8 across all participants
Peak traffic Not reported no figure on file
Peering LANs 2 shared subnets

Overview

What this is

recorded

An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.

Location
Hyderabad, India
Region
Asia-Pacific
Status
Active

Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.

Fabric

Peering LANs

2 on file

The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.

PrefixFamilyStatusParticipants
103.83.68.0/24IPv4Active8
2400:d180:72::/64IPv6Active8

Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.

Participants

Member networks

28 shown

Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS54113Fastly, Inc.2400:d180:72::22Open
AS54113Fastly, Inc.103.83.68.22Open
AS42WoodyNet, Inc.103.83.68.11Open
AS42WoodyNet, Inc.2400:d180:72::9Open
AS32934Facebook, Inc.103.83.68.157Open
AS32934Facebook, Inc.103.83.68.158Open
AS32934Facebook, Inc.2400:d180:72::158Open
AS32934Facebook, Inc.2400:d180:72::157Open
AS3856Packet Clearing House, Inc.103.83.68.10Open
AS3856Packet Clearing House, Inc.2400:d180:72::8Open
AS132215Powergrid Teleservices Limited2400:d180:72::7Open
AS132215Powergrid Teleservices Limited103.83.68.7Open
AS53813ZSCALER, INC.2400:d180:72::4Open
AS53813ZSCALER, INC.2400:d180:72::5Open
AS53813ZSCALER, INC.103.83.68.4Open
AS53813ZSCALER, INC.103.83.68.5Open
AS45884RVR Infrastructure Limited Service provider hyderabad india2400:d180:72::20Open
AS45884RVR Infrastructure Limited Service provider hyderabad india103.83.68.20Open
AS59185NETRUN TECHNOLOGIES PVT LTD2400:d180:72::c5Open
AS59173Iqtera Communication Pvt Ltd2400:d180:72::68Open
AS133304Hitech Broadband2400:d180:72::2cOpen
AS141259Flynet Online Solutions Pvt Ltd2400:d180:72::16Open
AS142575Rediff.com India Limited103.83.68.12Open
AS142575Rediff.com India Limited2400:d180:72::12Open
AS9437NIXI103.83.68.65Open
AS9437NIXI2400:d180:72::64Open
AS9437NIXI2400:d180:72::65Open
AS9437NIXI103.83.68.64Open

Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.

Provenance

Where this comes from

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member addresses, licensed CC BY-NC-SA 3.0.

This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. 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.