Skip to main content

AS137576

EASYCOMMUNICATE-AS-AP

EasyCable Pty Ltd

Registry

Authoritative registration data

AS number
137576
Name
EASYCOMMUNICATE-AS-AP
Organisation
EasyCable 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 AS137576
103.114.12.0/22 IPv4 /22 not checked
2402:c7c0::/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 AS137576
Address families
EdgeIX - Sydney: Main 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 AS137576 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS137576 in AS paths

Observed upstreams
Families
AS136557 HOST-AS-AP 675 971
v4 v6
AS6939 HURRICANE 34 40
v4
AS24516 VIRTUTEL-AS-AP 19 27
v4 v6
AS64073 VETTA 2 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS137576 in AS paths

Observed downstreams
Families
AS133429 PHOENIX-AS-AP 247 359
v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 3
v4 v6
AS49544 i3Dnet 2 3
v4 v6
AS132847 NETSG-AS-AP 2 3
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.