ping and internet speed is gone please help

[deadrop]

my internet has basicly died i went from like 60mbps download to like 2 and my ping went from like like 30-40 to like 300-400 i dont know why and my isp is claiming its not them.

i pinged my isp is this the isps fault or mine?
Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=649ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64

[two posts merged by mod]

 

[Olle P]

Way too little info here...
Your speed and ping times while reaching what/where? If you're comparing towards a specific server somewhere then that server can have problems or recently enforced limitations.
Is it between computers within your home?
Do you use a cable network or WiFi?
Do you have a router, modem or what?

 

[brian.h.schaefer]

Need a lot more information to give help on this. The only thing I can tell from the above information is that there MAY be some packet transmission problem. But we need exactly what you are pinging, better yet a tracert, as well as your network configuration.

 

[deadrop]

Can we do this you give me a list of thing you need to help me,i dont know what you would need to help me find the solution to my problem

 

[brian.h.schaefer]

Sure.
#1 I would probably run a tracert command to anything on the internet really. The only thing I would be concerned with is the IP address after your routers IP address, your router is probably 192.168.1.1 (may be different).

#2 Continuosly ping that second IP address to check to see how many latency spikes you get, if any. If you do still get the spikes, this could indicate something is wrong with the router. So you can move to test that. If you do not get these latency spikes then it is probably on the other side of your connection to the ISP in which case you tell your ISP to fix it. Have screenshots to back this up.

#3 Ping the ISP side interface on the router. If there are latency spikes then it is something internal to your network(router, computer, etc.)

 

[brian.h.schaefer]

tracert is performed just like ping. tracert [IP address]

 

[deadrop]

C:\WINDOWS\system32>Tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms LINKSYS00703 [192.168.1.1]
2 11 ms 13 ms 16 ms 10.80.0.1
3 255 ms 14 ms 19 ms ns-hlfx-asr001.eastlink.ca [24.222.226.177]
4 24 ms 27 ms 31 ms ns-hlfx-dr002.ns.eastlink.ca [24.215.102.217]
5 652 ms 588 ms 99 ms ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
6 210 ms 141 ms 127 ms 74.125.52.182
7 371 ms 45 ms 42 ms 108.170.251.53
8 314 ms 53 ms 53 ms 108.170.236.0
9 61 ms 60 ms 57 ms 108.177.3.59
10 59 ms 67 ms 67 ms 216.239.48.6
11 59 ms 58 ms 58 ms 216.239.48.181
12 * * * Request timed out.
13 59 ms 59 ms 65 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=253ms TTL=254
Reply from 10.80.0.1: bytes=32 time=10ms TTL=254
Reply from 10.80.0.1: bytes=32 time=23ms TTL=254
Reply from 10.80.0.1: bytes=32 time=310ms TTL=254

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 310ms, Average = 149ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=17ms TTL=254
Reply from 10.80.0.1: bytes=32 time=19ms TTL=254
Reply from 10.80.0.1: bytes=32 time=13ms TTL=254
Request timed out.

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 19ms, Average = 16ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=14ms TTL=254
Reply from 10.80.0.1: bytes=32 time=19ms TTL=254
Reply from 10.80.0.1: bytes=32 time=12ms TTL=254
Reply from 10.80.0.1: bytes=32 time=17ms TTL=254

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 19ms, Average = 15ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=13ms TTL=254
Reply from 10.80.0.1: bytes=32 time=17ms TTL=254
Reply from 10.80.0.1: bytes=32 time=18ms TTL=254
Reply from 10.80.0.1: bytes=32 time=23ms TTL=254

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 23ms, Average = 17ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=16ms TTL=254
Reply from 10.80.0.1: bytes=32 time=19ms TTL=254
Reply from 10.80.0.1: bytes=32 time=20ms TTL=254
Reply from 10.80.0.1: bytes=32 time=13ms TTL=254

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 20ms, Average = 17ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=312ms TTL=254
Reply from 10.80.0.1: bytes=32 time=81ms TTL=254
Reply from 10.80.0.1: bytes=32 time=18ms TTL=254
Reply from 10.80.0.1: bytes=32 time=20ms TTL=254

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 312ms, Average = 107ms

im not sure what you mean in the 3rd one

 

[brian.h.schaefer]

Ok, that is some good info. There definitely is stuff going on with those 3-7ish hops in the tracert. Hop 2-5ish look like they may be your ISP and those latency numbers are aweful. But you are still getting those when you ping your ISPs first router to you, 10.80.0.1. So that means there might be another problem either in your network or your connection to the ISP. The connection from your computer to your router, 192.168.1.1, looks fine so that PROBABLY narrows the problem down to your router or the ISPs first router.

To test this try to ping the ISPs side port on your router. You can get this address by googling "whatsmyip", that should be it. Ping it, if you still get those latency spikes then it is router.

edit - Just in case, ping your router, 192.168.1.1, and make sure there are no latency spikes.

 

[deadrop]

this is what i got from pinging my router
C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 6ms, Average = 2ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 8ms, Average = 2ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Request timed out.
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

 

[deadrop]

and this is my isp ping
C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=3ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Request timed out.
Reply from 24.89.211.133: bytes=32 time=296ms TTL=64
Request timed out.
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 296ms, Average = 149ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=8ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 8ms, Average = 2ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Request timed out.

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=3ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=19ms TTL=64
Reply from 24.89.211.133: bytes=32 time=3ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=9ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 19ms, Average = 8ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=4ms TTL=64
Reply from 24.89.211.133: bytes=32 time=8ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 8ms, Average = 3ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64

