Skip to main content

AS49052

DATAZYX

DATA ZYX SRL

Registry

Authoritative registration data

AS number
49052
Name
DATAZYX
Organisation
DATA ZYX SRL
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS49052
185.128.240.0/22 IPv4 /22 not checked
80.96.228.0/23 IPv4 /23 not checked
81.180.236.0/23 IPv4 /23 not checked
80.96.111.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 AS49052
Address families
InterLAN-IX: InterLAN Peering Network 2,000 Mbps IPv4

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 AS49052 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS49052 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 262 1,176
v4
AS6939 HURRICANE 20 63
v4
AS14840 ASN14840 2 15
v4
AS20764 RASCOM-AS 3 9
v4
AS47734 TELECOM-IT-SOLUTIONS-AS 2 6
v4
AS8708 DIGI-RO 1 3
v4
AS21215 UGNI 1 3
v4
AS22356 ASN22356 1 3
v4
AS263444 ASN263444 1 3
v4
AS12310 iNES 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49052 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

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.