Skip to main content

AS202371

ZALNETWORK

ZAL Network S.r.l.

Registry

Authoritative registration data

AS number
202371
Name
ZALNETWORK
Organisation
ZAL Network S.r.l.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS202371
80.173.140.0/22 IPv4 /22 RPKI valid
185.133.127.0/24 IPv4 /24 not checked
2.56.131.0/24 IPv4 /24 not checked
94.185.119.0/24 IPv4 /24 not checked
94.185.120.0/24 IPv4 /24 not checked
94.185.121.0/24 IPv4 /24 RPKI valid
94.185.122.0/24 IPv4 /24 RPKI valid

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 AS202371
Address families
MIX-IT 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 AS202371 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS202371 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 71 539
v4
AS203201 IT-SUPERNAP 58 435
v4
AS6939 HURRICANE 11 76
v4
AS8218 NEO-ASN 3 28
v4
AS14840 ASN14840 2 28
v4
AS4455 BSO 1 7
v4
AS29075 IELO 1 7
v4
AS31543 MYNET-AS 1 7
v4
AS263444 ASN263444 1 7
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS202371 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 21
v4
AS12779 ITGATE 1 7
v4
AS13237 LAMBDANET-AS 1 7
v4
AS24961 MYLOC-AS 1 7
v4
AS49544 i3Dnet 1 7
v4
AS59919 BRAINBOX 1 7
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.