Skip to main content

AS153836

SOLITARY-AS-AP

Solitary Technology

Registry

Authoritative registration data

AS number
153836
Name
SOLITARY-AS-AP
Organisation
Solitary Technology
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS153836
163.227.185.0/24 IPv4 /24 not checked
163.8.201.0/24 IPv4 /24 not checked
2001:df5:77c0::/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 AS153836
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 AS153836 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS153836 in AS paths

Observed upstreams
Families
AS136557 HOST-AS-AP 412 793
v4 v6
AS24516 VIRTUTEL-AS-AP 75 211
v4 v6
AS64073 VETTA 1 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS153836 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 v6
AS132847 NETSG-AS-AP 1 3
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.