Skip to main content

AS142049

LAUNCH-AS-AP

Launch Crew Pty Ltd

Registry

Authoritative registration data

AS number
142049
Name
LAUNCH-AS-AP
Organisation
Launch Crew Pty Ltd
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS142049
103.165.180.0/24 IPv4 /24 not checked
165.101.211.0/24 IPv4 /24 not checked
2402:19e0::/32 IPv6 /32 not checked
2001:df6:6e80::/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 AS142049
Address families
EdgeIX - Sydney: Main 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 AS142049 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS142049 in AS paths

Observed upstreams
Families
AS9507 NEXTHOP-AS-AP 438 1,306
v4 v6
AS6939 HURRICANE 30 68
v4
AS64073 2 8
v4 v6
AS24482 SGGS-AS-AP 2 6
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS142049 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
AS49544 i3Dnet 1 4
v4 v6
AS132847 1 4
v4 v6
AS35280 F5 1 2
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.