Before posting a new question, please check out our Internet / WiFi and Spectrum TV App troubleshooting pages for common issues, as well as useful information to include in your post.

Advanced Search Options


We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.

Bad ping times causing gaming issues

chrisn1955chrisn1955 Posts: 12 Participant
in Connectivity Jun 16, 2022

This is a traceroute using WinMtr.

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

|                                     WinMTR statistics                                  |

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

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

|                            192.168.4.1 -   0 | 520 | 520 |   0 |   0 |  18 |   0 |

|       142-254-211-249.inf.spectrum.com -   0 | 520 | 520 |   6 |  12 |  27 |  10 |

 lag-59.srspny0101h.netops.charter.com -   0 | 520 | 520 |  15 | 108 | 804 |  34 |

|  lag-32.albynyyf02r.netops.charter.com -   0 | 520 | 520 |   8 |  12 |  20 |  12 |

| lag-26.rcr01albynyyf.netops.charter.com -   0 | 520 | 520 |   8 |  17 | 389 |  10 |

|lag-416.nycmny837aw-bcr00.netops.charter.com -   0 | 520 | 520 |  16 |  23 | 150 |  20 |

|     lag-1.pr2.nyc20.netops.charter.com -   0 | 520 | 520 |  16 |  22 |  56 |  24 |

|                           24.30.201.34 -   1 | 513 | 511 |  16 |  19 |  51 |  17 |

|be-3111-cs01.newyork.ny.ibone.comcast.net -   0 | 520 | 520 |  16 |  21 |  31 |  17 |

|be-1112-cr12.newyork.ny.ibone.comcast.net -   0 | 520 | 520 |  17 |  21 |  59 |  24 |

| be-302-cr11.newark.nj.ibone.comcast.net -   0 | 520 | 520 |  16 |  21 |  58 |  26 |

|be-1211-cs02.newark.nj.ibone.comcast.net -   0 | 520 | 520 |  17 |  22 |  54 |  19 |

|be-1212-cr12.newark.nj.ibone.comcast.net -   1 | 516 | 515 |   0 |  18 |  29 |  18 |

|be-302-cr13.beaumeade.va.ibone.comcast.net -   0 | 520 | 520 |  22 |  27 |  53 |  23 |

|be-1313-cs03.beaumeade.va.ibone.comcast.net -   1 | 513 | 511 |  22 |  26 |  44 |  24 |

|be-3312-pe12.ashburn.va.ibone.comcast.net -   0 | 520 | 520 |  22 |  27 |  86 |  23 |

|                          50.208.232.58 -   0 | 520 | 520 |  22 |  27 |  40 |  23 |

|                  No response from host - 100 | 104 |   0 |   0 |   0 |   0 |   0 |

|                        209.192.154.124 -   0 | 520 | 520 |  21 |  26 |  41 |  29 |

|________________________________________________|______|______|______|______|______|______|

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

Note the server that I marked as bold. Over 520 traces average ping time is 108 ms and worst is 804 ms. When this happens I lose connection to the gaming site. (in this case path of exile).


Here is the trace to the same end server using a VPN through NYC.

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

|                                     WinMTR statistics                                  |

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

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

|          us-east-068.whiskergalaxy.com -   0 | 100 | 100 |  16 |  23 |  29 |  23 |

|       v114.ce01.nyc-01.us.leaseweb.net -   0 | 100 | 100 |  17 |  20 |  29 |  23 |

|       ae-1.br01.nyc-01.us.leaseweb.net -   0 | 100 | 100 |  17 |  24 |  40 |  23 |

|                            38.32.125.9 -   0 | 100 | 100 |  17 |  23 |  30 |  23 |

|  be3792.rcr21.ewr01.atlas.cogentco.com -   0 | 100 | 100 |  18 |  23 |  30 |  19 |

|  be2271.ccr42.jfk02.atlas.cogentco.com -   0 | 100 | 100 |  18 |  25 |  81 |  21 |

