Skip to main content

AS45240

NETWIDE-AU-AS-AP

REA Group, A subsidiary of Netwide,

Registry

Authoritative registration data

AS number
45240
Name
NETWIDE-AU-AS-AP
Organisation
REA Group, A subsidiary of Netwide,
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS45240
103.66.26.0/23 IPv4 /23 not checked
203.13.23.0/24 IPv4 /24 not checked
203.17.253.0/24 IPv4 /24 not checked
2001:df2:7700::/48 IPv6 /48 RPKI not found

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 AS45240
Address families
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 AS45240 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS45240 in AS paths

Observed upstreams
Families
AS15830 Equinix 225 627
v4 v6
AS6939 HURRICANE 16 48
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS45240 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 4
v4 v6
AS35280 F5 1 3
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.