Skip to main content

AS153615

APNIC ASN block

APNIC ASN block

Registry

Authoritative registration data

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

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS153615
163.61.134.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 AS153615
Address families
AIX 1,000 Mbps IPv4
DE-CIX ASEAN 10,000 Mbps IPv4 · IPv6
DE-CIX Jakarta 10,000 Mbps IPv4
EdgeNXT 10,000 Mbps IPv4 · IPv6
IIX-Jakarta 10,000 Mbps IPv4 · IPv6
JKT-IX: Main 1,000 Mbps IPv4
Metta-IX 1,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 AS153615 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS153615 in AS paths

Observed upstreams
Families
AS58389 SDI-NAP-AS-ID 540 751
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS153615 in AS paths

Observed downstreams
Families
AS153147 SALMA-AS-ID 269 377
v4
AS151581 2 2
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 3
v4
AS35280 F5 3 3
v4
AS151581 1 1
v4
AS153147 SALMA-AS-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.