Skip to main content

AS132394

OPUSV-AU

OpusV Technology Group

Registry

Authoritative registration data

AS number
132394
Name
OPUSV-AU
Organisation
OpusV Technology Group
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS132394
103.232.216.0/23 IPv4 /23 not checked
103.20.20.0/24 IPv4 /24 not checked
103.232.159.0/24 IPv4 /24 not checked
202.0.150.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 AS132394
Address families
MegaIX Melbourne: MegaIX 500 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 AS132394 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS132394 in AS paths

Observed upstreams
Families
AS2764 233 995
v4
AS140627 ONEQODEASSETS-AS-AP 33 188
v4
AS6939 HURRICANE 35 160
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS132394 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
AS24482 SGGS-AS-AP 1 4
v4
AS35280 F5 1 4
v4
AS132847 1 4
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.