Verbindugnsabbrüche bei Telekom?

  • Die erhöhte Latenz seit 15:2X Uhr gibt es "lustigerweise" vermutlich auch auswärts (ziemlich genau 10ms drauf) ins H-Netz; direkt am ersten Hop.

    Habe keine Ping-Ziele, aber ein Monitoring für Website-Response times.


    Bildschirmfoto 2018-11-22 um 19.02.27.png

    Code
    1. 1.|-- gw02.netcup.net 0.0% 1 13.2 13.2 13.2 13.2 0.0
    2. 2.|-- juniper2.rz2.hetz~.de 0.0% 1 13.6 13.6 13.6 13.6 0.0
    3. 3.|-- core21.fsn1.hetz~.com 0.0% 1 15.8 15.8 15.8 15.8 0.0
    4. 4.|-- ex9k2.dc5.fsn1.hetz~.com 0.0% 1 16.1 16.1 16.1 16.1 0.0
    5. 5.|-- h785.timme~.de 0.0% 1 19.2 19.2 19.2 19.2 0.0
  • Code
    1. |------------------------------------------------------------------------------------------|
    2. | WinMTR statistics |
    3. | Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
    4. |------------------------------------------------|------|------|------|------|------|------|
    5. | speedport.ip - 0 | 150 | 150 | 0 | 7 | 233 | 1 |
    6. | 62.155.xxx.x - 0 | 150 | 150 | 7 | 15 | 229 | 9 |
    7. | 217.239.48.122 - 0 | 150 | 150 | 12 | 18 | 241 | 13 |
    8. | gw-dtag.fra.netcup.net - 0 | 150 | 150 | 34 | 41 | 254 | 36 |
    9. | www.netcup.de - 0 | 150 | 150 | 34 | 40 | 269 | 35 |
    10. |________________________________________________|______|______|______|______|______|______|

    mein Rechner ist über WLAN mit dem Telekom Router verbunden.


    Das Netcup-Forum ist so nicht erreichbar, antwortet nicht auf ping


  • For me, the latency is still> 100ms + high. Before ~ 150ms // Now ~ 280ms
    I have already mailed the support, but haven't got any reply yet.
    Hopes to have it resolved soon>. <

    Peaceful Traveler | Food Lover | Optimistic Cinephilla | DIY Internals and Core | Analyst | Coder | Explorer | Born in ‘95 | Will die soon | Bookish

  • über einen Telekom-Anschluss läuft es ohne Probleme.


    Routenverfolgung zu http://www.netcup.de [46.38.224.30]

    über maximal 30 Hops:


    Code
    1. 1 1 ms 1 ms 1 ms speedport.ip [192.168.2.1]
    2. 2 8 ms 9 ms 9 ms 62.155.xxx.x
    3. 3 11 ms 9 ms 10 ms 217.239.48.86
    4. 4 16 ms 13 ms 14 ms gw-dtag.fra.netcup.net [80.157.204.242]
    5. 5 12 ms 12 ms 11 ms www.netcup.de [46.38.224.30]

    Ablaufverfolgung beendet.

  • 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
    1. 6 28 ms 27 ms 27 ms 182.19.106.111
    2. 7 122 ms 121 ms 121 ms ae28-100-xcr1.mar.cw.net [195.89.115.197]
    3. 8 134 ms 133 ms 134 ms 62.115.153.190
    4. 9 166 ms 166 ms 165 ms ffm-bb4-link.telia.net [62.115.133.180]
    5. 10 273 ms 273 ms 301 ms ffm-b4-link.telia.net [62.115.120.6]
    6. 11 270 ms 269 ms 283 ms ae9-1337.bbr01.anx25.fra.de.anexia-it.net [62.115.14.117]
    7. 12 276 ms 276 ms 276 ms ae1-0.bbr01.anx84.nue.de.anexia-it.net [144.208.208.140]
    8. 13 273 ms 274 ms 277 ms netcup-gw.bbr01.anx84.nue.de.anexia-it.net [144.208.211.27]
    9. 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?

    Peaceful Traveler | Food Lover | Optimistic Cinephilla | DIY Internals and Core | Analyst | Coder | Explorer | Born in ‘95 | Will die soon | Bookish