Jump to content

Ping Jitters


ViciousSavag3

Recommended Posts

Hi guys i have a problem with my ping but i TRULY know that i have my settings Perfect the way im suppose to have it. But everytime i play a game my ping goes from 12ms to like 35ms does anybody know why it does that or what i can do to fix it. My distance range is 996km and ping assist is 25ms.

 

any help would be Gladly Appreciated thank you

Link to comment
Share on other sites

  • Netduma Staff

Hi there - what results do you get if you run the ‘Internet Diagnostics’ tool on your Netduma R1 interface? It’s worth checking if there’s a problem on you’re line.

 

However, it’s most likely the server you are pinging. Is it the same server each time you see this jitter or is it true for every server you play on?

Link to comment
Share on other sites

hi there thanxs for the reply brother well i get 

 

Ping: Bright Exceptional

 

Jitter:  Low Faded Good

 

Spikes: Low Faded Good   

 

Packet Loss: Bright No Loss

 

and for now its been doin it for every server i play on for some reason ived tried everything i could do hopefully.. and right now i lowered the Filter Distance to 535km with 30ms Ping assist

any suggestions?

Link to comment
Share on other sites

hi there thanxs for the reply brother well i get 

 

Ping: Bright Exceptional

 

Jitter:  Low Faded Good

 

Spikes: Low Faded Good   

 

Packet Loss: Bright No Loss

 

and for now its been doin it for every server i play on for some reason ived tried everything i could do hopefully.. and right now i lowered the Filter Distance to 535km with 30ms Ping assist

any suggestions?

I think jack meant in internet diagnostics tab and run ping diagnostic. There is a button called "show details" I think he wanted you to check ping fluctuation in the readings!

Link to comment
Share on other sites

ohhh im sorry well this is my ''DETAILS''

 

 

Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=57 time=12.989 ms
64 bytes from 8.8.8.8: seq=1 ttl=57 time=12.583 ms
64 bytes from 8.8.8.8: seq=2 ttl=57 time=9.830 ms
64 bytes from 8.8.8.8: seq=3 ttl=57 time=9.884 ms
64 bytes from 8.8.8.8: seq=4 ttl=57 time=9.975 ms
64 bytes from 8.8.8.8: seq=5 ttl=57 time=10.140 ms
64 bytes from 8.8.8.8: seq=6 ttl=57 time=9.866 ms
64 bytes from 8.8.8.8: seq=7 ttl=57 time=10.176 ms
64 bytes from 8.8.8.8: seq=8 ttl=57 time=9.575 ms
64 bytes from 8.8.8.8: seq=9 ttl=57 time=10.469 ms
64 bytes from 8.8.8.8: seq=10 ttl=57 time=10.370 ms
64 bytes from 8.8.8.8: seq=11 ttl=57 time=10.265 ms
64 bytes from 8.8.8.8: seq=12 ttl=57 time=18.670 ms
64 bytes from 8.8.8.8: seq=13 ttl=57 time=9.958 ms
64 bytes from 8.8.8.8: seq=14 ttl=57 time=9.845 ms
64 bytes from 8.8.8.8: seq=15 ttl=57 time=9.958 ms
64 bytes from 8.8.8.8: seq=16 ttl=57 time=10.220 ms
64 bytes from 8.8.8.8: seq=17 ttl=57 time=9.871 ms
64 bytes from 8.8.8.8: seq=18 ttl=57 time=9.662 ms
64 bytes from 8.8.8.8: seq=19 ttl=57 time=10.721 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 9.575/10.751/18.670 ms
Trace
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.0.0.1 1.688 ms 1.498 ms 1.392 ms
2 96.120.89.177 11.327 ms 10.106 ms 10.400 ms
3 68.85.103.29 11.048 ms 11.017 ms 11.232 ms
4 162.151.79.77 12.267 ms 12.164 ms 12.732 ms
5 68.86.143.89 11.208 ms 11.870 ms 12.178 ms
6 96.112.146.14 13.213 ms 69.241.91.94 13.018 ms 96.112.146.14 12.968 ms
7 * * *
8 209.85.248.34 14.381 ms 108.170.237.144 12.417 ms 108.170.237.106 12.540 ms
9 108.170.232.59 13.075 ms 108.170.235.25 13.355 ms 108.170.232.61 12.389 ms
10 8.8.8.8 12.529 ms 12.473 ms 13.209 ms
Link to comment
Share on other sites

