Skip to main content

AS18153

MULTIDATA-ID-AP

PT Multidata Rancana Prima

Registry

Authoritative registration data

AS number
18153
Name
MULTIDATA-ID-AP
Organisation
PT Multidata Rancana Prima
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS18153
202.72.192.0/24 IPv4 /24 not checked
202.72.193.0/24 IPv4 /24 not checked
202.72.195.0/24 IPv4 /24 not checked
202.72.196.0/24 IPv4 /24 not checked
202.72.200.0/24 IPv4 /24 not checked
202.72.201.0/24 IPv4 /24 not checked
202.72.202.0/24 IPv4 /24 not checked
202.72.206.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS18153 in AS paths

Observed upstreams
Families
AS136106 FIBERSTAR-AS-ID 291 3,016
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS18153 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS56246 SDI-AS-ID 1 8
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.