Pinging
www.google.co.za [172.217.20.99] with 32 bytes of data:
Reply from 172.217.20.99: bytes=32 time=208ms TTL=50
Reply from 172.217.20.99: bytes=32 time=209ms TTL=50
Reply from 172.217.20.99: bytes=32 time=220ms TTL=50
Reply from 172.217.20.99: bytes=32 time=208ms TTL=50
Reply from 172.217.20.99: bytes=32 time=208ms TTL=50
Reply from 172.217.20.99: bytes=32 time=209ms TTL=50
Reply from 172.217.20.99: bytes=32 time=207ms TTL=50
Ping statistics for 172.217.20.99:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 207ms, Maximum = 220ms, Average = 209ms
Control-C
^C
C:\>tracert
www.google.co.za
Tracing route to
www.google.co.za [172.217.20.99]
over a maximum of 30 hops:
1 2 ms 2 ms 1 ms TP-LINK.Home [192.168.20.1]
2 * * * Request timed out.
3 12 ms 11 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 12 ms 11 ms 11 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 12 ms 12 ms 11 ms 41.164.52.40
6 33 ms 33 ms 33 ms 172.18.1.162
7 35 ms 34 ms 32 ms 72.14.194.206
8 193 ms 194 ms 253 ms 216.239.54.57
9 201 ms 201 ms 203 ms 209.85.253.10
10 209 ms 212 ms 214 ms 216.239.58.10
11 208 ms 208 ms 208 ms 216.239.57.142
12 212 ms 211 ms 212 ms 66.249.94.69
13 207 ms 208 ms 208 ms fra02s28-in-f3.1e100.net [172.217.20.99]
Trace complete.
I've tried this from various adsl lines (business uncapped) that we have in different areas of CPT and all are the same.
My private home line (which is a capped account) is doing the same.