Skip to main content

AS138663

AVM-MY

AVM Cloud Sdn. Bhd.

Registry

Authoritative registration data

AS number
138663
Name
AVM-MY
Organisation
AVM Cloud Sdn. Bhd.
Country
Flag of Malaysia MY Malaysia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS138663
103.106.6.0/24 IPv4 /24 not checked
103.106.7.0/24 IPv4 /24 not checked
103.117.164.0/24 IPv4 /24 not checked
103.117.165.0/24 IPv4 /24 not checked
203.78.162.0/24 IPv4 /24 not checked
43.239.204.0/24 IPv4 /24 not checked
43.239.205.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 AS138663
Address families
MyIX 1,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 AS138663 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS138663 in AS paths

Observed upstreams
Families
AS9930 TTNET-MY 592 2,703
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS138663 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
AS55720 GIGABIT-MY 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.