WAJeff
Web Africa Representative
Ok, tried again .. using other addresses.
C:\>tracert webafrica.co.za
Tracing route to webafrica.co.za [196.220.58.66]
over a maximum of 30 hops:
1 4 ms 3 ms 3 ms home.gateway.pace.net [10.0.0.2]
2 23 ms 26 ms 22 ms 196-210-138-1.dynamic.isadsl.co.za [196.210.138.
1]
3 22 ms 22 ms 29 ms 196.38.73.85
4 382 ms 377 ms 378 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 338 ms 335 ms 339 ms cdsl1-rba-vl2.ip.isnet.net [196.26.77.1]
6 334 ms 342 ms 371 ms cdsl1-ctn-cdsl1-rba.ip.isnet.net [196.38.72.159]
7 261 ms 250 ms 254 ms wa-is.isdsl.net [196.38.72.84]
8 42 ms 43 ms 44 ms wnls-cr2-vl-140.wa.co.za [41.185.1.1]
9 103 ms 82 ms 71 ms wnls-hr1-gi-9-13.wa.co.za [41.185.1.26]
10 44 ms 47 ms 49 ms 196.220.58.66
Trace complete.
C:\>tracert twitter.com
Tracing route to twitter.com [199.59.148.10]
over a maximum of 30 hops:
1 2 ms 3 ms 3 ms home.gateway.pace.net [10.0.0.2]
2 20 ms 22 ms 21 ms 196-210-138-1.dynamic.isadsl.co.za [196.210.138.
1]
3 22 ms 22 ms 22 ms 196.38.73.85
4 22 ms 25 ms 30 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 38 ms 28 ms 26 ms core1-pkl-tg0-7-0-0.ip.isnet.net [168.209.1.162]
6 250 ms 248 ms 217 ms 168.209.201.89
7 211 ms 205 ms 212 ms 168.209.246.3
8 204 ms 205 ms 204 ms 195.50.124.33
9 336 ms 256 ms 328 ms vl-3503-ve-117.csw1.London1.Level3.net [4.69.166
.137]
10 205 ms 207 ms 218 ms ae-1-51.edge4.London1.Level3.net [4.69.139.74]
11 204 ms 206 ms 202 ms TWITTER-INC.edge4.London1.Level3.net [212.113.14
.238]
12 284 ms 315 ms 279 ms xe-1-2-1.iad-cr2.twttr.com [199.16.159.125]
13 353 ms 353 ms 352 ms ae60.pao1-cr2.twttr.com [199.16.159.87]
14 353 ms 348 ms 349 ms ae52.smf1-er2.twttr.com [199.16.159.55]
15 357 ms 358 ms 358 ms r-199-59-148-10.twttr.com [199.59.148.10]
Trace complete.
My kids are not here, and no other computers are running ..
I dont have the energy to go thru Telkom/Web Africa ping-pong .. I have been there/done that.
Plse tell me, realistically, is there any hope, or do I just bite the bullet, and cancel ?
While I understand this is annoying, there's no need to cancel.
We've already established that there's an issue around some Western Cape locations.http://forums.webafrica.co.za/showt...dback-and-Issues?p=80296&viewfull=1#post80296
WAJeff said:Just want to confirm things here quickly, under one post
We're currently investigating a 15ms - 20ms latency increase within the Western Cape area. Unfortunately we aren't able to make an exact pin-point location at the moment, however latency is seen as being increased slightly by anywhere between 15ms to 20ms. This will be from hop 2.
Anything increased from the response times mentioned above may indicate an issue with your exchange or there is activity on the line whilst running a tracert.
Will have feedback posted up here as soon as we get further updates.
We should have further feedback or hopefully a resolution by tomorrow.
All in all though, I personally think this network move has gone very smoothly considering this is the only "major" problem we've experienced here. I promise you, this is something that we're busy sorting out.
Last edited: