All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Help |How critical is this packet loss
Hello LET people,
I have a dedicated server which has a packet loss since few days. it's really helpful if an expert give me an advice what to do on this issue.
From Client to Server
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.8.1 - 0 | 1227 | 1227 | 2 | 15 | 151 | 4 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| 125.214.190.148 - 1 | 1223 | 1222 | 18 | 44 | 571 | 24 |
| 125.214.162.139 - 4 | 1087 | 1050 | 126 | 156 | 723 | 153 |
| decix2.ovhcloud.com - 1 | 1223 | 1222 | 146 | 181 | 975 | 149 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| be102.rbx-g3-nc5.fr.eu - 1 | 1215 | 1212 | 152 | 182 | 1050 | 167 |
| lon-thw-sbb1-nc5.uk.eu - 1 | 1219 | 1217 | 156 | 187 | 1057 | 171 |
| nyc-ny1-sbb1-8k.nj.us - 80 | 297 | 62 | 0 | 258 | 403 | 278 |
| be102.bhs-g1-nc5.qc.ca - 1 | 1223 | 1222 | 231 | 267 | 1138 | 239 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 247 | 0 | 0 | 0 | 0 | 0 |
| Destination IP - 0 | 1226 | 1226 | 236 | 264 | 1147 | 240 |
|________________________________________________|______|______|______|______|______|______|
From Server to client
|------------------------------------------------|------|------|------|------|------|------|
| X.X.X.X - 0 | 1157 | 1157 | 0 | 0 | 12 | 0 |
| 10.34.66.64 - 0 | 1157 | 1157 | 0 | 0 | 6 | 0 |
| 10.74.8.114 - 0 | 1157 | 1157 | 0 | 0 | 6 | 0 |
| 10.95.81.10 - 1 | 1138 | 1133 | 0 | 2 | 371 | 0 |
| nyc-ny1-sbb2-8k.nj.us - 90 | 255 | 27 | 0 | 9 | 12 | 10 |
| be104.lon-drch-sbb1-nc5.uk.eu - 1 | 1130 | 1123 | 81 | 81 | 92 | 81 |
| be101.rbx-g2-nc5.fr.eu - 0 | 1157 | 1157 | 83 | 84 | 135 | 86 |
| be104.fra-fr5-sbb2-nc5.de.eu - 0 | 1157 | 1157 | 92 | 92 | 100 | 92 |
| 10.200.0.19 - 1 | 1142 | 1138 | 93 | 106 | 463 | 94 |
| uplc-isp-hw-gw-01.dialog.lk - 3 | 1057 | 1031 | 110 | 111 | 132 | 110 |
| 125.214.162.138 - 0 | 1157 | 1157 | 220 | 220 | 233 | 220 |
| 125.214.162.71 - 0 | 1157 | 1157 | 218 | 218 | 233 | 219 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 233 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
As You Can see there nyc-ny1-sbb1-8k.nj.us hop has loss in both ways.
Comments
This is normal if that "nyc-ny1-sbb2-8k.nj.us" is a router (e.g. not your client and not your server). Zero impact to your traffic.
Packet loss is based on the last hop, anything along the way is devices that treat packets with low priority and is not packet loss.
Hello Sanjue007,
If you need help analyzing packet loss and traceroute results, I recommend referring to this guide: [spam link]. It has been helpful for me in the past and is my go-to reference when analyzing traceroute results. Additionally, you may find their free visual traceroute tool helpful: [spam link].
Mod edit (angstrom): deleted