Skip to main content

AS151976

CFNPL-AS-AP

CoreFibre Networks Pty Ltd

Registry

Authoritative registration data

AS number
151976
Name
CFNPL-AS-AP
Organisation
CoreFibre Networks Pty Ltd
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS151976
103.67.56.0/23 IPv4 /23 not checked
2401:47a0::/32 IPv6 /32 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 AS151976
Address families
EdgeIX - Melbourne: Main 10,000 Mbps IPv4 · IPv6
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 AS151976 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS151976 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 252 374
v4 v6
AS49915 MEGAPORT 138 164
v4
AS9507 NEXTHOP-AS-AP 108 157
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS151976 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 2
v4 v6
AS132847 NETSG-AS-AP 1 2
v4 v6
AS35280 F5 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.