0
I've been having some inconsistency in my network connection, so I set up a script to constantly ping 1.1.1.1 and if it gets a timeout, it then runs a tracert and logs the results.
This is what I found today my home setup is wifi on pc -> router -> cable modem, so I'm assuming the first two bounces are to router then to modem, but idk how that all works...:
Trace complete.
Wed 08:34:26 PM
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 112 ms 101 ms 211 ms
2 * 66 ms 342 ms
3 15 ms 22 ms 16 ms
4 31 ms 28 ms 48 ms
5 52 ms 9 ms 21 ms
6 * 24 ms 187 ms
7 27 ms 20 ms 38 ms
8 36 ms 19 ms 57 ms
9 110 ms 216 ms *
10 114 ms 108 ms * one.one.one.one [1.1.1.1]
11 264 ms * 146 ms one.one.one.one [1.1.1.1]
Trace complete.
Wed 08:34:52 PM
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 85 ms 121 ms 120 ms
2 308 ms * 448 ms
3 * 157 ms 79 ms
4 64 ms 71 ms 106 ms
5 80 ms 128 ms 184 ms
6 60 ms 98 ms 51 ms
7 77 ms * 123 ms
8 140 ms 116 ms 89 ms
9 109 ms * 207 m
10 * 434 ms * one.one.one.one [1.1.1.1]
11 109 ms 57 ms 123 ms one.one.one.one [1.1.1.1]
Trace complete.
Wed 08:37:29 PM
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
1 18 ms 283 ms *
2 397 ms * 21 ms
3 * 122 ms 205 ms
4 227 ms * 36 ms
5 23 ms 61 ms 115 ms
6 182 ms 158 ms 67 ms
7 * 68 ms 237 ms
8 37 ms 41 ms 66 ms
9 * * * Request timed out.
10 * 363 ms * one.one.one.one [1.1.1.1]
11 431 ms * 164 ms one.one.one.one [1.1.1.1]
Can I glean from this that my router might be kaput?
This problem has been fine for a few weeks, but just happened again tonight and ten minutes later seems fine again (2 ms ping to the router).
If you are suspecting some trouble on the first hops, use
-h
to restrict the number of hops (a*
failure can happen on any of the intermediate hops). Also use-d
to avoid DNS lookup. If your ping increases hundredfold even on the first hops, it's indeed possible that something is wrong in your home network. – dirkt – 2019-04-18T06:42:45.933