Ping statistics for 24.89.211.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\WINDOWS\system32>ping 24.89.211.133

Pinging 24.89.211.133 with 32 bytes of data:
Reply from 24.89.211.133: bytes=32 time=1ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64
Reply from 24.89.211.133: bytes=32 time=2ms TTL=64

 

[deadrop]

i forgot to mention i am using wifi

 

[brian.h.schaefer]

Those pings to your router look mostly good but those timed out requests could be an issue. Have you tried powering off and on your router?

 

[brian.h.schaefer]

Ugh....

Connect with ethernet and redo all of that stuff.

 

[deadrop]

C:\WINDOWS\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 11 ms 19 ms 17 ms 10.80.0.1
2 12 ms 15 ms 13 ms ns-hlfx-asr001.eastlink.ca [24.222.226.177]
3 24 ms 26 ms 29 ms ns-hlfx-dr002.ns.eastlink.ca [24.215.102.217]
4 24 ms 27 ms 27 ms ns-hlfx-br002.ns.eastlink.ca [24.215.102.221]
5 41 ms 36 ms 38 ms 74.125.52.182
6 38 ms 42 ms 47 ms 108.170.251.53
7 46 ms 70 ms 57 ms 108.170.236.0
8 52 ms 54 ms 57 ms 108.177.3.51
9 64 ms 71 ms 72 ms 216.239.48.2
10 59 ms 58 ms 58 ms 72.14.234.53
11 * * * Request timed out.
12 58 ms 57 ms 57 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=19ms TTL=255
Reply from 10.80.0.1: bytes=32 time=11ms TTL=255
Reply from 10.80.0.1: bytes=32 time=14ms TTL=255
Reply from 10.80.0.1: bytes=32 time=16ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 19ms, Average = 15ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=16ms TTL=255
Reply from 10.80.0.1: bytes=32 time=16ms TTL=255
Reply from 10.80.0.1: bytes=32 time=13ms TTL=255
Reply from 10.80.0.1: bytes=32 time=16ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 16ms, Average = 15ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=17ms TTL=255
Reply from 10.80.0.1: bytes=32 time=11ms TTL=255
Reply from 10.80.0.1: bytes=32 time=11ms TTL=255
Reply from 10.80.0.1: bytes=32 time=12ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 17ms, Average = 12ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=19ms TTL=255
Reply from 10.80.0.1: bytes=32 time=12ms TTL=255
Reply from 10.80.0.1: bytes=32 time=10ms TTL=255
Reply from 10.80.0.1: bytes=32 time=11ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 19ms, Average = 13ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=18ms TTL=255
Reply from 10.80.0.1: bytes=32 time=10ms TTL=255
Reply from 10.80.0.1: bytes=32 time=10ms TTL=255
Reply from 10.80.0.1: bytes=32 time=10ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 18ms, Average = 12ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=19ms TTL=255
Reply from 10.80.0.1: bytes=32 time=13ms TTL=255
Reply from 10.80.0.1: bytes=32 time=15ms TTL=255
Reply from 10.80.0.1: bytes=32 time=12ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 19ms, Average = 14ms

C:\WINDOWS\system32>ping 10.80.0.1

Pinging 10.80.0.1 with 32 bytes of data:
Reply from 10.80.0.1: bytes=32 time=82ms TTL=255
Reply from 10.80.0.1: bytes=32 time=10ms TTL=255
Reply from 10.80.0.1: bytes=32 time=15ms TTL=255
Reply from 10.80.0.1: bytes=32 time=18ms TTL=255

Ping statistics for 10.80.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 82ms, Average = 31ms

C:\WINDOWS\system32>ping 24.89.209.101

Pinging 24.89.209.101 with 32 bytes of data:
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128

Ping statistics for 24.89.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>ping 24.89.209.101

Pinging 24.89.209.101 with 32 bytes of data:
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128

Ping statistics for 24.89.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>ping 24.89.209.101

Pinging 24.89.209.101 with 32 bytes of data:
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128

Ping statistics for 24.89.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>ping 24.89.209.101

Pinging 24.89.209.101 with 32 bytes of data:
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128

Ping statistics for 24.89.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>ping 24.89.209.101

Pinging 24.89.209.101 with 32 bytes of data:
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128

Ping statistics for 24.89.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\WINDOWS\system32>ping 24.89.209.101

Pinging 24.89.209.101 with 32 bytes of data:
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128
Reply from 24.89.209.101: bytes=32 time<1ms TTL=128

Ping statistics for 24.89.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

 

[deadrop]

this was my internet before and after
https://ibb.co/nsUtK5
https://ibb.co/bZQYK5

 

[deadrop]

is this any use
C:\WINDOWS\system32>pathping 192.168.1.1

Tracing route to Linksys00703 [192.168.1.1]
over a maximum of 30 hops:
0 DESKTOP-GTVG6U0.eastlink.ca [192.168.1.126]
1 Linksys00703 [192.168.1.1]

Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-GTVG6U0.eastlink.ca [192.168.1.126]
8/ 100 = 8% |
1 33ms 8/ 100 = 8% 0/ 100 = 0% Linksys00703 [192.168.1.1]