Tracing route to cnn-lax-tmp.gslb.vgtf.net [157.166.241.11]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.16.64
2 3 ms 3 ms 2 ms 10.1.1.1
3 10 ms 9 ms 21 ms 105.236.4.193
4 31 ms 29 ms 30 ms 41.181.178.77
5 47 ms 44 ms 53 ms 196.44.31.120
6 35 ms 33 ms 33 ms 196.44.0.42
7 34 ms 33 ms 37 ms 41.181.165.115
8 256 ms 251 ms 257 ms 212.72.41.89
9 419 ms * 451 ms 4.69.162.145
10 * * 404 ms 4.69.153.213
11 414 ms 420 ms 407 ms 4.69.143.70
12 403 ms 410 ms 414 ms 4.69.137.74
13 * 480 ms 413 ms 4.69.134.78
14 481 ms 471 ms * 4.69.148.45
15 467 ms 452 ms 402 ms 4.69.135.185
16 454 ms * 416 ms 4.69.132.10
17 * 446 ms 430 ms 4.69.137.34
18 405 ms * * 4.69.144.10
19 * * * Request timed out.
20 * * * Request timed out.
On Internet Solutions 1MB:
traceroute www.cnn.com
traceroute to www.cnn.com (157.166.248.11), 30 hops max, 60 byte packets
1 196.214.57.65 (196.214.57.65) 2.886 ms 2.789 ms 2.707 ms
2 196.212.94.201 (196.212.94.201) 525.795 ms 527.430 ms 530.306 ms
3 196.26.78.33 (196.26.78.33) 532.947 ms 535.778 ms 537.960 ms
4 core1b-ctn-gi0-2.ip.isnet.net (168.209.6.4) 540.102 ms 544.674 ms 545.481 ms
5 168.209.201.6 (168.209.201.6) 702.453 ms 703.349 ms 704.152 ms
6 168.209.246.66 (168.209.246.66) 707.626 ms 244.227 ms 244.617 ms
7 195.50.124.33 (195.50.124.33) 246.008 ms 263.957 ms 266.041 ms
8 vl-3601-ve-225.csw2.London1.Level3.net (4.69.166.145) 352.517 ms vl-3603-ve-227.csw2.London1.Level3.net (4.69.166.153) 354.894 ms vl-3604-ve-228.csw2.London1.Level3.net (4.69.166.157) 357.511 ms
9 ae-57-222.ebr2.London1.Level3.net (4.69.153.133) 360.398 ms ae-59-224.ebr2.London1.Level3.net (4.69.153.141) 362.297 ms ae-57-222.ebr2.London1.Level3.net (4.69.153.133) 365.654 ms
10 ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 368.782 ms ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 248.911 ms ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 252.594 ms
11 ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 253.090 ms 281.872 ms 267.341 ms
12 ae-1-100.ebr1.Washington12.Level3.net (4.69.143.213) 274.447 ms 281.463 ms 251.378 ms
13 ae-6-6.ebr1.Atlanta2.Level3.net (4.69.148.105) 257.311 ms 256.082 ms 256.647 ms
14 ae-1-51.edge2.Atlanta4.Level3.net (4.69.150.17) 257.777 ms 260.695 ms 262.805 ms
Every time I switch to an Afrihost account (end of the month), I realise just how good the performance from Telkom Internet really is. There's ALWAYS some issue with Afrihost with regards to speed or latency or both.
We've got a problem on international speeds, which is also impacting general latency on the network. We've got all our people dedicated to sorting this out. We'll post more info as it comes in, but sounds like service is in the process of being restored.
Type: MTN IP NETWORK
Date: 28 Jan 2013 12:56:42 AM
Cause of Problem: Circuit Down
Point of Impact: London, Telecity
Randburg
Symptoms Experienced: Slight Degradation in Service
Severity: Major
Status: Attending
Attending: Carrier Operators
Ticket Number:
Additional Information: Please note that we have lost 4 x EASSY STM4 circuits from Randburg to London Telecity.This has been reported to relevant Telco Provider’s for investigation. Traffic has been routed via other alternative paths.
Please accept our sincere apology for the inconvenience this may cause to your business.
Tried playing Guild wars 2 but the pings are just so unreliable. one moment is in the 300 then next its 900 and it jumps all over the place as if I was on a bad wireless connection.
Also have had telkom tech out 5 times in the last 4 weeks and they tell me everything looks fine.