asn.dev

Observed topology

AS152144 LAPL-AS-AP LIGHTSTORM ASIA PTE. LTD.

Upstreams 13 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 20
Adjacent (IPv6) 14

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152144: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv698
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv627
AS6939Hurricane Electric LLCTransitIPv416
AS174Cogent Communications, LLCTransitIPv63
AS24482SG.GSHostingIPv4 IPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv63
AS38001NewMedia Express Pte LtdHostingIPv42
AS56662Marcin GondekUnclassifiedIPv61
AS61292Blix Group ASUnclassifiedIPv61
AS34549meerfarbig GmbH & Co. KGHostingIPv61
AS34019Hivane AssociationUnclassifiedIPv61
AS205794JINZE YANGUnclassifiedIPv61
AS58057Securebit AGUnclassifiedIPv61

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you.

Transit

Downstream networks

inferred

Networks for which AS152144 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS141047Nepal Digital Service Pvt. Ltd.UnclassifiedIPv4 IPv61,075
AS134922R G TECHNOSOLUTIONS PVT LTDResidentialIPv4 IPv6248
AS135709Lightstorm Telecom Connectivity Private LimitedUnclassifiedIPv4177
AS38029Citibank N.A. - ISP Peering, Chennai, IndiaUnclassifiedIPv440

Adjacency

Adjacent networks

35 shown

Every AS seen directly next to AS152144 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS141047Nepal Digital Service Pvt. Ltd.UnclassifiedIPv4 IPv620,445
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv66,373
AS174Cogent Communications, LLCTransitIPv4 IPv64,994
AS2914NTT America, Inc.TransitIPv4 IPv63,433
AS6939Hurricane Electric LLCTransitIPv41,977
AS134922R G TECHNOSOLUTIONS PVT LTDResidentialIPv4 IPv6905
AS58057Securebit AGUnclassifiedIPv4 IPv6815
AS135709Lightstorm Telecom Connectivity Private LimitedUnclassifiedIPv4 IPv6530
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6529
AS24482SG.GSHostingIPv4 IPv6453
AS34019Hivane AssociationUnclassifiedIPv4 IPv6409
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6397
AS50673Serverius Holding B.V.UnclassifiedIPv4358
AS38001NewMedia Express Pte LtdHostingIPv4357
AS34927iFog GmbHHostingIPv4354
AS206499LOCIX LIMITEDUnclassifiedIPv4349
AS20764CJSC RASCOMUnclassifiedIPv4277
AS37721Virtual Technologies & SolutionsResidentialIPv4176
AS56662Marcin GondekUnclassifiedIPv6109
AS205794JINZE YANGUnclassifiedIPv6100
AS61292Blix Group ASUnclassifiedIPv699
AS38029Citibank N.A. - ISP Peering, Chennai, IndiaUnclassifiedIPv440
AS9498BHARTI Airtel Ltd.MobileIPv415

Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS152144, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 3 exchanges across 2 countries and 2 regions.

ExchangeLocationTheir addressMember ports
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.230.229490
Singapore Internet ExchangeSingapore, Singapore103.16.102.138273
NetIXSofia, Bulgaria185.1.226.196264

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: 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 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.