Skip to main content
ulf301's profile

ulf301

New Contributor

 • 

5 Messages

Closed

Major Latency issues when streaming or online gaming

As of a few weeks ago i am experiencing major issues with lag latency issues when gaming ... specifically WOW.  This was a reported issue with them and many individuals traced the blame to the hop from LEVEL3 in Phoenix.  That got fixed for them but i am still having issues.  I correlated the problem with the issues i am having just browsing and streaming video so i ran some tracer tests and noticed errors after the hop to Dallas Level3.  I need help to get this fixed asap .... the chat tech, when he realized I knew he was feeding me BS excuses just closed the session.  this is very frustrating and TBH if it isnt resolved i will switch ISP's

Discussions

 • 

Updated 

2.4K

1

0

0

Becky

Moderator

 • 

4.3K Messages

Hi Ulf301, are you able to provide your traceroutes and other test results showing the issue with the hop from Level 3 in Dallas? We're happy to take a closer look at this for you. Feel free to email us at cox.help@cox.com. -Becky, Cox Support Forums Moderator

4

0

ulf301

New Contributor

 • 

5 Messages

Microsoft Windows [Version 10.0.17134.407]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\keith>tracert cox.com

Tracing route to cox.com [45.60.49.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Car-Ramrod [xxxxxxxxxxxxxx]
2 6 ms 6 ms 6 ms xxxxxxxxx
3 8 ms 8 ms 11 ms 100.122.126.150
4 10 ms 11 ms 15 ms 100.122.125.86
5 20 ms 21 ms 21 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 * 757 ms 798 ms lag-105.ear5.Dallas1.Level3.net [4.7.200.13]
7 * * * Request timed out.
8 52 ms 52 ms 52 ms 4.7.26.34
9 51 ms 52 ms 52 ms 45.60.49.167

Trace complete.

C:\Users\keith>

im no expert but this seems to be the issue to me .... this is one tracer but each one i do has similar results ..... 

Like

Reply

0

Becky

Moderator

 • 

4.3K Messages

Hi Ulf301, if there was truly an issue with the Dallas Level 3 server in hop 6 or the following hop, your traceroute would not have completed successfully. Some servers and routers specifically block or down-prioritize ICMP echo requests. During a traceroute, these hops will show latency, packet loss, or time out completely, as in hop 7. The important point to understand about these hops is that if they are not affecting the downstream hops, their behavior is considered normal. -Becky, Cox Support Forums Moderator

Like

Reply

0

ulf301

New Contributor

 • 

5 Messages

well the WOW people are telling me this is where the error is occurring .... and it isnt happening with other ISP's in the New Orleans area.  the trace route I posted is one of many ... i would think if Cox wants to keep my business then you would want to help me fix this

Like

Reply

0

Becky

Moderator

 • 

4.3K Messages

Hi Ulf301, please post or email us (cox.help@cox.com) a few traceroutes to the WOW server(s) you use. -Becky, Cox Support Forums Moderator

Like

Reply

0

Related Content

  • Closed

    1

    0

  • Closed

    3

    0

  • Closed

    1

    0

  • Closed

    1

    0

  • Closed

    1

    0

Recent Discussions

View More

Loading...