Skip to main content

AS39067

Etanetas

ETANETAS UAB

Registry

Authoritative registration data

AS number
39067
Name
Etanetas
Organisation
ETANETAS UAB
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS39067
94.232.224.0/21 IPv4 /21 not checked
185.160.143.0/24 IPv4 /24 not checked
94.232.231.0/24 IPv4 /24 not checked
2a0d:1580:10::/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 AS39067
Address families
BALT-IX: BALT-IX 10,000 Mbps IPv4
LIXP: public peering vlan 10,000 Mbps IPv4
Litix: Litix 1,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 AS39067 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS39067 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 438 869
v4 v6
AS6939 HURRICANE 274 570
v4
AS3303 SWISSCOM 14 30
v4
AS210175 LIPTA-AS 2 4
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS39067 in AS paths

Observed downstreams
Families
AS44246 BITOSIS 272 377
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS1257 SWIPNET 1 2
v4
AS21412 CGATES-AS 1 2
v4
AS28917 Fiord-AS 1 2
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.