Skip to main content

AS153526

LMCSCL-AS-AP

01-00027433

Registry

Authoritative registration data

AS number
153526
Name
LMCSCL-AS-AP
Organisation
01-00027433
Country
Flag of Laos LA Laos
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

15

IPv6 prefixes

1

Total announced

16

Announced prefixes

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

Prefixes announced by AS153526
157.85.32.0/20 IPv4 /20 RPKI valid
157.85.48.0/20 IPv4 /20 not checked
203.77.168.0/21 IPv4 /21 not checked
45.197.152.0/22 IPv4 /22 RPKI valid
45.221.100.0/22 IPv4 /22 not checked
161.248.192.0/23 IPv4 /23 RPKI valid
203.77.168.0/23 IPv4 /23 not checked
203.77.170.0/23 IPv4 /23 RPKI valid
203.77.172.0/23 IPv4 /23 not checked
203.77.174.0/23 IPv4 /23 not checked
203.77.168.0/24 IPv4 /24 RPKI valid
203.77.169.0/24 IPv4 /24 not checked
203.77.170.0/24 IPv4 /24 not checked
203.77.174.0/24 IPv4 /24 not checked
203.77.175.0/24 IPv4 /24 not checked
2401:e9a0::/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 AS153526
Address families
BBIX Thailand: Main 10,000 Mbps IPv4 · IPv6
BKNIX (Thailand): Bangkok 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 AS153526 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS153526 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 273 1,369
v4 v6
AS45629 JASTEL-NETWORK-TH-AP 285 1,215
v4
AS6939 HURRICANE 121 563
v4 v6
AS38082 IIT-TIG-AS-AP 100 385
v4
AS63529 BKNIX-RS-AP 10 52
v4
AS9505 TWGATE-AP 2 7
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS153526 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 17
v4 v6

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.