Beiträge von shdkpr2008

    Your post does not make any sense at all. First you had 150ms. Now latency is >100ms. Now what?? What's the overall latency? What is MTR telling about packet loss on the hops to netcup DC.

    Yes, at first I was having a latency of about 150ms.
    Now it is about 280ms, thus I am facing an increased latency of about 130ms.
    The increased latency due to route changes made me face delays in connections between my local node and vServer.
    PS: My ISP have a limited bandwidth allocation across Europe ~100Mb/s
    I forgot to capture old routes at the time when the latency was about 150ms, but I was having a total of 18 hops (for sure) to reach vServer.
    But now after route changes, I am having a total of 14 hops.


    Code
      6    28 ms    27 ms    27 ms  182.19.106.111
      7   122 ms   121 ms   121 ms  ae28-100-xcr1.mar.cw.net [195.89.115.197]
      8   134 ms   133 ms   134 ms  62.115.153.190
      9   166 ms   166 ms   165 ms  ffm-bb4-link.telia.net [62.115.133.180]
     10   273 ms   273 ms   301 ms  ffm-b4-link.telia.net [62.115.120.6]
     11   270 ms   269 ms   283 ms  ae9-1337.bbr01.anx25.fra.de.anexia-it.net [62.115.14.117]
     12   276 ms   276 ms   276 ms  ae1-0.bbr01.anx84.nue.de.anexia-it.net [144.208.208.140]
     13   273 ms   274 ms   277 ms  netcup-gw.bbr01.anx84.nue.de.anexia-it.net [144.208.211.27]
     14   278 ms   277 ms   277 ms  myVservere.happysrv.de [37.120.170.x]


    From my understanding, the new changes brings about telia communications into the route which further worsen the latency.
    You can see an increased latency of about 100ms between the 9th hop and 1t0h hop.


    What may I do?