asn.dev

Interconnection

AS40676 AS40676 - Psychz Networks

Hosting ARIN

Exchanges 12 12 active
Countries 8 most in United States
Regions 5
Largest fabric 2,704 IX.br (PTT.br) São Paulo

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS40676, 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 5 North America 3 Africa 2 Europe 1 Latin America 1

ExchangeLocationTheir addressPolicyMember ports
IX.br (PTT.br) São PauloSão Paulo, Brazil187.16.222.139Open2,704
NAPAfrica IX JohannesburgJohannesburg, South Africa196.60.9.20Open603
MSK-IX MoscowMoscow, Russia195.208.208.180—505
BroadBand Internet eXchange TokyoTokyo, Japan2001:de8:c::4:676:1Open361
Coresite - Any2 WestLos Angeles, United States206.72.211.46Open344
Any2 CaliforniaLos Angeles, United States206.72.211.46Open319
Equinix Internet Exchange ChicagoChicago, United States208.115.137.52Open282
DE-CIX MumbaiMumbai, India103.27.170.33Open278
Extreme IX MumbaiMumbai, India103.77.108.74Open242
Johannesburg Internet ExchangeJohannesburg, South Africa196.60.96.168Open217
Taipei Internet Exchange (TPIX)Taipei, Taiwan203.163.222.68Open190
Korea Internet Neutral Exchange KINXSeoul, South Korea139.150.100.179—64

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-11 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,138 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.