Wouldn't the same risk be present if the servers that host the nodes are leased by the same provider?

I have seen it rebuilts something but after hours i see that the progress was killed.
When i type

bitcoind

it returns this

Error: Unable to bind to 0.0.0.0:8333 on this computer. Bitcoin is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.

Subject: Cron <root@spirosbitcoin> pythonusr/local/bin/btc-update.py
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>

Traceback (most recent call last):
  File "/usr/local/bin/btc-update.py", line 7, in <module>
    info = access.getinfo()
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 120, in __call__
    response = self._get_response()
  File "/usr/local/lib/python2.7/dist-packages/bitcoinrpc/authproxy.py", line 140, in _get_response
    http_response = self.__conn.getresponse()
  File "/usr/lib/python2.7/httplib.py", line 1045, in getresponse
    response.begin()
  File "/usr/lib/python2.7/httplib.py", line 409, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.7/httplib.py", line 365, in _read_status
    line = self.fp.readline(_MAXLINE + 1)
  File "/usr/lib/python2.7/socket.py", line 476, in readline
    data = self._sock.recv(self._rbufsize)
socket.timeout: timed out

You need to use the bitcoin-cli to interact with the bitcoind.

Bitcoin-cli comes in the same zip as bitcoind, and it is the only way way to interact with the bitcoind from the command line.

Well, it' not down since you linked us to http://69.12.86.115/ it shows 8 active connections.

It could be an issue with the server itself, assuming you did the VPS, correct?