Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Inconsistent high ping on the same servers


  • Please log in to reply
6 replies to this topic

#1 WagnerWarrior

WagnerWarrior

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:01 PM

Posted 18 August 2016 - 11:43 PM

Hello, I can't really come up with a solid title for my issue and I can not find my issue anywhere else.

Basically, when I play games such as Overwatch or Rocket League (any game at all) I will have one match where, for example, I'll have 60 ping. The next match I could have anywhere between 200-1000 ping, however it normally hovers around the 300 mark. Then, the next match, I could have 60 ping again. I've uploaded an example here: https://www.youtube.com/watch?v=oMPSFVlO4nA

I'm wired and have 100down/15up and an SBG6580 surfboard router/modem combination with no other routers on Time Warner Cable. Any other information you need such as speedtests I'm open and will provide.

So far I have tried opening ports for the game's servers, however I was told that shouldn't do anything. I've made my IP address static. I've disabled my modem/router's firewall as that seemed to be an issue to other users. I've moved the port my cat cable is plugged into and tried them all. I pinged my modem/router and had 0% packet loss. There's probably a few other things that I have tried that I can't pull from the top of my head right now.

Thank you!



BC AdBot (Login to Remove)

 


#2 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:01 PM

Posted 19 August 2016 - 07:38 AM

Cable gateways are not good IMO, specially for gaming. Is it possible to buy a separate modem and router?

 

On top of that, can you post a tracert to one of the game servers?

 

Last what are you signal levels? You can find them on the modem's connection tab on it's website. See here.



#3 WagnerWarrior

WagnerWarrior
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:01 PM

Posted 19 August 2016 - 11:05 PM

Cable gateways are not good IMO, specially for gaming. Is it possible to buy a separate modem and router?

 

On top of that, can you post a tracert to one of the game servers?

 

Last what are you signal levels? You can find them on the modem's connection tab on it's website. See here.

It's possible to buy a separate one but it would be nice not to.

I have two tracert's, the first one from a good server and the second from a bad server:

Good:

 
Tracing route to 24.105.43.51 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2    22 ms    22 ms    13 ms  cpe-67-11-200-1.satx.res.rr.com [67.11.200.1] 
  3    12 ms    18 ms    20 ms  cpe-67-11-200-1.satx.res.rr.com [67.11.200.1] 
  4    62 ms    65 ms    63 ms  tge0-0-8.lnvytxca02h.texas.rr.com [24.28.133.93] 
  5    11 ms    13 ms    11 ms  agg32.snaptxwm02r.texas.rr.com [24.175.33.132] 
  6    12 ms    13 ms    20 ms  agg23.snantxvy01r.texas.rr.com [24.175.32.184] 
  7    24 ms    22 ms    23 ms  24.175.33.4 
  8    38 ms    38 ms    31 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88] 
  9    23 ms    19 ms    17 ms  107.14.17.133 
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *     66.109.9.151  reports: Destination net unreachable.
 
Trace complete.
 
Bad:
 
 
Tracing route to ec2-52-67-128-134.sa-east-1.compute.amazonaws.com [52.67.128.134]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2    22 ms    20 ms    21 ms  cpe-67-11-200-1.satx.res.rr.com [67.11.200.1] 
  3    17 ms    13 ms    12 ms  cpe-67-11-200-1.satx.res.rr.com [67.11.200.1] 
  4    33 ms    99 ms    31 ms  tge0-0-9.lnvytxca02h.texas.rr.com [24.28.132.33] 
  5   105 ms   105 ms    82 ms  agg32.snaptxwm02r.texas.rr.com [24.175.33.132] 
  6    72 ms    81 ms    79 ms  agg23.snantxvy01r.texas.rr.com [24.175.32.184] 
  7    99 ms   109 ms   104 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146] 
  8   140 ms   119 ms   114 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88] 
  9    24 ms    33 ms    31 ms  0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236] 
 10    44 ms    30 ms    19 ms  dls-bb1-link.telia.net [213.248.93.189] 
 11    68 ms   160 ms    70 ms  nyk-bb1-link.telia.net [213.155.137.50] 
 12   102 ms    70 ms    90 ms  nyk-b5-link.telia.net [213.155.131.137] 
 13    97 ms    68 ms    86 ms  62.115.32.130 
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17   404 ms   426 ms   416 ms  177.72.240.99 
 18   264 ms   235 ms   221 ms  177.72.240.141 
 19   203 ms   207 ms   209 ms  177.72.240.153 
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 
Trace complete.
 
