Anybody would like to comment on tracert.
C:\Windows\system32>tracert -d axxess.co.za
Tracing route to axxess.co.za [197.242.150.113]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 12 ms 12 ms 13 ms 41.181.178.18
4 11 ms 48 ms 11 ms 41.181.178.17
5 11 ms 11 ms 11 ms 41.181.165.115
6 11 ms 10 ms 10 ms 196.31.180.4
7 12 ms 13 ms 13 ms 196.44.0.224
8 12 ms 11 ms 12 ms 196.44.31.99
9 11 ms 12 ms 12 ms 196.31.220.6
10 13 ms 13 ms 12 ms 196.31.220.23
11 12 ms 11 ms 12 ms 196.31.63.206
12 13 ms 12 ms 12 ms 196.30.42.133
13 12 ms 12 ms 12 ms 197.242.150.113
Trace complete.
This happened now when the exchange was upgraded.
Second hop times out.
If I do a local or internation tracert this happens. Just curious why this happens. Before the upgrade it was right. Even Zertop utility does this to.
It does not effect download speed. This happen with two different modem. D-Link and TP-Link.