C:\Users\Joe's Game PC>ping -t google.com
C:\Users\Joe's Game PC>tracert google.com
Tracing route to google.com [216.58.195.78]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.8.1
2 41 ms 14 ms 16 ms 10.81.8.1
3 18 ms 20 ms 9 ms 100.120.109.84
4 19 ms 9 ms 12 ms ^C
C:\Users\Joe's Game PC>ping -t 10.81.8.1
Pinging 10.81.8.1 with 32 bytes of data:
Reply from 10.81.8.1: bytes=32 time=6ms TTL=254
Reply from 10.81.8.1: bytes=32 time=38ms TTL=254
Reply from 10.81.8.1: bytes=32 time=9ms TTL=254
Reply from 10.81.8.1: bytes=32 time=30ms TTL=254
Reply from 10.81.8.1: bytes=32 time=10ms TTL=254
Reply from 10.81.8.1: bytes=32 time=10ms TTL=254
Reply from 10.81.8.1: bytes=32 time=77ms TTL=254
Reply from 10.81.8.1: bytes=32 time=108ms TTL=254
Reply from 10.81.8.1: bytes=32 time=17ms TTL=254
Reply from 10.81.8.1: bytes=32 time=36ms TTL=254
Reply from 10.81.8.1: bytes=32 time=76ms TTL=254
Reply from 10.81.8.1: bytes=32 time=92ms TTL=254
Reply from 10.81.8.1: bytes=32 time=12ms TTL=254
Reply from 10.81.8.1: bytes=32 time=24ms TTL=254
Reply from 10.81.8.1: bytes=32 time=131ms TTL=254
Reply from 10.81.8.1: bytes=32 time=77ms TTL=254
Reply from 10.81.8.1: bytes=32 time=33ms TTL=254
Reply from 10.81.8.1: bytes=32 time=108ms TTL=254
Reply from 10.81.8.1: bytes=32 time=278ms TTL=254
Reply from 10.81.8.1: bytes=32 time=11ms TTL=254
Reply from 10.81.8.1: bytes=32 time=25ms TTL=254
Reply from 10.81.8.1: bytes=32 time=13ms TTL=254
Reply from 10.81.8.1: bytes=32 time=123ms TTL=254
Reply from 10.81.8.1: bytes=32 time=52ms TTL=254
Reply from 10.81.8.1: bytes=32 time=68ms TTL=254
Reply from 10.81.8.1: bytes=32 time=49ms TTL=254
Reply from 10.81.8.1: bytes=32 time=34ms TTL=254
Reply from 10.81.8.1: bytes=32 time=66ms TTL=254
Reply from 10.81.8.1: bytes=32 time=160ms TTL=254
Ping statistics for 10.81.8.1:
Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 278ms, Average = 61ms
Control-C
^C
Issues such as this have been going on for a while even before quarantine started. I live in an apartment complex where they have a deal with you guys to be the only internet choice for the people here. I suspect this is part of the issue. If I wanted to switch service I would have to move out.
I know there is a pinned post about latency and packet loss but it really doesnt cover the issue and doesnt offer solutions.
Another thing is this varies from time to time. Sometimes my connection is perfect but most times it is not.
JonathanJ
Former Moderator
•
Try bypassing the router (192) and hardwired directly to the modem and run the traceroute.
Jonathan J
Cox Moderator
2
0
joe564338
New Contributor
•
Microsoft Windows [Version 10.0.18363.1198]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Users\Joe's Game PC>tracert
Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name
Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.
C:\Users\Joe's Game PC>tracert google.com
Tracing route to google.com [172.217.6.78]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.8.1
2 68 ms 49 ms 127 ms 10.81.8.1
^C
C:\Users\Joe's Game PC>ping -t 10.81.8.1
Pinging 10.81.8.1 with 32 bytes of data:
Reply from 10.81.8.1: bytes=32 time=195ms TTL=254
Request timed out.
Reply from 10.81.8.1: bytes=32 time=116ms TTL=254
Reply from 10.81.8.1: bytes=32 time=83ms TTL=254
Reply from 10.81.8.1: bytes=32 time=504ms TTL=254
Request timed out.
Reply from 10.81.8.1: bytes=32 time=185ms TTL=254
Reply from 10.81.8.1: bytes=32 time=191ms TTL=254
Reply from 10.81.8.1: bytes=32 time=393ms TTL=254
Reply from 10.81.8.1: bytes=32 time=65ms TTL=254
Reply from 10.81.8.1: bytes=32 time=175ms TTL=254
Reply from 10.81.8.1: bytes=32 time=346ms TTL=254
Request timed out.
Reply from 10.81.8.1: bytes=32 time=370ms TTL=254
Reply from 10.81.8.1: bytes=32 time=59ms TTL=254
Reply from 10.81.8.1: bytes=32 time=285ms TTL=254
Reply from 10.81.8.1: bytes=32 time=100ms TTL=254
Reply from 10.81.8.1: bytes=32 time=103ms TTL=254
Reply from 10.81.8.1: bytes=32 time=13ms TTL=254
Reply from 10.81.8.1: bytes=32 time=168ms TTL=254
Reply from 10.81.8.1: bytes=32 time=218ms TTL=254
Reply from 10.81.8.1: bytes=32 time=183ms TTL=254
Reply from 10.81.8.1: bytes=32 time=24ms TTL=254
Reply from 10.81.8.1: bytes=32 time=173ms TTL=254
Reply from 10.81.8.1: bytes=32 time=239ms TTL=254
Reply from 10.81.8.1: bytes=32 time=53ms TTL=254
Request timed out.
Reply from 10.81.8.1: bytes=32 time=46ms TTL=254
Reply from 10.81.8.1: bytes=32 time=42ms TTL=254
Reply from 10.81.8.1: bytes=32 time=59ms TTL=254
Reply from 10.81.8.1: bytes=32 time=34ms TTL=254
Reply from 10.81.8.1: bytes=32 time=121ms TTL=254
Reply from 10.81.8.1: bytes=32 time=235ms TTL=254
Reply from 10.81.8.1: bytes=32 time=28ms TTL=254
Reply from 10.81.8.1: bytes=32 time=33ms TTL=254
Reply from 10.81.8.1: bytes=32 time=76ms TTL=254
Reply from 10.81.8.1: bytes=32 time=43ms TTL=254
Reply from 10.81.8.1: bytes=32 time=24ms TTL=254
Reply from 10.81.8.1: bytes=32 time=248ms TTL=254
Reply from 10.81.8.1: bytes=32 time=45ms TTL=254
Reply from 10.81.8.1: bytes=32 time=140ms TTL=254
Reply from 10.81.8.1: bytes=32 time=37ms TTL=254
Reply from 10.81.8.1: bytes=32 time=77ms TTL=254
Reply from 10.81.8.1: bytes=32 time=65ms TTL=254
Reply from 10.81.8.1: bytes=32 time=191ms TTL=254
Reply from 10.81.8.1: bytes=32 time=46ms TTL=254
Reply from 10.81.8.1: bytes=32 time=52ms TTL=254
Reply from 10.81.8.1: bytes=32 time=20ms TTL=254
Reply from 10.81.8.1: bytes=32 time=108ms TTL=254
Ping statistics for 10.81.8.1:
Packets: Sent = 49, Received = 45, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 504ms, Average = 133ms
Control-C
^C
C:\Users\Joe's Game PC>
Got this today just now
2
0