Skip to main content

AS139466

LCHS-AS-AP

LATROBE COMMUNITY HEALTH SERVICE LIMITED

Registry

Authoritative registration data

AS number
139466
Name
LCHS-AS-AP
Organisation
LATROBE COMMUNITY HEALTH SERVICE LIMITED
Country
Flag of Australia AU Australia
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 AS139466
103.141.199.0/24 IPv4 /24 not checked
2402:6820::/32 IPv6 /32 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 AS139466
Address families
EdgeIX - Melbourne: Main 10,000 Mbps IPv4 · IPv6
MegaIX Melbourne: MegaIX 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 AS139466 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS139466 in AS paths

Observed upstreams
Families
AS4764 AUSSIEFIBRE-AS-AP 162 232
v4 v6
AS137409 GSLNETWORKS-AS-AP 98 123
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS139466 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 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.