Jump to content
In 3 days you will no longer be able to login to the forum using your display name, you will then be required to use your email address to login. This is for security purposes and will take effect on 15th Nov 2024. ×

Post your Internet Diagnosis results


Guest Netduma Luke

Recommended Posts

  • Replies 193
  • Created
  • Last Reply

Isp's have different routing some have more hops than others as long as they are fast servers you wont see much ms between them. Only worry if one of the hops is causing a high rise in ping affecting the final ping to the destination.

 

Sometimes the hops (server) might show higher ping times because they are set not to have high priorty for pings.

 

As long as the destination is showing the expected ping time your good to go.

Link to comment
Share on other sites

  • 3 weeks later...

My internet is awful, I don't know how it looks this good.

You do not need a high speed connection for gaming , you just need a steady ping with low jitter and no packet loss and you connection is fine on these things.

Link to comment
Share on other sites

Ping Jitter Spikes Packet Loss Good Ok Bad No Loss

 

Ping

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=54 time=25.549 ms
64 bytes from 8.8.8.8: seq=1 ttl=54 time=39.589 ms
64 bytes from 8.8.8.8: seq=2 ttl=54 time=24.840 ms
64 bytes from 8.8.8.8: seq=3 ttl=54 time=36.888 ms
64 bytes from 8.8.8.8: seq=4 ttl=54 time=24.380 ms
64 bytes from 8.8.8.8: seq=5 ttl=54 time=24.193 ms
64 bytes from 8.8.8.8: seq=6 ttl=54 time=48.928 ms
64 bytes from 8.8.8.8: seq=7 ttl=54 time=23.728 ms
64 bytes from 8.8.8.8: seq=8 ttl=54 time=23.479 ms
64 bytes from 8.8.8.8: seq=9 ttl=54 time=23.292 ms
64 bytes from 8.8.8.8: seq=10 ttl=54 time=23.005 ms
64 bytes from 8.8.8.8: seq=11 ttl=54 time=22.850 ms
64 bytes from 8.8.8.8: seq=12 ttl=54 time=22.574 ms
64 bytes from 8.8.8.8: seq=13 ttl=54 time=22.335 ms
64 bytes from 8.8.8.8: seq=14 ttl=54 time=63.210 ms
64 bytes from 8.8.8.8: seq=15 ttl=54 time=41.888 ms
64 bytes from 8.8.8.8: seq=16 ttl=54 time=21.717 ms
64 bytes from 8.8.8.8: seq=17 ttl=54 time=21.861 ms
64 bytes from 8.8.8.8: seq=18 ttl=54 time=41.103 ms
64 bytes from 8.8.8.8: seq=19 ttl=54 time=24.331 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 21.717/29.987/63.210 ms

Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 192.168.1.1 0.336 ms 0.271 ms 0.247 ms
2 10.0.0.1 5.137 ms 5.377 ms 4.681 ms
3 69.248.180.1 64.832 ms 29.522 ms 39.745 ms
4 68.85.76.177 14.957 ms 18.739 ms 16.922 ms
5 68.86.152.26 14.388 ms 17.350 ms 68.85.63.61 16.278 ms
6 68.85.63.57 19.721 ms 68.85.63.193 19.737 ms 68.85.63.57 19.577 ms
7 4.68.71.121 19.890 ms 19.533 ms 33.187 ms
8 4.69.138.228 20.502 ms 39.709 ms 28.434 ms
9 4.69.138.228 26.964 ms 23.174 ms 20.352 ms
10 72.14.203.136 25.961 ms 39.471 ms 24.455 ms
11 209.85.244.139 25.310 ms 209.85.244.141 54.005 ms 25.191 ms
12 8.8.8.8 19.796 ms 19.682 ms 23.693 ms

 

 

Got a new modem because I was having 3,000ms ping spikes and packet loss, this new one isn't much better.

Link to comment
Share on other sites

Ping Jitter Spikes Packet Loss Good Ok Bad No Loss

 

Ping

PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=0 ttl=54 time=25.549 ms

64 bytes from 8.8.8.8: seq=1 ttl=54 time=39.589 ms

64 bytes from 8.8.8.8: seq=2 ttl=54 time=24.840 ms

64 bytes from 8.8.8.8: seq=3 ttl=54 time=36.888 ms

64 bytes from 8.8.8.8: seq=4 ttl=54 time=24.380 ms

64 bytes from 8.8.8.8: seq=5 ttl=54 time=24.193 ms

64 bytes from 8.8.8.8: seq=6 ttl=54 time=48.928 ms

64 bytes from 8.8.8.8: seq=7 ttl=54 time=23.728 ms

64 bytes from 8.8.8.8: seq=8 ttl=54 time=23.479 ms

64 bytes from 8.8.8.8: seq=9 ttl=54 time=23.292 ms

64 bytes from 8.8.8.8: seq=10 ttl=54 time=23.005 ms

64 bytes from 8.8.8.8: seq=11 ttl=54 time=22.850 ms

64 bytes from 8.8.8.8: seq=12 ttl=54 time=22.574 ms

64 bytes from 8.8.8.8: seq=13 ttl=54 time=22.335 ms

64 bytes from 8.8.8.8: seq=14 ttl=54 time=63.210 ms

64 bytes from 8.8.8.8: seq=15 ttl=54 time=41.888 ms

64 bytes from 8.8.8.8: seq=16 ttl=54 time=21.717 ms

64 bytes from 8.8.8.8: seq=17 ttl=54 time=21.861 ms

64 bytes from 8.8.8.8: seq=18 ttl=54 time=41.103 ms

64 bytes from 8.8.8.8: seq=19 ttl=54 time=24.331 ms

 

--- 8.8.8.8 ping statistics ---

20 packets transmitted, 20 packets received, 0% packet loss

