Skip to main content

AS141384

ISAL-AS-AP

Internet Society Asia Limited

Registry

Authoritative registration data

AS number
141384
Name
ISAL-AS-AP
Organisation
Internet Society Asia Limited
Country
Flag of Singapore SG Singapore
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 AS141384
103.162.142.0/24 IPv4 /24 not checked
2001:df6:780::/48 IPv6 /48 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 AS141384
Address families
IX Australia Sydney (NSW-IX): NSW-IX 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 AS141384 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS141384 in AS paths

Observed upstreams
Families
AS138466 469 648
v4 v6
AS6939 HURRICANE 35 40
v4
AS64073 VETTA 1 2
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS141384 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 2
v4 v6
AS36236 NETACTUATE 1 2
v4 v6
AS49544 i3Dnet 1 2
v4 v6
AS132847 1 2
v4 v6
AS35280 F5 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.