Connection issues since 1.1.0.

Since 1.1.0. me and my corpmates as well have huge connection issues. Strangely the ping is okay (around 20) but it feels like having lags from about half a second up to several seconds.

 

Here the wanted informations, as stated in the FAQ.

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\PathPing -n -4 -w 500 5.153.37.200

Routenverfolgung zu 5.153.37.200 über maximal 30 Abschnitte

  0  192.168.2.106
  1  192.168.2.1
  2  87.186.224.53
  3  87.190.169.138
  4  217.239.48.154
  5  213.248.103.169
  6  80.239.160.70
  7  50.97.18.219
  8  50.97.18.216
  9  50.97.18.237
 10     *        *     159.253.158.131
 11  5.153.37.200

Berechnung der Statistiken dauert ca. 275 Sekunden…
            Quelle zum Abs.  Knoten/Verbindung
Abs. Zeit   Verl./Ges.=   %  Verl./Ges.=   %  Adresse
  0                                           192.168.2.106
                                2/ 100 =  2%   |
  1    2ms     2/ 100 =  2%     0/ 100 =  0%  192.168.2.1
                                1/ 100 =  1%   |
  2   15ms    77/ 100 = 77%    74/ 100 = 74%  87.186.224.53
                                0/ 100 =  0%   |
  3   20ms     3/ 100 =  3%     0/ 100 =  0%  87.190.169.138
                                1/ 100 =  1%   |
  4   21ms     7/ 100 =  7%     3/ 100 =  3%  217.239.48.154
                                0/ 100 =  0%   |
  5   20ms     4/ 100 =  4%     0/ 100 =  0%  213.248.103.169
                                2/ 100 =  2%   |
  6  —     100/ 100 =100%    94/ 100 = 94%  80.239.160.70
                                0/ 100 =  0%   |
  7  —     100/ 100 =100%    94/ 100 = 94%  50.97.18.219
                                0/ 100 =  0%   |
  8  —     100/ 100 =100%    94/ 100 = 94%  50.97.18.216
                                0/ 100 =  0%   |
  9  —     100/ 100 =100%    94/ 100 = 94%  50.97.18.237
                                0/ 100 =  0%   |
 10  —     100/ 100 =100%    94/ 100 = 94%  159.253.158.131
                                0/ 100 =  0%   |
 11   33ms     6/ 100 =  6%     0/ 100 =  0%  5.153.37.200

Ablaufverfolgung beendet.

 

 

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |

                       Host              -   %  Sent Recv Best Avrg Wrst Last
                            speedport.ip -    0   421   421     2     2    21     2
                           87.186.224.53 -    0   421   421     7    39   204    29
                          87.190.169.138 -    0   421   421     9    41   204    35
                          217.239.48.154 -    0   421   421    11    42   202    26
                  ffm-b12-link.telia.net -    0   421   421    11    42   206    33
xe-1-0-1.bbr01.xn01.fra01.networklayer.com -    1   417   416    11    42   206   118
   ae7.bbr02.xn01.fra01.networklayer.com -    4   373   361    40    70   242   138
   ae1.bbr01.eq01.ams02.networklayer.com -    0   421   421    17    49   213    53
   ae5.dar01.sr01.ams01.networklayer.com -    1   417   416    16    49   212   123
   po1.fcr01.sr01.ams01.networklayer.com -   25   213   161     0    60   322   128
5.153.37.200-static.reverse.softlayer.com -    0   421   421    17    49   211    47
________________________________________________ ______ ______ ______ ______ ______ ______

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

 

The tenth node (po1.fcr01.sr01.ams01.networklayer.com) went down from 100% loss to about 25% after a few minutes, still way too much. The seventh (ae7.bbr02.xn01.fra01.networklayer.com) started at about 25% loss, down to 4% at the end.

 

The upper one using cmd.exe ran at the beginning of the WinMTR test and shows how bad it was at the start of that test. No clue what´s happening here.

For some reason some matches run without a problem and others are, well, terrible.

 

Hope this helps.

it is a known issue. We will fix it on this week.