HERES MY 2ND TEST

 

 

 

Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=57 time=12.217 ms
64 bytes from 8.8.8.8: seq=1 ttl=57 time=11.889 ms
64 bytes from 8.8.8.8: seq=2 ttl=57 time=9.796 ms
64 bytes from 8.8.8.8: seq=3 ttl=57 time=9.932 ms
64 bytes from 8.8.8.8: seq=4 ttl=57 time=10.206 ms
64 bytes from 8.8.8.8: seq=5 ttl=57 time=10.280 ms
64 bytes from 8.8.8.8: seq=6 ttl=57 time=10.070 ms
64 bytes from 8.8.8.8: seq=7 ttl=57 time=10.306 ms
64 bytes from 8.8.8.8: seq=8 ttl=57 time=10.075 ms
64 bytes from 8.8.8.8: seq=9 ttl=57 time=9.906 ms
64 bytes from 8.8.8.8: seq=10 ttl=57 time=9.942 ms
64 bytes from 8.8.8.8: seq=11 ttl=57 time=9.868 ms
64 bytes from 8.8.8.8: seq=12 ttl=57 time=10.051 ms
64 bytes from 8.8.8.8: seq=13 ttl=57 time=9.863 ms
64 bytes from 8.8.8.8: seq=14 ttl=57 time=9.999 ms
64 bytes from 8.8.8.8: seq=15 ttl=57 time=10.556 ms
64 bytes from 8.8.8.8: seq=16 ttl=57 time=10.466 ms
64 bytes from 8.8.8.8: seq=17 ttl=57 time=9.803 ms
64 bytes from 8.8.8.8: seq=18 ttl=57 time=10.472 ms
64 bytes from 8.8.8.8: seq=19 ttl=57 time=9.752 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 9.752/10.272/12.217 ms
Trace
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.0.0.1 1.294 ms 1.181 ms 1.841 ms
2 96.120.89.177 9.897 ms 9.310 ms 9.893 ms
3 68.85.103.29 10.930 ms 10.981 ms 10.980 ms
4 162.151.79.77 11.315 ms 10.834 ms 11.200 ms
5 68.86.143.89 12.360 ms 11.562 ms 11.019 ms
6 69.241.91.94 20.317 ms 96.112.146.10 12.505 ms 13.243 ms
7 * * *
8 108.170.237.106 12.746 ms 108.170.237.22 20.323 ms 72.14.239.42 12.746 ms
9 209.85.240.169 13.090 ms 108.170.230.87 13.289 ms 209.85.240.41 12.088 ms
10 8.8.8.8 12.465 ms 12.308 ms 12.860 ms
Link to comment
Share on other sites

