- Joined
- May 24, 2012
- Messages
- 17,239
Caught it again:
Tracing route to google.com [74.125.24.102]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 6 ms 7 ms * 105-236-2-65-esr-lo.mtnbusiness.co.za
.65]
3 8 ms 8 ms * ipc-recieve-jh-2a.za.mtnbusiness.net
.17]
4 8 ms 9 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net
.115]
5 * 8 ms 8 ms jh-dca-2.za--qux-q.za.mtnbusiness.net
0.4]
6 * * * Request timed out.
7 205 ms * 205 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 206 ms 204 ms 202 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 207 ms 206 ms 206 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 * * * Request timed out.
11 197 ms * 210 ms proxy.google.com [216.239.51.5]
12 219 ms 228 ms 216 ms 209.85.250.216
13 197 ms 196 ms 197 ms 72.14.235.189
14 * * * Request timed out.
15 * 215 ms 218 ms de-in-f102.1e100.net [74.125.24.102]
Did that, then line lost sync, when it reconnected no internet light, router restart cured it as usual. What is this?
Like this now:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Scott Kirby>tracert google.com
Tracing route to google.com [74.125.24.138]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 7 ms 7 ms 6 ms 105-236-2-65-esr-lo.mtnbusiness.co.za
.65]
3 8 ms 8 ms 7 ms ipc-recieve-jh-4a.za.mtnbusiness.net
.41]
4 8 ms 8 ms 7 ms qux-jh-dca-2.za-b.za.mtnbusiness.net
.115]
5 8 ms 10 ms 7 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 188 ms 188 ms 189 ms 41.181.180.10
7 248 ms 205 ms 205 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
8 197 ms 194 ms 199 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 206 ms 205 ms 206 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 * 192 ms 188 ms 209.85.255.76
11 204 ms 193 ms 215 ms proxy.google.com [216.239.51.5]
12 205 ms 204 ms 208 ms 209.85.250.216
13 222 ms 197 ms 197 ms 72.14.235.189
14 * * * Request timed out.
15 197 ms 197 ms 197 ms de-in-f138.1e100.net [74.125.24.138]
Trace complete.
If the router restart fixes it, it could be a line issue. It could be a DNS issue, if swapping out DNS fixes it (as someone suggests) but I would expect a lot more clients to experience this if there was a failing component in our DNS cluster.
I would definitely look at the line and router first. Have you run any troubleshooting with them team yet? Maybe drop me a PM so we can test
