VDS Availability Diagnostics

To check server availability from an external network, we recommend using the following tools:

  • WinMTR for Windows
  • MTR for Linux-based systems

These tools allow you to trace the route traffic takes from your computer to the server and help identify nodes where delays or packet loss occur.


WinMTR

Instructions for using WinMTR are provided in a separate article. In the Host field, enter your server’s IP address or domain name.


MTR

In most operating systems, MTR is not installed by default. To install it, use the following commands:

Ubuntu/Debian:

sudo apt-get install mtr

CentOS/Fedora:

yum install mtr

After installation, run the utility using:

mtr domain.ru


Analysis of Results

1. Traffic reached the destination without any packet loss

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  218 |  218 |    1 |    4 |  113 |    1 |
|                              172.16.1.2 -    0 |  218 |  218 |    1 |    4 |  130 |    3 |
|                              172.16.1.9 -    0 |  218 |  218 |    2 |    5 |  108 |    3 |
|         bb-center-g2-237.net.ttc-net.ru -    0 |  218 |  218 |    2 |    4 |   24 |    2 |
|          bb-south-ge-189.net.ttc-net.ru -    0 |  218 |  218 |    2 |    6 |  117 |    2 |
|                          217.21.222.252 -    0 |  218 |  218 |    2 |    9 |  187 |    6 |
|                            79.104.52.37 -    0 |  218 |  218 |    2 |    6 |  105 |    5 |
|                    pe06.Moscow.gldn.net -    0 |  218 |  218 |    3 |    7 |   47 |    4 |
|         beeline-gw.moscow.rostelecom.ru -    0 |  218 |  218 |    3 |    8 |  109 |    4 |
|                          213.59.212.223 -    0 |  218 |  218 |    2 |    7 |  122 |    5 |
|                           5.143.221.250 -    0 |  218 |  218 |    2 |    6 |  119 |    3 |
|                       MSK-CTV-R2.nic.ru -    0 |  218 |  218 |    3 |   12 |  197 |    4 |
|                       MSK-DP-GW1.nic.ru -    0 |  218 |  218 |    4 |   11 |  180 |    5 |
|                          185.26.114.131 -    0 |  218 |  218 |    3 |    7 |   99 |    5 |

This means the server is accessible from the external network. If you are experiencing issues with website functionality, we recommend contacting your system administrator.

2. Some traffic was lost on the ISP’s nodes

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                            217.173.16.4 -    0 |  142 |  141 |   20 |   58 |  251 |   50 |

|                      gw1-ge1.KZN.TBT.RU -    0 |  141 |  141 |   10 |   46 |  201 |   20 |

|                           217.66.22.177 -    3 |  141 |  138 |   10 |   45 |  161 |   20 |

|                      gw1-ge2.KZN.TBT.RU -    0 |  141 |  141 |   10 |   43 |  201 |   20 |

|                          83.229.243.101 -   11 |  141 |  126 |   20 |   45 |  150 |   30 |

|          MSK-B1-HQ-0-0-0.0.rusmedia.net -   12 |  141 |  124 |   50 |   88 |  210 |  150 |

|             msk-bgw1-ae0-128.rt-comm.ru -    8 |  141 |  130 |   60 |   92 |  280 |   80 |

|             msk-dsr13-ge1-24.rt-comm.ru -   13 |  141 |  123 |   60 |  116 |  510 |  120 |

|             msk-dsr13-ge1-24.rt-comm.ru -   12 |  141 |  125 |   60 |  144 | 1652 |  141 |

|                          195.161.158.14 -    9 |  141 |  129 |   60 |  129 | 1552 |  110 |

|                     MSK-M9-MR3.ripn.net -    0 |  141 |  141 |   60 |  110 |  310 |  120 |

|                        KHOUSE-H1.nic.ru -    0 |  141 |  141 |   60 |  114 |  290 |  100 |

|                            195.208.0.15 -    0 |  141 |  141 |   60 |  114 |  290 |   90 |

If there is packet loss on the connection, access to the server may be intermittent. To determine the cause, we recommend contacting your Internet service provider.

3. Traffic reached only the internal nic.ru network

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  194 |  194 |    1 |    4 |   36 |    3 |
|                              172.16.1.2 -    0 |  194 |  194 |    1 |    6 |  211 |    1 |
|                              172.16.1.9 -    0 |  194 |  194 |    2 |    5 |   33 |    2 |
|         bb-center-g2-237.net.ttc-net.ru -    0 |  194 |  194 |    2 |    6 |   19 |    4 |
|          bb-south-ge-189.net.ttc-net.ru -    0 |  194 |  194 |    2 |    6 |   34 |    3 |
|                          217.21.222.252 -    0 |  194 |  194 |    2 |   11 |  206 |    4 |
|                            79.104.52.37 -    0 |  194 |  194 |    2 |    7 |   33 |    4 |
|                    pe26.Moscow.gldn.net -    0 |  194 |  194 |    3 |    7 |   32 |    4 |
|                           79.133.94.225 -    0 |  194 |  194 |    3 |   10 |   53 |    3 |
|                          213.59.212.223 -    0 |  194 |  194 |    3 |    7 |   33 |    3 |
|                           5.143.251.250 -    0 |  194 |  194 |    3 |    7 |   33 |    3 |
|                       MSK-CTV-R2.nic.ru -    0 |  194 |  194 |    3 |   12 |  173 |    5 |
|                       MSK-DP-GW1.nic.ru -    0 |  194 |  194 |    4 |   15 |  639 |    5 |
|                   No response from host -  100 |   40 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   40 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   40 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   40 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   40 |    0 |    0 |    0 |    0 |    0 |

This may be related to your server configuration. For example, a firewall may be blocking UDP or ICMP traffic (ping).

For further diagnostics, we recommend connecting to the server via the virtual console and checking its configuration.

Connecting to a VDS Server
How to Reboot a VDS Server
 

Всё ещё остались вопросы?