well, everything looks fine on the R1, when you say your ping fluctuates so much do you look at your ping in cod for instance bo3 allows you to see your ping in game (which fluctuates on mine from 15 - 30 but I know my line is stable.

 

 

If that is not how you are viewing your ping tell us where you are seeing the spikes.........what kind of connection do you have, is it vdsl or fibre? If fibre is it fttc or fttp and who is your isp and the make and model of your isp modem?

 

 

 

You can download a program called pingplotter which actually monitors your connection in real time and is very very accurate. If you do get pingplotter then ping twitter and run it for approx 2- - 30 mins and post a screenshot!

Link to comment
Share on other sites

well yea i know it is good but the moment i join lobbies thats were it starts Jittering dont know why.. i can actually see my ping thru the GEO Filter when im playing a game and it HOPS from 12ms to like 30ms sometimes 50ms i wonder and hope is the server? but hope u can help me with this. 

 

IPS: XFINITY : DSL

 

MODEL:  TG1682G

 

MAKE: ARRIS

 

Ps. Downloading Pingplotter

Link to comment
Share on other sites

sorry for the delay in replying, been a busy day. Your modem has a very bad intel puma 6 chipset which is quite commonly known for spiking and theres a lawsuit going on over it as it is affecting customers from all over the wolrd with that chipset in their modems. I would suggest buying an alternative model. 

 

here is the article............................... https://www.theregis...uma_modem_woes/

 

I would suggest buying your own modem and this is a list of the best ones from 1 of our mods on here.

 

*NOTE FROM NETDUMA FRASER*

 

Keep in mind, the R1 still works with those listed you just may get a better experience with those in the compatibility list. Some people use those in the non compatible list and have no issues.

 

There is no reason to purchase another modem/router unless you have specifically found issues with your existing modem/router.

----

 

 

THIS IS IN NO WAY A FULL LIST OF THE BEST GAMING MODEMS.

 

AS A GENERAL RULE - STAY AWAY FROM ISP PROVIDED "ALL IN ONE" MODEM/ROUTER HUBS IF YOU CAN.

 

IF YOU ARE LOOKING FOR A NEW MODEM AND WANT TO BE SURE IT WILL WORK PROPERLY ONLY PURCHASE FROM THE GOOD MODEM LIST.

 

BAD*:

 

Arris/Motorola:

SB6121

SB6141

SB6183

SB6190

TG1672G

TM1602

TG2492LG - Virgin Media Super Hub 3

TG3482G

 

AVM:
FRITZ!Box 6460

FRITZ!Box 6490

FRITZ!Box 6320

Cisco:
XG1-V3

DPC3848

DPC3848V

DPC3939
DPC3941B

DPC3941T

DPC3941 (commonly - Comcast Xfinity XB3)

Compal:

Super Hub 3  - virgin media
CH7465-LG Virgin Media Hub 3

CH7466

CH66xxx

 

Hitron:
CDA Series: CDA-32372 CDA-3-35
CDE Series: CDE-32372
CGN3 Series: CGN3, CGN3ACR,CGN3AMF, CGN3AMR, CGN3ACSMR
CGNM Series: CGNM-2250 CGNM-3552
CGNDM Series.
CGNV Series: CGNV4

Linksys:
CM3016

CM3024

CG7500

Netgear:

CG3300

CG4000
CG4500

CG4500TM

C6300

C6300BD (Telstra Gateway Max - Australia)

CM500

CM600

CM700

AC1750

AC1900 (R7000)

 

Pace:

C704

 

Panasonic:

C01AS03

Samsung:
Home Media Server

Horizon G5400

Horizon G7400

Bbox G7441

 

Sagemcom

F@st 5260

SMC:
D3G2408

D3G0804

D3GNV5

D3GN4

D3M1604

D3G1604

E3G1604

 

TP-Link:

CR7000

TC-7620

 

Technicolor:

TC8715D

 

Ubee:

EVW3226

 

Zoom:

5370

 

*By "bad" modem we mean ones that either have bugged chipsets which cause slowdowns and huge ping spikes under load or ones that have been tested and proven to cause issues with ping while gaming.

 

 

GOOD:

 

Arris/Motorola:

TM722G

TM822G

 

TP-Link:

TC-7610

TC-7610-E

 

Zoom:

5341J

Link to comment
Share on other sites

so u suggest that i buy one of the GOOD LIST MODEMS? i wouldnt mind if u guarantee me that it would work better? but thank you for the heads up..

 

at first i was hoping it might of been the SERVERS for WWII because they been down idk if u knew that.. anyways if they are can that be the issue? 

Link to comment
Share on other sites

i am not sure as I do not live in the U.S and not sure but I do know the tp-link 7610 is available for about 40USD so it is not a bank breaker to buy 1.

 

 

 

Trust me, if your modem has that puma 6 chipset (which it does) then it is 95% certain that is your problem!

 

 

https://www.amazon.com/TP-Link-Download-Certified-Spectrum-TC-7610/dp/B010Q29YF8/ref=sr_1_1?ie=UTF8&qid=1516997383&sr=8-1&keywords=TC-7610

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...