Skip to main content

AS38790

XYZTELECOM-AS-AP

XYZ Telecom Pty Ltd

Registry

Authoritative registration data

AS number
38790
Name
XYZTELECOM-AS-AP
Organisation
XYZ Telecom Pty Ltd
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS38790
Address families
EdgeIX - Sydney: Main 10,000 Mbps IPv4 · IPv6
IX Australia Brisbane (QLD-IX): QLD-IX 10,000 Mbps IPv4 · IPv6
IX Australia Melbourne (VIC-IX): VIC-IX 10,000 Mbps IPv4
IX Australia Sydney (NSW-IX): NSW-IX 10,000 Mbps IPv4
MegaIX Brisbane: MegaIX 10,000 Mbps IPv4 · IPv6
MegaIX Melbourne: MegaIX 10,000 Mbps IPv4 · IPv6
MegaIX Sydney: 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 AS38790 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS38790 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 211 872
v4 v6
AS64073 VETTA 5 24
v4 v6
AS55850 MERCURYNZ-AS-AP 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS38790 in AS paths

Observed downstreams
Families
AS9336 XYZTELECOM-AS-AP 156 930
v4
AS55573 XYZTELECOM-AS-AP 97 121
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 8 35
v4 v6
AS4608 APNIC-SERVICES 7 33
v4
AS132847 NETSG-AS-AP 7 26
v4 v6
AS24482 SGGS-AS-AP 6 25
v4 v6
AS35280 F5 4 23
v4
AS36236 NETACTUATE 3 11
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.