Jump to content

ATT UVERSE / R1 BLOPS3...New R1 Ping Diagnostics BAD!


Recommended Posts

Hello,

Yesterday I received my R1. Was really excited, until I found it has not helped one bit. I'm having terrible connection issues on XB1 and BLOPS3. Ping is outrageous and the lag compensation basically makes me lose every single gunfight. Almost as there is a 1-1.5 second delay before shots even register.

My internet is incredible. 1G up and down. With a ping of 2-4. But on a hard wired connection, in game it showing my ping over 100. And the lag is unbearable.

 

Also under the netduma settings on ping diagnostics when it's run it says. Ping- good. Jitter-ok. Spikes- BAD packet loss Bad. Why is this happening, as when I check it on the console it says 0 packet loss and the ping is fine.

 

Anyone have any ideas? I'm located in USA Texas. Geo filter is just a little bigger then the state, ping Asia it set to 30.

Link to comment
Share on other sites

I've updated the router. The bottom of the page says 1.03.5m.

 

Step 2 says click on host filtering, and well once I do that and hard refresh the page, nothing happens. No map or anything comes up. Just a losing bar at the top of the screen that's flashing. I've tried this 8 times and no luck. So I guess I'm stuck unless someone knows how to fix this......

Link to comment
Share on other sites

  • Netduma Staff

Ok unplugged it and now it's allowing me to see the Geo filtering page. I followed all of the instructions. And it's still exactly the same problem. Ran the ping diagnostics again. Spikes and packet loss are both BAD. Ping is good and jitter is ok.

 

Any ideas?

 

Can you run an internet diagnostics, press details then post the results here please :) Also are all devices connected to the Netduma?

Link to comment
Share on other sites

Today, for some reason.....I ran the test in safari and it never finishes. Just loads for 30 mins. Hop into Firefox, and it loads for about 25 mins and finally finishes and says. ping- exceptional, jitter- exceptional, spikes, exceptional, packet loss- no loss.

 

How come with each browser it does something different? That shouldn't happen.

Link to comment
Share on other sites

  • Netduma Staff

Today, for some reason.....I ran the test in safari and it never finishes. Just loads for 30 mins. Hop into Firefox, and it loads for about 25 mins and finally finishes and says. ping- exceptional, jitter- exceptional, spikes, exceptional, packet loss- no loss.

 

How come with each browser it does something different? That shouldn't happen.

 

No, that shouldn't happen. Can you try on a computer wired to the Netduma and see what happens.

Link to comment
Share on other sites

ok, i tried it hard wired on all the different browsers and it is no different. the only one that seems to work is firefox. safari does not work. it just loads and loads and loads... also a little info as well, when i was doing the update for the R1 the only browser that would do it was safai. firefox did not work for that.

 

anyways here is the info from the test on firefox.

Ping Jitter Spikes Packet Loss Exceptional Exceptional Exceptional No Loss

Show Details

Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=55 time=9.082 ms
64 bytes from 8.8.8.8: seq=1 ttl=55 time=8.663 ms
64 bytes from 8.8.8.8: seq=2 ttl=55 time=9.000 ms
64 bytes from 8.8.8.8: seq=3 ttl=55 time=8.931 ms
64 bytes from 8.8.8.8: seq=4 ttl=55 time=9.404 ms
64 bytes from 8.8.8.8: seq=5 ttl=55 time=9.144 ms
64 bytes from 8.8.8.8: seq=6 ttl=55 time=10.872 ms
64 bytes from 8.8.8.8: seq=7 ttl=55 time=8.975 ms
64 bytes from 8.8.8.8: seq=8 ttl=55 time=8.702 ms
64 bytes from 8.8.8.8: seq=9 ttl=55 time=8.742 ms
64 bytes from 8.8.8.8: seq=10 ttl=55 time=8.799 ms
64 bytes from 8.8.8.8: seq=11 ttl=55 time=8.763 ms
64 bytes from 8.8.8.8: seq=12 ttl=55 time=8.761 ms
64 bytes from 8.8.8.8: seq=13 ttl=55 time=8.823 ms
64 bytes from 8.8.8.8: seq=14 ttl=55 time=8.781 ms
64 bytes from 8.8.8.8: seq=15 ttl=55 time=8.814 ms
64 bytes from 8.8.8.8: seq=16 ttl=55 time=8.890 ms
64 bytes from 8.8.8.8: seq=17 ttl=55 time=8.857 ms
64 bytes from 8.8.8.8: seq=18 ttl=55 time=8.875 ms
64 bytes from 8.8.8.8: seq=19 ttl=55 time=8.877 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 8.663/8.987/10.872 ms
Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 162.237.204.1 8.514 ms 8.780 ms 14.910 ms
2 71.149.77.146 4.470 ms 2.718 ms 2.553 ms
3 * * *
4 12.83.68.145 5.834 ms 12.83.68.137 2.385 ms 4.954 ms
5 12.122.138.189 8.145 ms 8.190 ms 8.005 ms
6 * * *
7 216.239.54.19 8.920 ms 216.239.54.105 8.618 ms 216.239.40.197 9.480 ms
8 64.233.175.11 8.964 ms 72.14.234.105 8.761 ms 72.14.234.145 9.154 ms
9 8.8.8.8 8.612 ms 8.717 ms 8.801 ms

Link to comment
Share on other sites

there are numerous other things that only work on certain browsers. example. geo filter will not show up on safari, but works fine on firefox. before the update, they both worked fine on all my devices. i have the safari internet diagnostics still running and has yet to finish and its been 45 mins. firefox takes about 2 and works fine. really odd this is happening. i have 3 different browsers  giving different info.

 

on the xbox one console if you open a browser and run the diagnostics it gives GOOD, OK, BAD BAD with an error message.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...