Skip to main content

AS149976

ADSNETWORK-AS-ID

PT Adhelin Data Solution

Registry

Authoritative registration data

AS number
149976
Name
ADSNETWORK-AS-ID
Organisation
PT Adhelin Data Solution
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS149976
103.157.62.0/24 IPv4 /24 not checked
103.157.63.0/24 IPv4 /24 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 AS149976
Address families
IIX-Jakarta 10,000 Mbps IPv4 · IPv6
JKT-IX: Main 50,000 Mbps IPv4 · IPv6
OpenIXP / NiCE 10,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS149976 in AS paths

Observed upstreams
Families
AS38158 CBN-AS-ID 237 304
v4
AS24198 DATAKOMNAP-AS-ID 191 223
v4
AS138089 GMDP-AS-ID 44 52
v4
AS150506 IDNIC-PFI-AS-ID 9 10
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS149976 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

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