and finally here are my signal levels (i don't know exactly which is what you're asking for though) https://i.gyazo.com/67f64718a3ee25e743c26e842203cee8.png


#4 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:01 PM

Posted 20 August 2016 - 08:47 AM

What is the second tracert to? Amazon server in Brazil? Olympic? Looking like a Roadrunner issue deep in their system. A issue in NE Texas as seen here.  Routing North is good, but south is bad. Have you called RR and asked if a known issue?

 

  5   105 ms   105 ms    82 ms  agg32.snaptxwm02r.texas.rr.com [24.175.33.132] 


Edited by Trikein, 20 August 2016 - 08:55 AM.


#5 WagnerWarrior

WagnerWarrior
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:01 PM

Posted 20 August 2016 - 07:45 PM

What is the second tracert to? Amazon server in Brazil? Olympic? Looking like a Roadrunner issue deep in their system. A issue in NE Texas as seen here.  Routing North is good, but south is bad. Have you called RR and asked if a known issue?

 

  5   105 ms   105 ms    82 ms  agg32.snaptxwm02r.texas.rr.com [24.175.33.132] 

Both of those tracert's are to Overwatch servers. The first one is to a good server that I had normal ping on however the second one was another overwatch server where I had the issue on it.



#6 Trikein

Trikein

  • Members
  • 1,321 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Rhode Island, US
  • Local time:09:01 PM

Posted 20 August 2016 - 08:18 PM

I am ignorant on how Overwatch matchmaking works. Is 52.67.128.134 the IP of a dedicated game server or the IP of a player? The main different between the first and second trace are the huge geographical differences. The first trace stays within Texas, while the second trace bounces around the US, through NY over to Europe and Sweden, then back over the ocean again to South America. Hop 14-16 is where you are probably seeing the worst latency spikes. Do you have problems with local players? If not, then this is some what normal. 



#7 WagnerWarrior

WagnerWarrior
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:09:01 PM

Posted 20 August 2016 - 08:41 PM

I am ignorant on how Overwatch matchmaking works. Is 52.67.128.134 the IP of a dedicated game server or the IP of a player? The main different between the first and second trace are the huge geographical differences. The first trace stays within Texas, while the second trace bounces around the US, through NY over to Europe and Sweden, then back over the ocean again to South America. Hop 14-16 is where you are probably seeing the worst latency spikes. Do you have problems with local players? If not, then this is some what normal. 

24.105.43.51 and 52.67.128.134 are the IPs of Overwatch's game servers. Here is another tracert to a different bad server:

 

 

 
Tracing route to 24.105.41.7 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2    20 ms    38 ms    14 ms  cpe-67-11-200-1.satx.res.rr.com [67.11.200.1] 
  3    12 ms    10 ms    12 ms  cpe-67-11-200-1.satx.res.rr.com [67.11.200.1] 
  4    28 ms    32 ms    32 ms  tge0-0-8.lnvytxca02h.texas.rr.com [24.28.133.93] 
  5    49 ms    40 ms    48 ms  agg32.snaptxwm02r.texas.rr.com [24.175.33.132] 
  6    51 ms    44 ms    49 ms  agg23.snantxvy01r.texas.rr.com [24.175.32.184] 
  7    21 ms    39 ms    28 ms  agg23.dllatxl301r.texas.rr.com [24.175.32.146] 
  8    54 ms    42 ms    39 ms  bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.109.6.88] 
  9    20 ms    17 ms    20 ms  107.14.17.133 
 10     *     66.109.9.151  reports: Destination net unreachable.
 
Trace complete.
 
From those results it looks like the server wouldn't be bad, but interestingly enough this time my ping was fluctuating from normal, to around double or triple normal, while averaging around double my normal ping. The server before this one saw no fluctuations and stayed at a normal ping.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users