FTP connection error

ping resolves ftpupload.net to 185.27.134.11. ping got no response. proably configured to not respond. scan port 21 on ftpupload.net is open so server exists tracert to ftpupload.net stops at 242.3.84.197 or 171.75.9.67 not a usr/pwd issue because would get descriptive error, as with other servers not a host not found issue because would get descriptive error, as with other servers not a firewall issue because other hosts work, other ftp clients work, and tested w/ firewall off tried all servers with all modes: ftpupload.net explicit TLS/SSL port 21, connection fail implicit TLS/SSL port 990, connection fail no encryption port 21, connection fail ftp.infinityfree.com explicit TLS/SSL port 21, connection fail implicit TLS/SSL port 990, connection fail, actively refused no encryption port 21, success 185.27.134.11 explicit TLS/SSL port 21, connection fail, timeout implicit TLS/SSL port 990, connection fail, actively refused no encryption port 21, success ftp.epizy.com explicit TLS/SSL port 21, success implicit TLS/SSL port 990, connection fail, actively refused no encryption port 21, success tried ftpupload.net explicit TLS/SSL port 21 file transfer active/passive/auto connection fail on all modes tried ftp.epizy.com SCP port 22, connection refused SFTP port 22, connection refused webdav implicit port 443, connection fail, actively refused webdav no encryption port 80, connection fail, actively refused summary: 1. ftpupload.net connection fail on all modes. server exists, port 21 open, tracert fails. 2. ftp.infinityfree.com and 185.27.134.11 success with no encryption, all other modes no work 3. ftp.epizy.com success with explicit or no encryption. conclusion: 1. ftpupload.net FUBAR, needs fixed 2. ftp.infinityfree.com and 185.27.134.11 also need fix or reconfigure 3. use ftp.epizy.com as an alternate until ftpupload.net is fixed actions: fix your FTP servers