Skip to main content

AS64024

YESIMEDIA-AS-ID

PT Yesi Media Utama

Registry

Authoritative registration data

AS number
64024
Name
YESIMEDIA-AS-ID
Organisation
PT Yesi Media Utama
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS64024
103.210.116.0/24 IPv4 /24 not checked
103.210.117.0/24 IPv4 /24 not checked
103.210.118.0/24 IPv4 /24 not checked
103.210.119.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 AS64024
Address families
IIX-Jakarta 100,000 Mbps IPv4
JKT-IX: Main 40,000 Mbps IPv4
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 AS64024 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS64024 in AS paths

Observed upstreams
Families
AS147094 MVNET-AS-ID 231 1,192
v4
AS64315 IDNIC-CLOUD-INDO-AS-ID 16 64
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS64024 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 4
v4
AS35280 F5 1 4
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.