Jump to content

excessive jitter


smolina1212

Recommended Posts

that's all local backbone all the way to 8.8.8.8

 

Here's what i'd do

1. Register an account at http://www.speedtest.net/

2. Go to http://www.pingtest.net/

     2.1 run 5 of these tests, or as many as you can a day for 5 days.

     2.2 You can use this as evidence against your ISP anything lower than a B rating is fixable by ISP.

3. Go here http://www.dslreports.com/pingtest

     3.1 Run a couple of those tests as well.

 

The reason I recommend the above is this line from your traceroute:

 

3 te-9-2-ur01.mcgayhesvlle.va.richmond.comcast.net (68.85.226.125) 27.214 ms 41.143 ms 14.979 ms

 

The 41.143ms is way over 27ms or 15ms...that's a lot of jitter and it's on your first hop, meaning it is your local node.  

 

This is very very suspicious to me

 

i'll be posting this as well, nothing in the above is anything dangerous

Link to comment
Share on other sites

I think we should have a test your i.s.p latency and jitter sticky , as i notice many threads with people saying why is the netduma not working for me and in my mind the jitter problem is quite large spread with people not testing how smooth their connection is before blaming the duma or psn/xbox live.

 

A thread sticky in general as this is probaly the most looked at forum,  Itcould be useful to point to instead of us having to repete the steps on how to do this for windows and mac in multiple threads, what do you think guys?

Link to comment
Share on other sites

I think we should have a test your i.s.p latency and jitter sticky , as i notice many threads with people saying why is the netduma not working for me and in my mind the jitter problem is quite large spread with people not testing how smooth their connection is before blaming the duma or psn/xbox live.

 

A thread sticky in general as this is probaly the most looked at forum,  Itcould be useful to point to instead of us having to repete the steps on how to do this for windows and mac in multiple threads, what do you think guys?

Agreed. Also could there be a post with a plug in to the xbox / psn current status? No idea if such a post on forum would auto update in live time but at worst could be a link to their current status pages.

Link to comment
Share on other sites

Guest Netduma Luke

I think we should have a test your i.s.p latency and jitter sticky , as i notice many threads with people saying why is the netduma not working for me and in my mind the jitter problem is quite large spread with people not testing how smooth their connection is before blaming the duma or psn/xbox live.

 

A thread sticky in general as this is probaly the most looked at forum,  Itcould be useful to point to instead of us having to repete the steps on how to do this for windows and mac in multiple threads, what do you think guys?

Agreed. Also could there be a post with a plug in to the xbox / psn current status? No idea if such a post on forum would auto update in live time but at worst could be a link to their current status pages.

Great idea. I'll ask one of the guys to see if they can get this up soon.

Link to comment
Share on other sites

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets
 1  r1.lan (192.168.88.1)  1.664 ms  0.717 ms  0.662 ms
 2  69.142.208.1 (69.142.208.1)  9.136 ms  10.701 ms  11.498 ms
 3  xe-5-3-0-sur01.absecon.nj.panjde.comcast.net (68.86.154.173)  9.376 ms  9.464 ms  11.704 ms
 4  ae-5-0-ar03.audubon.nj.panjde.comcast.net (68.85.63.165)  10.879 ms  12.438 ms  11.820 ms
 5  ae10.bar1.philadelphia1.level3.net (4.68.71.121)  16.929 ms  31.609 ms  13.128 ms
 6  * * *
 7  * * *
 8  google-level3-30gb.newyork1.level3.net (4.68.70.54)  20.927 ms  15.700 ms  13.915 ms
 9  209.85.244.149 (209.85.244.149)  15.498 ms  15.899 ms  15.732 ms
10  google-public-dns-a.google.com (8.8.8.8)  14.342 ms  16.183 ms  14.474 ms
 

These are the results to my 8.8.8.8 test, is this the problem?

Link to comment
Share on other sites

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets

 1  r1.lan (192.168.88.1)  1.664 ms  0.717 ms  0.662 ms

 2  69.142.208.1 (69.142.208.1)  9.136 ms  10.701 ms  11.498 ms

 3  xe-5-3-0-sur01.absecon.nj.panjde.comcast.net (68.86.154.173)  9.376 ms  9.464 ms  11.704 ms

 4  ae-5-0-ar03.audubon.nj.panjde.comcast.net (68.85.63.165)  10.879 ms  12.438 ms  11.820 ms

 5  ae10.bar1.philadelphia1.level3.net (4.68.71.121)  16.929 ms  31.609 ms  13.128 ms

 6  * * *

 7  * * *

 8  google-level3-30gb.newyork1.level3.net (4.68.70.54)  20.927 ms  15.700 ms  13.915 ms

 9  209.85.244.149 (209.85.244.149)  15.498 ms  15.899 ms  15.732 ms

10  google-public-dns-a.google.com (8.8.8.8)  14.342 ms  16.183 ms  14.474 ms

 

These are the results to my 8.8.8.8 test, is this the problem?

 

No that looks good

Link to comment
Share on other sites

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets

 1  r1.lan (192.168.88.1)  1.664 ms  0.717 ms  0.662 ms

 2  69.142.208.1 (69.142.208.1)  9.136 ms  10.701 ms  11.498 ms

 3  xe-5-3-0-sur01.absecon.nj.panjde.comcast.net (68.86.154.173)  9.376 ms  9.464 ms  11.704 ms

 4  ae-5-0-ar03.audubon.nj.panjde.comcast.net (68.85.63.165)  10.879 ms  12.438 ms  11.820 ms

 5  ae10.bar1.philadelphia1.level3.net (4.68.71.121)  16.929 ms  31.609 ms  13.128 ms

 6  * * *

 7  * * *

 8  google-level3-30gb.newyork1.level3.net (4.68.70.54)  20.927 ms  15.700 ms  13.915 ms

 9  209.85.244.149 (209.85.244.149)  15.498 ms  15.899 ms  15.732 ms

10  google-public-dns-a.google.com (8.8.8.8)  14.342 ms  16.183 ms  14.474 ms

 

These are the results to my 8.8.8.8 test, is this the problem?

 

 

 

 5  ae10.bar1.philadelphia1.level3.net (4.68.71.121)  16.929 ms  31.609 ms  13.128 ms

you had a 16ms difference in ping on this hop, also not good.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...