Skip to main content

AS152144

LAPL-AS-AP

LIGHTSTORM ASIA PTE. LTD.

Registry

Authoritative registration data

AS number
152144
Name
LAPL-AS-AP
Organisation
LIGHTSTORM ASIA PTE. LTD.
Country
Flag of Singapore SG Singapore
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS152144
210.87.106.0/24 IPv4 /24 not checked
210.87.107.0/24 IPv4 /24 not checked
223.31.200.0/24 IPv4 /24 not checked
2401:5760::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS152144
Address families
Equinix Singapore 100,000 Mbps IPv4 · IPv6
NetIX: NetIX 100,000 Mbps IPv4 · IPv6
SGIX: Peering LAN 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS152144 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

38 networks seen before AS152144 in AS paths

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS152144 in AS paths

Observed downstreams
Families
AS141047 NDSPL-AS-AP 18,225 134,728
v4 v6
AS134922 RGTECHNOSOLUTIONS-AS 3,146 5,977
v4 v6
AS135709 LTCIN-AS-IN 267 1,034
v4
AS38029 CITI-IN-ISP_PEER 9 26
v4

No rows match “”.

Showing – of

Uncertain adjacencies

39 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.