asn.dev

Interconnection

AS55821 RADIUSTELECOMS-AS-AP RADIUS TELECOMS, INC.

Unclassified APNIC NSP

Exchanges 11 11 active
Countries 4 most in Philippines
Regions 2
Largest fabric 496 Equinix Internet Exchange Singapore

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS55821, 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 9 North America 2

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.230.122Open496
Coresite - Any2 WestLos Angeles, United States206.72.211.221Open344
Any2 CaliforniaLos Angeles, United States206.72.211.221Open319
Hong Kong Internet ExchangeHong Kong, China123.255.91.166Open307
Singapore Internet ExchangeSingapore, Singapore103.16.102.226Open277
Equinix Internet Exchange Hong KongHong Kong, China2001:de8:7::5:5821:1Open232
GetaFIX ManilaManila, Philippines103.104.19.83Open133
BroadBand Internet eXchange Hong KongHong Kong, China103.203.158.182Open101
Maharlika Internet ExchangeManila, Philippines163.223.201.39Open65
Philippine Open Internet ExchangeManila, Philippines198.32.172.56Open48
GetaFIX CebuCebu, Philippines116.89.244.9—9

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.