Skip to main content

AS149915

LINTASDAYA-AS-ID

PT Lintas Daya Nusantara

Registry

Authoritative registration data

AS number
149915
Name
LINTASDAYA-AS-ID
Organisation
PT Lintas Daya Nusantara
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS149915
103.189.254.0/24 IPv4 /24 not checked
2001:df3:fac0::/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

Internet Exchange memberships listed for AS149915
Address families
JKT-IX Surabaya 10,000 Mbps IPv4 · IPv6
JKT-IX: Main 10,000 Mbps IPv4 · IPv6
NIX Surabaya 40,000 Mbps IPv4
ODIX Omadata 10,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 AS149915 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS149915 in AS paths

Observed upstreams
Families
AS58389 SDI-NAP-AS-ID 351 612
v4 v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS149915 in AS paths

Observed downstreams
Families
AS154023 IDNIC-GUT-AS-ID 8 8
v4
AS149913 IDNIC-OOFYDI-AS-ID 2 2
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 3
v4 v6
AS35280 F5 2 3
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.