Jump to content

Packet loss help


Recommended Posts

I am experiencing a packet loss of between 5 and 10 everytime i run a netduma diagnostic . I have tried turning my netduma off and on and also a factory reset , any ideas how to fix this . Thanks . Update on my xbox one it says zero packet loss but when i run a duma diagnostics it says different .

Link to comment
Share on other sites

I am experiencing a packet loss of between 5 and 10 everytime i run a netduma diagnostic . I have tried turning my netduma off and on and also a factory reset , any ideas how to fix this . Thanks . Update on my xbox one it says zero packet loss but when i run a duma diagnostics it says different .

 

Could you please copy and paste your duma internet diagnostic test?

Link to comment
Share on other sites

 

Netduma Logo

Ping Diagnostics

Run Test

Ping Good

Jitter Exceptional

Spikes Exceptional

Packet Loss 7

 

Show Details

Ping

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=1 ttl=51 time=27.352 ms

64 bytes from 8.8.8.8: seq=3 ttl=51 time=27.341 ms

64 bytes from 8.8.8.8: seq=4 ttl=51 time=27.113 ms

64 bytes from 8.8.8.8: seq=5 ttl=51 time=27.205 ms

64 bytes from 8.8.8.8: seq=7 ttl=51 time=27.193 ms

64 bytes from 8.8.8.8: seq=9 ttl=51 time=27.586 ms

64 bytes from 8.8.8.8: seq=10 ttl=51 time=27.265 ms

64 bytes from 8.8.8.8: seq=11 ttl=51 time=27.332 ms

64 bytes from 8.8.8.8: seq=12 ttl=51 time=27.078 ms

64 bytes from 8.8.8.8: seq=14 ttl=51 time=27.126 ms

64 bytes from 8.8.8.8: seq=15 ttl=51 time=27.369 ms

64 bytes from 8.8.8.8: seq=16 ttl=51 time=27.876 ms

64 bytes from 8.8.8.8: seq=17 ttl=51 time=27.136 ms

64 bytes from 8.8.8.8: seq=18 ttl=51 time=27.193 ms

64 bytes from 8.8.8.8: seq=19 ttl=51 time=27.256 ms

64 bytes from 8.8.8.8: seq=20 ttl=51 time=27.460 ms

64 bytes from 8.8.8.8: seq=22 ttl=51 time=27.562 ms

64 bytes from 8.8.8.8: seq=23 ttl=51 time=27.399 ms

 

--- 8.8.8.8 ping statistics ---

25 packets transmitted, 18 packets received, 28% packet loss

round-trip min/avg/max = 27.078/27.324/27.876 ms

Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.1.254 0.741 ms 0.631 ms 0.606 ms

2 217.32.142.197 11.044 ms 10.734 ms 10.451 ms

3 217.32.142.222 11.467 ms 11.324 ms 11.468 ms

4 212.140.206.50 18.928 ms 18.638 ms 18.468 ms

5 31.55.165.45 16.657 ms 16.706 ms 16.432 ms

6 31.55.165.107 17.122 ms 16.933 ms 16.931 ms

7 109.159.250.100 16.498 ms 109.159.250.50 16.859 ms 109.159.250.82 16.676 ms

8 109.159.250.13 28.338 ms 109.159.250.34 24.233 ms 109.159.255.147 25.552 ms

9 109.159.254.102 26.334 ms 109.159.254.169 25.386 ms 25.177 ms

10 195.99.126.185 24.590 ms 27.400 ms 24.753 ms

11 216.239.54.223 24.106 ms 24.977 ms 216.239.54.247 25.005 ms

12 216.239.58.61 27.863 ms 216.239.58.51 27.603 ms 216.239.57.89 26.402 ms

13 * 8.8.8.8 26.200 ms 29.676 ms

Online Gaming Services

Service

Status

Xbox Live Click for details

Play station network Click for details

© Netduma Software Ltd.

R1 debug version 1.03.6g running on rb-951g-2hnd .

Credits

Link to comment
Share on other sites

This maybe Google playing up again we have seen a lot of problems with them lately.

 

You could download ping plotter pro then you can ping 8.8.8.8 so we can see where the issue is and you could also ping other sites like twitter.com

 

https://www.pingplotter.com/download/

 

Type the IP or URL into target and press go.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...