Skip to main content

AS142125

CAPTI-AS-AP

Capti Networks Pty Ltd

Registry

Authoritative registration data

AS number
142125
Name
CAPTI-AS-AP
Organisation
Capti Networks Pty Ltd
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 AS142125
103.166.148.0/24 IPv4 /24 not checked
103.166.149.0/24 IPv4 /24 not checked
2001:df6:9380::/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 AS142125
Address families
IX Australia Brisbane (QLD-IX): QLD-IX 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 AS142125 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS142125 in AS paths

Observed upstreams
Families
AS7594 ONQ-AS-AP 222 494
v4 v6
AS6939 HURRICANE 226 374
v4 v6
AS148968 FALCORE-AS-AP 206 277
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS142125 in AS paths

Observed downstreams
Families
AS152893 FIBOSSPTYLTD-AS-AP 240 313
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS132847 NETSG-AS-AP 1 3
v4 v6
AS4608 APNIC-SERVICES 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.