Skip to main content

AS49724

VAINAHTELECOM-AS

JSC Vainah Telecom

Registry

Authoritative registration data

AS number
49724
Name
VAINAHTELECOM-AS
Organisation
JSC Vainah Telecom
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

20

IPv6 prefixes

0

Total announced

20

Announced prefixes

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

Prefixes announced by AS49724
188.0.160.0/19 IPv4 /19 not checked
188.0.160.0/20 IPv4 /20 not checked
188.0.176.0/21 IPv4 /21 not checked
188.0.184.0/22 IPv4 /22 not checked
91.215.220.0/22 IPv4 /22 not checked
188.0.166.0/23 IPv4 /23 not checked
188.0.190.0/23 IPv4 /23 not checked
91.215.222.0/23 IPv4 /23 not checked
188.0.162.0/24 IPv4 /24 not checked
188.0.169.0/24 IPv4 /24 not checked
188.0.174.0/24 IPv4 /24 not checked
188.0.175.0/24 IPv4 /24 not checked
188.0.178.0/24 IPv4 /24 not checked
188.0.179.0/24 IPv4 /24 not checked
188.0.183.0/24 IPv4 /24 not checked
188.0.186.0/24 IPv4 /24 not checked
188.0.188.0/24 IPv4 /24 not checked
188.0.189.0/24 IPv4 /24 not checked
91.215.220.0/24 IPv4 /24 not checked
91.215.221.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

25 networks seen before AS49724 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS49724 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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