|  be2807.ccr42.dca01.atlas.cogentco.com -   0 | 100 | 100 |  24 |  30 |  38 |  30 |

|  be3084.ccr41.iad02.atlas.cogentco.com -   0 | 100 | 100 |  25 |  30 |  37 |  26 |

|                        209.192.153.250 -   0 | 100 | 100 |  24 |  30 |  37 |  30 |

|                 s1-r1.was1.servers.com -   0 | 100 | 100 |  26 |  31 |  61 |  32 |

|                        209.192.154.124 -   2 |  97 |  96 |   0 |  26 |  30 |  26 |

|________________________________________________|______|______|______|______|______|______|

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

Note that pings are around 30 ms and the worst ping is 81 ms for all the hops.

Why are Spectrum's servers in Saratoga Springs such a big problem? I have had this problem before and all of Spectrum's experts provided no meaningful answer or solution.

Please fix this problem.

Replies

  • James_MJames_M Posts: 3,493 ADMIN
    edited June 16 Jun 16, 2022

    Hi -

    Can you also send a trace using the command prompt tracert?

    Thanks!

  • chrisn1955chrisn1955 Posts: 12 Participant
    Jun 16, 2022

    Not as many lag problems today, but you can see that the one spectrum server still has issues.


    C:\Windows\System32>tracert 209.192.154.124


    Tracing route to 209.192.154.124 over a maximum of 30 hops


     1   <1 ms   <1 ms   <1 ms 192.168.4.1

     2    9 ms    9 ms    9 ms 142-254-211-249.inf.spectrum.com [142.254.211.249]

     3  220 ms   27 ms   19 ms lag-59.srspny0101h.netops.charter.com [24.58.201.249]

     4   11 ms   10 ms   10 ms lag-32.albynyyf02r.netops.charter.com [24.58.34.216]

     5   10 ms   10 ms    8 ms lag-26.rcr01albynyyf.netops.charter.com [24.58.32.56]

     6   18 ms   17 ms   19 ms lag-416.nycmny837aw-bcr00.netops.charter.com [66.109.6.10]

     7   15 ms   17 ms   16 ms lag-1.pr2.nyc20.netops.charter.com [66.109.9.5]

     8   17 ms   18 ms   17 ms 24.30.201.34

     9   17 ms   19 ms   17 ms be-3111-cs01.newyork.ny.ibone.comcast.net [96.110.34.17]

     10   27 ms   18 ms   18 ms be-1112-cr12.newyork.ny.ibone.comcast.net [96.110.35.130]

     11   21 ms   18 ms   18 ms be-302-cr11.newark.nj.ibone.comcast.net [96.110.36.149]

     12   20 ms   19 ms   18 ms be-1211-cs02.newark.nj.ibone.comcast.net [96.110.35.69]

     13   19 ms   18 ms   19 ms be-1212-cr12.newark.nj.ibone.comcast.net [96.110.35.86]

     14   23 ms   23 ms   23 ms be-302-cr13.beaumeade.va.ibone.comcast.net [96.110.36.117]

     15   24 ms   27 ms   42 ms be-1313-cs03.beaumeade.va.ibone.comcast.net [68.86.85.73]

     16   23 ms   24 ms   24 ms be-3312-pe12.ashburn.va.ibone.comcast.net [96.110.34.122]

     17   23 ms   23 ms   22 ms 209.192.153.250

     18    *       *       *    Request timed out.

     19   24 ms   24 ms   24 ms 209.192.154.124


    Trace complete.

  • James_MJames_M Posts: 3,493 ADMIN
    edited June 17 Jun 16, 2022

    I can see there is some jitter on hop 3. Can you provide two additional command prompt tracerts to different IP's? This will demonstrate the issue on hop 3 so we can forward the issue to our contacts in Network Operations.

    Thanks!

  • chrisn1955chrisn1955 Posts: 12 Participant
    Jun 17, 2022

    C:\Windows\System32>tracert www.ups.com

    Tracing route to e13626.a.akamaiedge.net [23.11.225.148]

    over a maximum of 30 hops:


     1   <1 ms   <1 ms   <1 ms 192.168.4.1

     2    8 ms    8 ms    7 ms 142-254-211-249.inf.spectrum.com [142.254.211.249]

     3  691 ms   25 ms   30 ms lag-59.srspny0101h.netops.charter.com [24.58.201.249]

     4   11 ms   10 ms   11 ms lag-32.albynyyf02r.netops.charter.com [24.58.34.216]

     5   10 ms   10 ms   11 ms lag-26.rcr01albynyyf.netops.charter.com [24.58.32.56]

     6   19 ms   18 ms   19 ms lag-416.nycmny837aw-bcr00.netops.charter.com [66.109.6.10]

     7   32 ms   33 ms   33 ms lag-12.chcgildt87w-bcr00.netops.charter.com [66.109.6.25]

     8   42 ms   55 ms   43 ms 24.30.201.109

     9    *       *       *    Request timed out.

     10    *       *       *    Request timed out.

     11    *       *       *    Request timed out.

     12   32 ms   32 ms   33 ms a23-11-225-148.deploy.static.akamaitechnologies.com [23.11.225.148]


    Trace complete.


    C:\Windows\System32>tracert www.blizard.com

    Tracing route to www.blizard.com [35.186.238.101]

    over a maximum of 30 hops:


     1    1 ms    1 ms    1 ms 192.168.4.1

     2    9 ms   10 ms   10 ms 142-254-211-249.inf.spectrum.com [142.254.211.249]

     3  477 ms   29 ms  198 ms lag-59.srspny0101h.netops.charter.com [24.58.201.249]

     4   11 ms    9 ms   10 ms lag-32.albynyyf02r.netops.charter.com [24.58.34.216]

     5   10 ms   10 ms   10 ms lag-26.rcr01albynyyf.netops.charter.com [24.58.32.56]

     6   19 ms   19 ms   18 ms lag-416.nycmny837aw-bcr00.netops.charter.com [66.109.6.10]

     7   17 ms   17 ms   18 ms 72.14.195.162

     8   18 ms   18 ms   18 ms 108.170.236.98

     9   17 ms   17 ms   16 ms 142.251.65.103

     10   17 ms   16 ms   17 ms 101.238.186.35.bc.googleusercontent.com [35.186.238.101]


    Trace complete.

  • RAIST5150RAIST5150 Posts: 858 Contributor
    edited June 17 Jun 17, 2022

    Strange thing is that even though the echo requests qet held in queue earlier in the route, it doesn't seem to be exhibiting similar issues at hops towards the end of the routes.

    Sure, the fact it is holding those responses in queue is an indicator of high utilization there, but it would seem it is still doing a decent job of forwarding packets for the most part.


    Wonder if perhaps there is a bigger issue on return paths to your IP. Will need a looking glass tool or something similar to check that though. Think DSL reports still has their path/smoke ping tools up, but your router will need to be opened to respond to ping/echo requests to use them.

  • James_MJames_M Posts: 3,493 ADMIN
    Jun 17, 2022

    Thanks. Definitely seeing an issue on hop 3. Can you also provide another tracert to another, common url, either google.com or yahoo.com so we can see if the same traffic issue occurs?

  • RAIST5150RAIST5150 Posts: 858 Contributor
    Jun 17, 2022

    A pathping report may be handy too of you start seeing dropped packets show up further down the route. Used just like tracert, but it can give more info about where packets are actually dropping (ie between hops 5 and 6 when pinging any hop after hop 5):

    https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/pathping

  • chrisn1955chrisn1955 Posts: 12 Participant
    Jun 17, 2022

    I posted above on your first request for additional sites traces to www.blizard.com and www.ups.com. Do you want even more sites than that?

    BTW - as per Raist5150's comment about using a looking glass network tool, here is a trace from the Battle.net looking glass site doing a trace back to me.

    Once again the server in bold is spectrum in Saratoga and it has delays.


    And I found it curious that my IP address in the Saratoga region is reported as being served by Rochester RR.com. Is that typical server routing to route traffic to a server 8 miles from my house and then route it to a server 250 miles away? Is that an indication that the Saratoga region servers are being overwhelmed and it is moving traffic off to other Spectrum servers?



    17/06/2022 19:49:06 UTC

    --------------------


    MTR:

    Start: Fri Jun 17 19:49:05 2022

    HOST: ord1b-admin-looking-glass-back01            Loss%  Snt  Last  Avg Best Wrst StDev

     1.|-- 24.105.63.83                                 0.0%   10   0.5  0.7  0.5  1.5  0.0

     2.|-- 24.105.62.148                                0.0%   10   0.8  0.8  0.6  0.9  0.0

     3.|-- 137.221.66.8                                 0.0%   10   1.1  1.0  0.9  1.1  0.0

     4.|-- ???                                         100.0   10   0.0  0.0  0.0  0.0  0.0

     5.|-- 137.221.69.32                                0.0%   10   1.5  3.3  1.4 18.9  5.5

     6.|-- lag-1061.pr2.chi10.netops.charter.com        0.0%   10   1.2  1.9  1.0  5.0  1.2

     7.|-- lag-111.chcgildt87w-bcr00.netops.charter.com 0.0%   10   1.9  2.0  1.8  2.3  0.0

     8.|-- lag-1.rcr01rochnyei.netops.charter.com       0.0%   10  14.9 26.4 14.7 100.6 27.7

     9.|-- lag-1.srspny0102h.netops.charter.com         0.0%   10  32.6 108.4 25.2 754.0 226.9

     10.|-- agg2.srspny0104m.nyroc.rr.com                0.0%   10  26.0 26.3 25.9 28.9  0.7

     11.|-- cpe-67-247-91-12.rochester.res.rr.com        0.0%   10  32.8 33.3 32.6 33.8  0.0



    17/06/2022 19:49:05 UTC

    --------------------

  • James_MJames_M Posts: 3,493 ADMIN
    Jun 17, 2022

    Sorry, I neglected to request that one of the traces point to google.com or yahoo.com. Our Field Operations Team asks for it as a comparison. Please post a command prompt tracert to google.com and I will forward all four tracerts to our network contacts.

    Thanks.

  • chrisn1955chrisn1955 Posts: 12 Participant
    Jun 17, 2022

    C:\Windows\System32>tracert www.yahoo.com


    Tracing route to new-fp-shed.wg1.b.yahoo.com [2001:4998:124:1507::f001]

    over a maximum of 30 hops:


     1   <1 ms   <1 ms   <1 ms 2603-7081-4101-9d14-52c7-bfff-fea0-855f.res6.spectrum.com [2603:7081:4101:9d14:52c7:bfff:fea0:855f]

     2    *      19 ms    8 ms 2604:6000:401:72::1

     3   12 ms  174 ms   12 ms lag-59.srspny0101h.netops.charter.com [2604:6000:0:4:0:2001:0:1ae]

     4   10 ms   10 ms   10 ms lag-32.albynyyf02r.netops.charter.com [2604:6000:0:4:0:2001:0:526]

     5   12 ms    *       *    lag-26.rcr01albynyyf.netops.charter.com [2604:6000:0:4::de]

     6    *       *      27 ms lag-16.nycmny837aw-bcr00.netops.charter.com [2001:1998:0:8::12]

     7   26 ms   17 ms    *    lag-0.pr2.nyc20.netops.charter.com [2001:1998:0:4::519]

     8   22 ms   22 ms   24 ms xe-0-0-8.pat1.nyc.yahoo.com [2001:4998:f00b:d::]

     9   33 ms   33 ms   33 ms ae-0.pat2.bfw.yahoo.com [2001:4998:f00b:14::1]

     10   43 ms   33 ms    *    et-18-1-0.msr1.bf2.yahoo.com [2001:4998:f023:202::1]

     11    *      34 ms   33 ms 2001:4998:58:fe21::1

     12   32 ms   32 ms   32 ms 2001:4998:124:f807::1

     13   34 ms    *      33 ms et30.usw1-1-lbb.bf2.yahoo.com [2001:4998:124:d006::1]

     14   34 ms   32 ms   33 ms media-router-fp74.prod.media.vip.bf1.yahoo.com [2001:4998:124:1507::f001]


    Trace complete.


    Even more charter server problems.

  • James_MJames_M Posts: 3,493 ADMIN
    Jun 17, 2022

    Thanks! I'll forward to our network team in Field Operations and will advise when I receive an update.

  • RAIST5150RAIST5150 Posts: 858 Contributor
    edited June 18 Jun 18, 2022

    Interesting that you managed an IPv6 trace that time (yahoo trace).

    The game may be using only IPv4 though... a LOT of games are not using v6 yet (part of the problem with adoption rates).

    EDIT: Just searched PoE forums and found no mention of GGG starting to support IPv6... likely still only IPv4.

    May be something to keep in mind when generating reports for support. You can set a switch to force which version to run:

    tracert -4 target_name

  • James_MJames_M Posts: 3,493 ADMIN
    Jun 22, 2022

    @chrisn1955

    We forwarded your issue to the network team. Just checking in to see if you are still seeing an issue?

  • chrisn1955chrisn1955 Posts: 12 Participant
    Jun 22, 2022

    This issue is always a matter of degree. It goes from OK to Terrible. I ran another Tracert to a random address and you can see the server is still an issue (see below)

    So recently the game only lags until it disconnects about once and hour. A few days ago when I posted the message the game was unplayable without going through a VPN.

    So I guess it is better than it was, but is that the level of network quality Spectrum is striving for? Half bad?

    Perhaps the server that occasionally has bad responses is not the cause of the gaming issue, but it is a strong case because when I connect through my VPN the problem goes away.


    C:\Windows\System32>tracert aol.com

    Tracing route to aol.com [124.108.115.100]

    over a maximum of 30 hops:


     1    1 ms   <1 ms    1 ms 192.168.4.1

     2    8 ms   11 ms    8 ms 142-254-211-249.inf.spectrum.com [142.254.211.249]

     3  630 ms   21 ms   20 ms lag-59.srspny0101h.netops.charter.com [24.58.201.249]

     4    9 ms    9 ms   10 ms lag-32.albynyyf02r.netops.charter.com [24.58.34.216]

     5   10 ms   10 ms   10 ms lag-26.rcr01albynyyf.netops.charter.com [24.58.32.56]

     6   19 ms   18 ms   17 ms lag-16.nycmny837aw-bcr00.netops.charter.com [66.109.6.74]

     7   20 ms   21 ms   18 ms lag-20.nwrknjmd67w-bcr00.netops.charter.com [66.109.5.139]

     8    *       *       *    Request timed out.

     9    *       *       *    Request timed out.

     10   82 ms   82 ms   82 ms 4.7.18.146

     11  214 ms  213 ms  211 ms r4001-s2.tp.hinet.net [211.72.108.22]

     12    *       *       *    Request timed out.

     13    *       *       *    Request timed out.

     14    *       *       *    Request timed out.

     15  226 ms  225 ms  226 ms 210.242.71.37

     16  221 ms  221 ms  223 ms ae-2.clr1-a-gdc.tw1.yahoo.com [119.160.240.61]

     17  214 ms  213 ms  221 ms fab2-1-gdc.tw1.yahoo.com [119.160.240.236]

     18  225 ms  219 ms  216 ms lo0.egr5-129-pda.tw1.yahoo.com [124.108.116.128]

     19  214 ms  218 ms  219 ms lo0.lef11-1-pda.tw1.yahoo.com [124.108.117.18]

     20  221 ms  217 ms  217 ms lo0.usw11-143-pda.tw1.yahoo.com [124.108.116.142]

     21  218 ms  217 ms  222 ms w2.src.vip.tw1.yahoo.com [124.108.115.100]


    Trace complete.

  • James_MJames_M Posts: 3,493 ADMIN
    Jun 23, 2022

    Thanks. We requested an update from the network team. I will advise when I have more information.

  • RAIST5150RAIST5150 Posts: 858 Contributor
    edited June 24 Jun 23, 2022

    Yet again... the delayed response to an ECHO request earlier in the route is not reflected at the endpoint.

    Hate to keep bringing that up... but the fact that an intermediate router (primarily focused on forwarding packets, not replying to them) is queueing an ECHO request does not necessarily mean it is the source of your packet loss.

    It most likely means it is getting busy and is holding that response to conserve resources so that it can continue it's primary focus--to forward packets.

    Such occurrences can and often lead to excessive jitter to/from the endpoint, but not necessarily packet loss.


    It would be more beneficial if you can show a road map where packets are actually missing the mark at the endpoint.


    At the very least, perhaps a pathping, as it may shed more light on what may be going on.

    Just as an example, here is a pathping report to that servers.com network in the original posts. Granted mine is "clean"... but if not, this report may better demonstrate when packet loss may be occuring between hops, as shown between hops 9 and 10 in this report. Loss occurred at hop 10, but ONLY between hops 9 and 10 (because it is ignoring ECHO requests and is only forwarding). But no losses were detected anywhere else in the run.



    C:\WINDOWS\system32>pathping 209.192.154.124


    Tracing route to 209.192.154.124 over a maximum of 30 hops


     0 G75VXLAP [10.10.100.10]

     1 LPTSRV [10.10.100.1]

     2 cpe-24-211-64-1.sc.res.rr.com [24.211.64.1]

     3 lag-63.flrnscwk01h.netops.charter.com [174.111.74.92]

     4 lag-34.mybhsc0601r.netops.charter.com [24.31.196.210]

     5 lag-42.rcr01drhmncev.netops.charter.com [24.93.64.32]

     6 lag-15.asbnva1611w-bcr00.netops.charter.com [66.109.6.80]

     7 lag-310.pr2.dca10.netops.charter.com [209.18.43.59]

     8 be-206-pe07.ashburn.va.ibone.comcast.net [50.242.149.253]

     9 be-3207-cs02.beaumeade.va.ibone.comcast.net [96.110.32.189]

     10 be-3212-pe12.ashburn.va.ibone.comcast.net [96.110.34.118]

     11 209.192.153.250

     12    *       *       *

    Computing statistics for 275 seconds...

               Source to Here  This Node/Link

    Hop RTT   Lost/Sent = Pct Lost/Sent = Pct Address

     0                                          G75VXLAP [10.10.100.10]

                                   0/ 100 = 0%  |

     1   1ms    0/ 100 = 0%    0/ 100 = 0% LPTSRV [10.10.100.1]

                                   0/ 100 = 0%  |

     2  16ms    0/ 100 = 0%    0/ 100 = 0% cpe-24-211-64-1.sc.res.rr.com [24.211.64.1]

                                   0/ 100 = 0%  |

     3  21ms    0/ 100 = 0%    0/ 100 = 0% lag-63.flrnscwk01h.netops.charter.com [174.111.74.92]

                                   0/ 100 = 0%  |

     4  16ms    0/ 100 = 0%    0/ 100 = 0% lag-34.mybhsc0601r.netops.charter.com [24.31.196.210]

                                   0/ 100 = 0%  |

     5  25ms    0/ 100 = 0%    0/ 100 = 0% lag-42.rcr01drhmncev.netops.charter.com [24.93.64.32]

                                   0/ 100 = 0%  |

     6  35ms    0/ 100 = 0%    0/ 100 = 0% lag-15.asbnva1611w-bcr00.netops.charter.com [66.109.6.80]

                                   0/ 100 = 0%  |

     7  31ms    0/ 100 = 0%    0/ 100 = 0% lag-310.pr2.dca10.netops.charter.com [209.18.43.59]

                                   0/ 100 = 0%  |

     8  32ms    0/ 100 = 0%    0/ 100 = 0% be-206-pe07.ashburn.va.ibone.comcast.net [50.242.149.253]

                                   0/ 100 = 0%  |

     9  28ms    0/ 100 = 0%    0/ 100 = 0% be-3207-cs02.beaumeade.va.ibone.comcast.net [96.110.32.189]

                                 100/ 100 =100%  |

     10 ---    100/ 100 =100%    0/ 100 = 0% be-3212-pe12.ashburn.va.ibone.comcast.net [96.110.34.118]

                                   0/ 100 = 0%  |

     11 ---    100/ 100 =100%    0/ 100 = 0% 209.192.153.250


    Trace complete.

  • Paul_BPaul_B Posts: 485 Moderator
    Jun 25, 2022

    Good morning @chrisn1955 -

    I wanted to post an update to this discussion. Our network engineers did get back to us and they are indicating that they found no trouble with hop 3 in the traces provided. The way it was explained to us is our network equipment treats ICMP requests such as pings and traceroutes at the lowest priority and as a result the routers may respond slower to this type of traffic as opposed to normal traffic such as video, gaming etc.

    They also indicated that if hop 3 was an issue, that everything after it more than likely would be displaying high latency and as a result more customers would be experiencing issues with video, phone calls, gaming, streaming etc.

    If you have any further questions, please feel free to let us know.

    Paul_B

  • chrisn1955chrisn1955 Posts: 12 Participant
    edited June 25 Jun 25, 2022

    I appreciate you checking with network engineering. From what you say it indicates the problem is in another area and not a Spectrum server issue. It is still interesting to me that when the problem occurs connecting via VPN usually fixes the issue.

    Per @RAIST5150 's request I ran a pathping to the POE server that the log files indicate was the last one I connected to.

    I'm not familiar with what this test is looking for or what it indicates. There were a few lost packets and I don't know if that is at all significant.


    C:\Windows\System32>pathping 173.233.139.180

    Tracing route to 173.233.139.180 over a maximum of 30 hops

     0 MSI [192.168.4.131]

     1 192.168.4.1

     2 142-254-211-249.inf.spectrum.com [142.254.211.249]

     3 lag-59.srspny0101h.netops.charter.com [24.58.201.249]

     4 lag-32.albynyyf02r.netops.charter.com [24.58.34.216]

     5    *    lag-26.rcr01albynyyf.netops.charter.com [24.58.32.56]

     6 lag-416.nycmny837aw-bcr00.netops.charter.com [66.109.6.10]

     7 lag-0.pr2.nyc20.netops.charter.com [66.109.5.119]

     8 24.30.201.34

     9    *    be-3311-cs03.newyork.ny.ibone.comcast.net [96.110.34.25]

     10 be-1312-cr12.newyork.ny.ibone.comcast.net [96.110.35.138]

     11 be-301-cr11.newark.nj.ibone.comcast.net [96.110.36.145]

     12 be-1311-cs03.newark.nj.ibone.comcast.net [96.110.35.73]

     13 be-1312-cr12.newark.nj.ibone.comcast.net [96.110.35.90]

     14    *    be-302-cr13.beaumeade.va.ibone.comcast.net [96.110.36.117]

     15 be-1113-cs01.beaumeade.va.ibone.comcast.net [68.86.85.65]

     16    *    be-3112-pe12.ashburn.va.ibone.comcast.net [96.110.34.114]

     17 209.192.153.250

     18    *       *       *

    Computing statistics for 425 seconds...

               Source to Here  This Node/Link

    Hop RTT   Lost/Sent = Pct Lost/Sent = Pct Address

     0                                          MSI [192.168.4.131]

                                   0/ 100 = 0%  |

     1   0ms    0/ 100 = 0%    0/ 100 = 0% 192.168.4.1

                                   0/ 100 = 0%  |

     2   8ms    0/ 100 = 0%    0/ 100 = 0% 142-254-211-249.inf.spectrum.com [142.254.211.249]

                                   0/ 100 = 0%  |

     3  14ms    1/ 100 = 1%    1/ 100 = 1% lag-59.srspny0101h.netops.charter.com [24.58.201.249]

                                   0/ 100 = 0%  |

     4  10ms    1/ 100 = 1%    1/ 100 = 1% lag-32.albynyyf02r.netops.charter.com [24.58.34.216]

                                   0/ 100 = 0%  |

     5  10ms    0/ 100 = 0%    0/ 100 = 0% lag-26.rcr01albynyyf.netops.charter.com [24.58.32.56]

                                   0/ 100 = 0%  |

     6  18ms    1/ 100 = 1%    1/ 100 = 1% lag-416.nycmny837aw-bcr00.netops.charter.com [66.109.6.10]

                                   0/ 100 = 0%  |

     7  18ms    0/ 100 = 0%    0/ 100 = 0% lag-0.pr2.nyc20.netops.charter.com [66.109.5.119]

                                   0/ 100 = 0%  |

     8  18ms    0/ 100 = 0%    0/ 100 = 0% 24.30.201.34

                                   0/ 100 = 0%  |

     9  18ms    0/ 100 = 0%    0/ 100 = 0% be-3311-cs03.newyork.ny.ibone.comcast.net [96.110.34.25]

                                   0/ 100 = 0%  |

     10  18ms    0/ 100 = 0%    0/ 100 = 0% be-1312-cr12.newyork.ny.ibone.comcast.net [96.110.35.138]

                                   0/ 100 = 0%  |

     11  18ms    0/ 100 = 0%    0/ 100 = 0% be-301-cr11.newark.nj.ibone.comcast.net [96.110.36.145]

                                   0/ 100 = 0%  |

     12  18ms    0/ 100 = 0%    0/ 100 = 0% be-1311-cs03.newark.nj.ibone.comcast.net [96.110.35.73]

                                   0/ 100 = 0%  |

     13  18ms    0/ 100 = 0%    0/ 100 = 0% be-1312-cr12.newark.nj.ibone.comcast.net [96.110.35.90]

                                   0/ 100 = 0%  |

     14  23ms    2/ 100 = 2%    2/ 100 = 2% be-302-cr13.beaumeade.va.ibone.comcast.net [96.110.36.117]

                                   0/ 100 = 0%  |

     15  23ms    0/ 100 = 0%    0/ 100 = 0% be-1113-cs01.beaumeade.va.ibone.comcast.net [68.86.85.65]

                                   0/ 100 = 0%  |

     16  23ms    0/ 100 = 0%    0/ 100 = 0% be-3112-pe12.ashburn.va.ibone.comcast.net [96.110.34.114]

                                   0/ 100 = 0%  |

     17  23ms    0/ 100 = 0%    0/ 100 = 0% 209.192.153.250


    Trace complete.

  • Paul_BPaul_B Posts: 485 Moderator
    Jun 25, 2022

    Thank you for that additional information. PathPing combines the functionality of a tracert and a ping test into one test. It looks like on this particular test you're getting pretty good statistics. I would keep an eye on this and if anything changes where you see latency all the way through a trace, we can take another look.

    Are you seeing any issues with any other games? Or just Path of Exile?

    Paul_B

Sign In or Register to comment.