maybe the problem is on our side aswell.
*** This morning ***
Tracing route to
www.l.google.com [209.85.227.147]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 9 ms 8 ms 8 ms 196-44-65-49.digichilli.co.za [196.44.65.49]
3 37 ms 39 ms 58 ms 196.44.229.138
4 38 ms 38 ms 38 ms 196.44.225.19
5 257 ms 255 ms 256 ms 196.44.239.5
6 265 ms 262 ms 264 ms 195.14.66.13
7 266 ms 262 ms * 195.66.224.125
8 * * 259 ms 64.233.175.25
9 * * 262 ms 72.14.232.134
10 * * * Request timed out.
11 * * * Request timed out.
12 * 262 ms 263 ms wy-in-f147.1e100.net [209.85.227.147]
Trace complete.
*** Now ***
Tracing route to
www.l.google.com [209.85.227.105]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 8 ms 8 ms 8 ms 196-44-65-49.digichilli.co.za [196.44.65.49]
3 43 ms 42 ms 42 ms 196.44.229.138
4 * * * Request timed out.
5 * * 262 ms 196.44.239.5 (BCS IP)
6 * * * Request timed out.
7 271 ms 268 ms * 195.66.224.125
8 * * * Request timed out.
9 * * 277 ms 66.249.95.170
10 * * 277 ms 209.85.251.231
11 303 ms 280 ms 280 ms 209.85.243.97
12 271 ms 271 ms 270 ms wy-in-f105.1e100.net [209.85.227.105]
Trace complete.
Monitoring google also.
WARNING 12-22-2009 12:47:19 0d 0h 1m 59s 2/3 PING WARNING - Packet loss = 37%, RTA = 277.80 ms