Skip to main content

AS151567

TUNASMEDIADATA-AS-ID

PT Tunas Media Data

Registry

Authoritative registration data

AS number
151567
Name
TUNASMEDIADATA-AS-ID
Organisation
PT Tunas Media Data
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 AS151567
103.38.104.0/24 IPv4 /24 not checked
103.38.105.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 AS151567
Address families
AIX 1,000 Mbps IPv4
IIX-Jakarta 10,000 Mbps IPv4
JKT-IX: Main 1,000 Mbps IPv4
OpenIXP / NiCE 1,000 Mbps IPv4
Transhybrid IX Network 3,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 AS151567 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS151567 in AS paths

Observed upstreams
Families
AS24534 TRANSHYBRID-AS-ID 277 709
v4
AS38158 CBN-AS-ID 42 60
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS151567 in AS paths

Observed downstreams
Families
AS153805 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

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