Skip to main content

AS58096

Elit-TV-AS

Viter Evgeniy Vasilevich

Registry

Authoritative registration data

AS number
58096
Name
Elit-TV-AS
Organisation
Viter Evgeniy Vasilevich
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

0

Total announced

11

Announced prefixes

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

Prefixes announced by AS58096
168.222.204.0/22 IPv4 /22 not checked
185.154.72.0/22 IPv4 /22 not checked
185.33.228.0/22 IPv4 /22 not checked
195.170.204.0/22 IPv4 /22 not checked
45.93.4.0/22 IPv4 /22 not checked
94.141.124.0/22 IPv4 /22 not checked
185.216.192.0/23 IPv4 /23 not checked
193.160.204.0/23 IPv4 /23 not checked
193.105.114.0/24 IPv4 /24 not checked
91.213.168.0/24 IPv4 /24 not checked
91.220.69.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 AS58096
Address families
GNM-IX 80,000 Mbps IPv4
MSK-IX Moscow: MSK-IX peering network — IPv4
PITER-IX Frankfurt 100,000 Mbps IPv4
PITER-IX Helsinki 100,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 100,000 Mbps IPv4
PITER-IX Rostov 100,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 100,000 Mbps IPv4
Sea-IX 20,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 AS58096 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS58096 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS58096 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 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.