copacetic
King of the Hippies
careful... jy weet mos!![]()
I will keep that in mind.
It will be nice to get any sort of improvement on the 14 Kb/s and 700+ ms I was getting this afternoon though.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
careful... jy weet mos!![]()
tracert said:Tracing route to samsung.com [211.45.27.198]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 3792 ms 3347 ms 2793 ms ti-225-8-01.telkomadsl.co.za [105.225.8.1]
3 2475 ms 1730 ms 1666 ms ti-226-0-22.telkomadsl.co.za [105.226.0.22]
4 2068 ms * 1748 ms ti-226-0-57.telkomadsl.co.za [105.226.0.57]
5 * 773 ms 721 ms 165.165.214.213
6 1419 ms 1715 ms 2071 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 2650 ms 3293 ms * xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net [83.2
31.146.245]
8 * 3315 ms 3318 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.5
4]
9 * * 3413 ms as-1.r22.osakjp02.jp.bb.gin.ntt.net [129.250.5.3
5]
10 * 3943 ms * p16-1-0-0.r02.seolko01.kr.bb.gin.ntt.net [129.25
0.2.81]
11 3770 ms * * ae-0.r03.seolko01.kr.bb.gin.ntt.net [129.250.2.1
03]
12 3682 ms * 3501 ms ge-1-1-5.r03.seolko01.kr.ce.gin.ntt.net [61.251.
97.162]
13 3596 ms * 3467 ms user217.s163.samsung.co.kr [203.241.163.217]
14 3360 ms 3369 ms 2856 ms u254.ppp81.samsung.co.kr [157.197.81.254]
15 3531 ms
Everything has gone to cr@p for me, all of the sudden.
![]()
Madness!
Still dead, Ct. http://www.speedtest.net/my-result/i/755280170
All of the sudden, because up until appox. 10 mins ago every thing was fine?Looks like DSLAM congestion. Can't help with that.
Tracing route to samsung.com [211.45.27.198]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 9 ms 15 ms 36 ms ti-225-8-01.telkomadsl.co.za [105.225.8.1]
3 18 ms 13 ms 13 ms ti-226-0-22.telkomadsl.co.za [105.226.0.22]
4 11 ms 12 ms 12 ms ti-226-0-57.telkomadsl.co.za [105.226.0.57]
5 12 ms 20 ms 23 ms 165.165.214.213
6 178 ms 169 ms 168 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
3.9.46]
7 179 ms 197 ms 179 ms xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net [83.2
1.146.245]
8 177 ms 177 ms 177 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.5
]
9 444 ms 428 ms 427 ms as-1.r22.osakjp02.jp.bb.gin.ntt.net [129.250.5.3
]
No offence ranger but whatever you did both this morning and tonight has just made the problem worse.
My account blacked out for a few minutes and now that it is back online (after a reboot) it is taking ages to "resolve with host". Once the page is cached everything seems hunky dory. This is for both local and international traffic now.
I have given Telkom the benefit of the doubt but I will be cancelling monday and moving on. A shame really because I thoroughly enjoyed the TI experience until 6th January of this year.
In the first case, we had assurances that everything had been done, but then when we found a problem and provided proof that there was a problem, we found that half of the required changes had not been communicated.
And this is why we normally make changes of this nature between 00h00 and 06h00, but we had the choice of risking impacting experience in order to improve it, or leaving it so everyone still has a crappy internet for all of Saturday evening.
There is a slight design issue, which bit us. We worked around it, and will address the actual problem next week (it is too big a change to put in without testing, so we will QA it during the week.
Maybe you should at least give us until Monday morning. Sunday night is actually our total peak traffic, if the experience tomorrow night is adequate, it probably won't get worse.
Unfortunately I can't give too many details on exactly why it took so long to resolve, but unfortunately there have been a lot of organisational and legal issues that have complicated fixing the root cause. In the interim we did as much as we could to mitigate the problem, but ran into some technical challenges, which we are still trying to address.
/interest piqued!... and legal issues that have complicated fixing the root cause.
/interest piqued!
Wholesale/Retail (internal) or external parties?
I would want to see a traceroute.
All of the sudden, because up until appox. 10 mins ago every thing was fine?
Now again everything is good again, someone was messing with the Telkom Network.
![]()
Not exchange congestion.