Skip to main content

AS138984

SLT-NW2

Sri Lanka Telecom Ltd

Registry

Authoritative registration data

AS number
138984
Name
SLT-NW2
Organisation
Sri Lanka Telecom Ltd
Country
Flag of Sri Lanka LK Sri Lanka
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

3

Total announced

7

Announced prefixes

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

Prefixes announced by AS138984
112.134.56.0/22 IPv4 /22 not checked
112.134.60.0/22 IPv4 /22 not checked
203.96.160.0/22 IPv4 /22 not checked
203.96.160.0/23 IPv4 /23 not checked
2402:d000:1000::/36 IPv6 /36 not checked
2402:d000:42::/48 IPv6 /48 not checked
2402:d000:43::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS138984 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS138984 in AS paths

Observed upstreams
Families
AS45489 SLT-GLOBAL 646 1,717
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS138984 in AS paths

Observed downstreams
Families
AS400318 VERSA-01 257 339
v4
AS151485 CEB-AS-AP 17 21
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS38229 LEARN-LK 1 2
v4

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.