Skip to main content

AS44668

ZNET

Znet

Registry

Authoritative registration data

AS number
44668
Name
ZNET
Organisation
Znet
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

2

Total announced

13

Announced prefixes

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

Prefixes announced by AS44668
176.122.88.0/21 IPv4 /21 not checked
77.87.40.0/21 IPv4 /21 not checked
185.11.80.0/22 IPv4 /22 not checked
185.255.48.0/22 IPv4 /22 not checked
193.194.112.0/22 IPv4 /22 not checked
195.18.28.0/22 IPv4 /22 not checked
46.33.44.0/22 IPv4 /22 not checked
91.202.104.0/22 IPv4 /22 not checked
193.168.51.0/24 IPv4 /24 not checked
193.168.55.0/24 IPv4 /24 not checked
195.5.126.0/24 IPv4 /24 not checked
2a0c:5940::/29 IPv6 /29 RPKI valid
2a0c:5940::/48 IPv6 /48 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 AS44668
Address families
UA-IX 10,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 AS44668 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS44668 in AS paths

Observed upstreams
Families
AS34056 KIEVNET 401 2,160
v4 v6
AS174 COGENT-174 79 552
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS44668 in AS paths

Observed downstreams
Families
AS41027 NETEXPERT-AS 163 198
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS48919 UA-CITY-AS 2 12
v4
AS49544 i3Dnet 2 12
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.