Skip to main content

AS137032

IRIS-AS-AP

Iris Communications Pty Ltd

Registry

Authoritative registration data

AS number
137032
Name
IRIS-AS-AP
Organisation
Iris Communications Pty Ltd
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS137032
103.102.164.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 AS137032
Address families
EdgeIX - Brisbane: Main 10,000 Mbps IPv4 · IPv6
IX Australia Brisbane (QLD-IX): QLD-IX 10,000 Mbps IPv4 · IPv6
MegaIX Brisbane: 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 AS137032 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS137032 in AS paths

Observed upstreams
Families
AS49915 MEGAPORT 190 229
v4
AS6939 HURRICANE 35 39
v4
AS10143 EXETEL-AS-AP 5 5
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS137032 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
AS4608 APNIC-SERVICES 1 1
v4
AS132847 NETSG-AS-AP 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.