Skip to main content

AS153839

APNIC ASN block

APNIC ASN block

Registry

Authoritative registration data

AS number
153839
Name
—
Organisation
APNIC ASN block
Country
—
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS153839
163.227.100.0/24 IPv4 /24 RPKI valid
2001:df5:61c0::/48 IPv6 /48 RPKI valid

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 AS153839
Address families
BIX Jakarta 10,000 Mbps IPv4 · IPv6
CXC Jakarta 1,000 Mbps IPv4 · IPv6
IIX-Jakarta 10,000 Mbps IPv4 · IPv6
JKT-IX: Main 10,000 Mbps IPv4 · IPv6
ODIX Omadata 10,000 Mbps IPv4 · IPv6

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

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS153839 in AS paths

Observed upstreams
Families
AS38158 CBN-AS-ID 320 622
v4 v6
AS138840 HSP-NAP-AS-ID 93 125
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS153839 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

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