round-trip min/avg/max = 21.717/29.987/63.210 ms

Trace

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

1 192.168.1.1 0.336 ms 0.271 ms 0.247 ms

2 10.0.0.1 5.137 ms 5.377 ms 4.681 ms

3 69.248.180.1 64.832 ms 29.522 ms 39.745 ms

4 68.85.76.177 14.957 ms 18.739 ms 16.922 ms

5 68.86.152.26 14.388 ms 17.350 ms 68.85.63.61 16.278 ms

6 68.85.63.57 19.721 ms 68.85.63.193 19.737 ms 68.85.63.57 19.577 ms

7 4.68.71.121 19.890 ms 19.533 ms 33.187 ms

8 4.69.138.228 20.502 ms 39.709 ms 28.434 ms

9 4.69.138.228 26.964 ms 23.174 ms 20.352 ms

10 72.14.203.136 25.961 ms 39.471 ms 24.455 ms

11 209.85.244.139 25.310 ms 209.85.244.141 54.005 ms 25.191 ms

12 8.8.8.8 19.796 ms 19.682 ms 23.693 ms

 

 

Got a new modem because I was having 3,000ms ping spikes and packet loss, this new one isn't much better.

Who's your internet provider?

Link to comment
Share on other sites


These are my results, i have no idea what all those numbers are. lol

 

file:///Users/hector/Downloads/Internet%20Diagnosis.pdf

 

 


file:///Users/hector/Desktop/picture%202.png

file:///Users/hector/Desktop/picture%201.png

 

ok i have realized i have no idea how to post a picture, sad. lol

Link to comment
Share on other sites

  • Netduma Staff

 

These are my results, i have no idea what all those numbers are. lol
 
file:///Users/hector/Downloads/Internet%20Diagnosis.pdf
 
 
file:///Users/hector/Desktop/picture%202.png
file:///Users/hector/Desktop/picture%201.png
 
ok i have realized i have no idea how to post a picture, sad. lol

 

 

Hehe, if you want to post pics look here :)

Link to comment
Share on other sites

Thanks Crossy,

 

Take 2!!

1433354109-U2171.png

 

1433354148-U2171.png

 

Sorry for these big pictures, I do not know how to make them smaller. Better said, i have no clue what i am doing. So what are your thoughts on these results? I have no idea what all these numbers are lol.

Link to comment
Share on other sites

  • Netduma Staff

Sorry for these big pictures, I do not know how to make them smaller. Better said, i have no clue what i am doing. So what are your thoughts on these results? I have no idea what all these numbers are lol.

 

Those results look alright. Your ping is relatively low, there was no packet loss and there was only a little but of jitter. And I don't think it is possible to resize the pics on the forum - you have to do it before you upload them which is a bit of a pain :)

Link to comment
Share on other sites

Always wondered why there is a small jump on the trace route after 3 and 4 dont respond.

This is from VM in the UK.

 

Ping

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=56 time=19.411 ms
64 bytes from 8.8.8.8: seq=1 ttl=56 time=19.475 ms
64 bytes from 8.8.8.8: seq=2 ttl=56 time=19.262 ms
64 bytes from 8.8.8.8: seq=3 ttl=56 time=19.027 ms
64 bytes from 8.8.8.8: seq=4 ttl=56 time=19.371 ms
64 bytes from 8.8.8.8: seq=5 ttl=56 time=20.952 ms
64 bytes from 8.8.8.8: seq=6 ttl=56 time=20.767 ms
64 bytes from 8.8.8.8: seq=7 ttl=56 time=21.123 ms
64 bytes from 8.8.8.8: seq=8 ttl=56 time=20.865 ms
64 bytes from 8.8.8.8: seq=9 ttl=56 time=20.912 ms
64 bytes from 8.8.8.8: seq=10 ttl=56 time=20.703 ms
64 bytes from 8.8.8.8: seq=11 ttl=56 time=20.675 ms
64 bytes from 8.8.8.8: seq=12 ttl=56 time=20.390 ms
64 bytes from 8.8.8.8: seq=13 ttl=56 time=20.650 ms
64 bytes from 8.8.8.8: seq=14 ttl=56 time=20.247 ms
64 bytes from 8.8.8.8: seq=15 ttl=56 time=20.208 ms
64 bytes from 8.8.8.8: seq=16 ttl=56 time=20.268 ms
64 bytes from 8.8.8.8: seq=17 ttl=56 time=20.502 ms
64 bytes from 8.8.8.8: seq=18 ttl=56 time=20.233 ms
64 bytes from 8.8.8.8: seq=19 ttl=56 time=20.006 ms

--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 19.027/20.252/21.123 ms

Trace

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
1 10.143.8.1 6.501 ms 5.688 ms 6.124 ms
2 81.97.50.129 8.179 ms 7.387 ms 7.806 ms
3 * * *
4 * * *
5 213.105.159.50 18.389 ms 19.800 ms 19.739 ms
6 212.250.14.246 20.291 ms 19.376 ms 213.104.85.102 19.883 ms
7 216.239.47.219 20.072 ms 216.239.47.223 20.301 ms 216.239.47.221 19.475 ms
8 209.85.249.191 19.440 ms 72.14.237.41 20.248 ms 216.239.47.53 20.625 ms
9 8.8.8.8 20.486 ms 20.094 ms 19.547 ms
 
Link to comment
Share on other sites

  • Administrators

Derek, the Internet Diagnosis test is a pure test of your Internet. It disables all devices so they can't influence the test. Unfortunately the only person that can fix it is your ISP. Can you contact them and give them the results of the test. Let them know its simply a ping to google with no other traffic allowed through. 

Link to comment
Share on other sites

  • 1 month later...

Archived

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


×
×
  • Create New...