asn.dev

Interconnection

AS4800 LINTASARTA-AS-AP PT Aplikanusa Lintasarta

Hosting RIPE

Exchanges 12 12 active
Countries 6 most in Indonesia
Regions 3
Largest fabric 2,071 OpenIXP Internet exchange Point

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
OpenIXP Internet exchange PointJakarta, Indonesia218.100.36.108Open2,071
Indonesian Internet Exchange (IIX-Jakarta)Jakarta, Indonesia123.108.8.215Open951
LINX LON1London, United Kingdom195.66.226.132Open931
AMS-IX AmsterdamAmsterdam, Netherlands80.249.214.190Open882
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.228.33Open496
Coresite - Any2 WestLos Angeles, United States206.72.211.60Open344
Any2 CaliforniaLos Angeles, United States206.72.211.60Open319
Hong Kong Internet ExchangeHong Kong, China123.255.90.49Open307
Singapore Internet ExchangeSingapore, Singapore103.16.102.83Open277
Alien Internet ExchangeDepok, Indonesia43.254.82.30Open249
EdgeNXT Internet ExchangeJakarta, Indonesia103.61.232.10Open130
Digital Edge EPIX JakartaJakarta, Indonesia202.159.50.8Open86

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.