Remington-Ocelot Posted February 12, 2015 Posted February 12, 2015 Still trying to fix my results Isp: Verizon fios 50/50 connection
Guest Netduma Fraser Posted February 12, 2015 Posted February 12, 2015 Still trying to fix my results Isp: Verizon fios 50/50 connection Thats a pretty high base ping, where are you located?
a1pha TG Posted February 12, 2015 Posted February 12, 2015 Also have FiOS 50/50 I called them and they say it's not on there end it's somewhere between them and the google server and it's not there problem. I had them test and they only test to THEIR closest server which is only getting results of 10ms or less. Then they basically told me that I needed to disconnect any secondary router that I had hooked up because they could tell that it was hooked up still while they were testing. And my problem was in that router not theirs.=(
Guest Netduma Fraser Posted February 12, 2015 Posted February 12, 2015 Also have FiOS 50/50 I called them and they say it's not on there end it's somewhere between them and the google server and it's not there problem. I had them test and they only test to THEIR closest server which is only getting results of 10ms or less. Then they basically told me that I needed to disconnect any secondary router that I had hooked up because they could tell that it was hooked up still while they were testing. And my problem was in that router not theirs.=( All it does is ping Google, yours is higher than most. It could be your location, its usually a good test. Do they recommend somewhere else to ping?
a1pha TG Posted February 12, 2015 Posted February 12, 2015 I know that it's going to Google and they (Verizon) test to their servers in NYC and I'm in Syracuse NY. About 200 miles from NYC.
Remington-Ocelot Posted February 12, 2015 Posted February 12, 2015 Here you go Iain my ping is getting a little better from bad to good but would like to get it to exceptional
Guest Netduma Fraser Posted February 12, 2015 Posted February 12, 2015 I know that it's going to Google and they (Verizon) test to their servers in NYC and I'm in Syracuse NY. About 200 miles from NYC. I meant did Verizon recommend you yourself ping somewhere other than Google for a test?
Remington-Ocelot Posted February 12, 2015 Posted February 12, 2015 Same here Im in Southern California
a1pha TG Posted February 12, 2015 Posted February 12, 2015 They basically said they didn't care because 10ms to their closest server wasn't bad. They had me use Verizon.com/speedtest which went to NYC.
paradosis Posted February 12, 2015 Posted February 12, 2015 Same here Im in Southern California Iain, I'm Remington's FiOS tech. If you want me to test anything, let me know. I can start sending this up the path, but my guess is that the ping to the verizon server is 10 ms and they won't do much. It could be an edge server somewhere else... But not sure where to go from here.
a1pha TG Posted February 12, 2015 Posted February 12, 2015 Let me know if there is any solutions because they said it would cost almost $200 to send a tech out to my house without any major issues.
Guest Netduma_Iain Posted February 12, 2015 Posted February 12, 2015 Hi Remington/Paradosis/Alpha All the test does is show you the ping to google/8.8.8.8 when nothing is using the Internet. That is all, I can't comment further than that. I would personally not recommend incurring any further costs with the issue. It will depend on the agreed services with your ISP and neither I or Netduma can advise on that. All it says is your ping to google thats it. I have an idea for a more comprehensive test that I'll try in the coming weeks. In the meantime alpha, Remington please signup here we can try a "local" experiment. http://forum.netduma.com/topic/942-new-york-california-experiment/
AOrtiz Posted February 12, 2015 Posted February 12, 2015 Ping Jitter Spikes Packet Loss Exceptional Exceptional Exceptional No Loss Show Details PingPING 8.8.8.8 (8.8.8.8): 56 data bytes64 bytes from 8.8.8.8: seq=0 ttl=58 time=14.045 ms64 bytes from 8.8.8.8: seq=1 ttl=58 time=13.771 ms64 bytes from 8.8.8.8: seq=2 ttl=58 time=17.907 ms64 bytes from 8.8.8.8: seq=3 ttl=58 time=17.036 ms64 bytes from 8.8.8.8: seq=4 ttl=58 time=16.863 ms64 bytes from 8.8.8.8: seq=5 ttl=58 time=16.691 ms64 bytes from 8.8.8.8: seq=6 ttl=58 time=16.502 ms64 bytes from 8.8.8.8: seq=7 ttl=58 time=16.396 ms64 bytes from 8.8.8.8: seq=8 ttl=58 time=16.171 ms64 bytes from 8.8.8.8: seq=9 ttl=58 time=16.017 ms64 bytes from 8.8.8.8: seq=10 ttl=58 time=15.821 ms64 bytes from 8.8.8.8: seq=11 ttl=58 time=15.655 ms64 bytes from 8.8.8.8: seq=12 ttl=58 time=15.504 ms64 bytes from 8.8.8.8: seq=13 ttl=58 time=14.620 ms64 bytes from 8.8.8.8: seq=14 ttl=58 time=15.073 ms64 bytes from 8.8.8.8: seq=15 ttl=58 time=14.177 ms64 bytes from 8.8.8.8: seq=16 ttl=58 time=14.029 ms64 bytes from 8.8.8.8: seq=17 ttl=58 time=13.845 ms64 bytes from 8.8.8.8: seq=18 ttl=58 time=13.701 ms64 bytes from 8.8.8.8: seq=19 ttl=58 time=13.521 ms--- 8.8.8.8 ping statistics ---20 packets transmitted, 20 packets received, 0% packet lossround-trip min/avg/max = 13.521/15.367/17.907 ms Tracetraceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets1 192.168.1.1 0.436 ms 0.250 ms 0.376 ms2 108.7.229.1 4.423 ms 7.527 ms 7.598 ms3 130.81.139.16 9.365 ms 8.521 ms 9.445 ms4 130.81.151.76 26.785 ms 130.81.209.94 88.562 ms 8.627 ms5 152.63.20.117 17.491 ms 16.123 ms 17.117 ms6 152.63.29.230 15.277 ms 152.63.19.61 16.885 ms 152.63.19.118 12.215 ms7 204.148.18.206 19.598 ms 32.815 ms 28.031 ms8 64.233.175.45 26.421 ms 64.233.175.63 64.706 ms 64.233.175.89 20.409 ms9 8.8.8.8 103.017 ms 17.075 ms 16.181 ms
LXA KinG LXA Posted February 19, 2015 Posted February 19, 2015 Ping Jitter Spikes Packet Loss Good Ok Ok No Loss Show Details PingPING 8.8.8.8 (8.8.8.8): 56 data bytes64 bytes from 8.8.8.8: seq=0 ttl=58 time=28.365 ms 64 bytes from 8.8.8.8: seq=1 ttl=58 time=54.744 ms 64 bytes from 8.8.8.8: seq=2 ttl=56 time=24.146 ms 64 bytes from 8.8.8.8: seq=3 ttl=58 time=34.442 ms 64 bytes from 8.8.8.8: seq=4 ttl=58 time=43.120 ms 64 bytes from 8.8.8.8: seq=5 ttl=56 time=19.025 ms 64 bytes from 8.8.8.8: seq=6 ttl=56 time=17.771 ms 64 bytes from 8.8.8.8: seq=7 ttl=56 time=17.365 ms 64 bytes from 8.8.8.8: seq=8 ttl=58 time=50.832 ms 64 bytes from 8.8.8.8: seq=9 ttl=58 time=53.299 ms 64 bytes from 8.8.8.8: seq=10 ttl=58 time=25.387 ms 64 bytes from 8.8.8.8: seq=11 ttl=58 time=33.986 ms 64 bytes from 8.8.8.8: seq=12 ttl=56 time=27.638 ms 64 bytes from 8.8.8.8: seq=13 ttl=56 time=47.443 ms 64 bytes from 8.8.8.8: seq=14 ttl=58 time=27.399 ms 64 bytes from 8.8.8.8: seq=15 ttl=56 time=19.246 ms 64 bytes from 8.8.8.8: seq=16 ttl=58 time=25.670 ms 64 bytes from 8.8.8.8: seq=17 ttl=56 time=21.120 ms 64 bytes from 8.8.8.8: seq=18 ttl=58 time=28.026 ms 64 bytes from 8.8.8.8: seq=19 ttl=58 time=25.183 ms This is the best test i got.. no idea whats going on.. I'm in northern Florida USA on Comcast internet 50/10.... my other tests were bad and some even terrible
PuppetMaster Posted February 19, 2015 Posted February 19, 2015 Capture.PNG5e4f7ce64a65c95b9b74e9f8f40800fe-16-01-2015.png I have 150/20 & I run around 30/5(PS4). How the hell are you getting those speeds?
Guest Netduma_Iain Posted February 19, 2015 Posted February 19, 2015 LXA King, give your ISP a call, and tell them your latency results are not the best, is there something wrong in your area.
JP003 Posted February 21, 2015 Posted February 21, 2015 To be honest this latest version is a pile of poo!! The geo filter doesn't work anymore on my ps4 i am constantly being put in games outside the filter!!! Dont understand why its happening and is really starting to annoy me. I had no problems with any of the other software versions but since Advanced Warfare has had the last patch update my connection is absolutely rubbish. Ive check using the diagnostics and my internet connection is good. Why doesnt the geo filter work anymore!!!
Guest Netduma_Iain Posted February 21, 2015 Posted February 21, 2015 Hi JP, Sorry to hear that, if you're having issues please start a new thread and let us know as soon as possible. Few things you may have not done: Can you select "Xbox Live PA" instead of "Xbox live" OR "Playstation Network" PA" instead of "Playstation Network", so replace the old one Go to "Settings > Misc" and click apply in the cloud setting section Set your ping-assist to 40ms Then refresh the page, that should sort any issues you're having with the geo-filter. Let me know in a new thread if that doesn't help please.
JP003 Posted February 21, 2015 Posted February 21, 2015 Hi JP, Sorry to hear that, if you're having issues please start a new thread and let us know as soon as possible. Few things you may have not done: Can you select "Xbox Live PA" instead of "Xbox live" OR "Playstation Network" PA" instead of "Playstation Network", so replace the old one Go to "Settings > Misc" and click apply in the cloud setting section Set your ping-assist to 40ms Then refresh the page, that should sort any issues you're having with the geo-filter. Let me know in a new thread if that doesn't help please. Ill start a new thread, i have emailed you Iain
Cajun72 Posted February 25, 2015 Posted February 25, 2015 This is what I got tonight when running although I did seem to have lag tonight with black ops 2 on ps3 which is unusual? Ping PING 8.8.8.8 (8.8.8.8): 56 data bytes64 bytes from 8.8.8.8: seq=0 ttl=56 time=14.168 ms 64 bytes from 8.8.8.8: seq=1 ttl=56 time=14.400 ms 64 bytes from 8.8.8.8: seq=2 ttl=56 time=13.387 ms 64 bytes from 8.8.8.8: seq=3 ttl=56 time=13.055 ms 64 bytes from 8.8.8.8: seq=4 ttl=56 time=13.840 ms 64 bytes from 8.8.8.8: seq=5 ttl=56 time=17.866 ms 64 bytes from 8.8.8.8: seq=6 ttl=56 time=14.551 ms 64 bytes from 8.8.8.8: seq=7 ttl=56 time=13.516 ms 64 bytes from 8.8.8.8: seq=8 ttl=56 time=13.213 ms 64 bytes from 8.8.8.8: seq=9 ttl=56 time=13.546 ms 64 bytes from 8.8.8.8: seq=10 ttl=56 time=13.655 ms 64 bytes from 8.8.8.8: seq=11 ttl=56 time=13.542 ms 64 bytes from 8.8.8.8: seq=12 ttl=56 time=12.971 ms 64 bytes from 8.8.8.8: seq=13 ttl=56 time=13.109 ms 64 bytes from 8.8.8.8: seq=14 ttl=56 time=14.364 ms 64 bytes from 8.8.8.8: seq=15 ttl=56 time=13.327 ms 64 bytes from 8.8.8.8: seq=16 ttl=56 time=13.469 ms 64 bytes from 8.8.8.8: seq=17 ttl=56 time=14.485 ms 64 bytes from 8.8.8.8: seq=18 ttl=56 time=13.223 ms 64 bytes from 8.8.8.8: seq=19 ttl=56 time=13.329 ms --- 8.8.8.8 ping statistics --- 20 packets transmitted, 20 packets received, 0% packet loss round-trip min/avg/max = 12.971/13.850/17.866 ms Tracetraceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets1 195.166.128.195 15.629 ms 12.656 ms 16.485 ms 2 212.159.2.146 13.261 ms 12.199 ms 12.447 ms 3 212.159.0.242 12.124 ms 12.193 ms 12.449 ms 4 72.14.223.32 12.834 ms 13.540 ms 13.143 ms 5 216.239.48.55 13.019 ms 216.239.48.35 13.111 ms 12.893 ms 6 72.14.236.25 13.228 ms 209.85.245.187 13.337 ms 216.239.47.105 16.084 ms 7 8.8.8.8 13.677 ms 12.881 ms 12.921 ms
Guest Netduma_Iain Posted February 26, 2015 Posted February 26, 2015 Looks like a good connection mate. Just keep an eye on it I guess. We will try get long term monitoring soon!
Cajun72 Posted February 26, 2015 Posted February 26, 2015 Cheers I will keep an eye on it. Obviously I don't expect now as I'm sure you're all working hard on future developments but would be very useful to have some time in the future.
Guest Netduma_Iain Posted February 26, 2015 Posted February 26, 2015 Cheers buddy will try get it in as soon as possible
Jstrick17 Posted February 26, 2015 Posted February 26, 2015 At&t Uverse in NW Florida...I hate all you sub 20 pingers, you think you're special!!!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.