Pretty much, I have chatted to telkom and they tell me that my exchange definitely isn't congested etc :/ http://i.imgur.com/ybAldGL.png
Don't know where to go from here.
Don't know where to go from here.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Pretty much, I have chatted to telkom and they tell me that my exchange definitely isn't congested etc :/ http://i.imgur.com/ybAldGL.png
Don't know where to go from here.
I check the last time I had a constant connection and speed was in July 2014. What changed in August AH? Since then everything on your network went to shyte?
Things have been mostly fine here in PE, so it's not a nationwide thing. Why are you still with AH if things have been terrible for so long? Just find another ISP and switch back if you see things are back to normal. This isn't Mweb where it takes two months to leave.
Going to start looking for a new ISP now. Eskom dipped us into darkness so could not do a lot of reading...
Oh and only realized this morning when I looked at the stats for the past year on my internet use, that the amount of data fell from about 200GB per month to about 100GB per month.
Going to start looking for a new ISP now. Eskom dipped us into darkness so could not do a lot of reading...
Oh and only realized this morning when I looked at the stats for the past year on my internet use, that the amount of data fell from about 200GB per month to about 100GB per month.
Then have a look at a Web Africa capped account. They have a 120GB option with uncapped usage from midnight until 6am every day.
So afrigenie, what is being done about streaming? Youtube is being routed to international instead of local, Humercellc was kind enough to do the work for you guys and provide tracerts......Speeds are erratic, very up and down, never consistent....
We are making definite progress with it, it has been an elusive issue, and not all of our clients experience it. We should have everyone routing through the local Google caches again shortly.
Morning Guys!
My apologies for the connectivity issues that many of our Cape users experienced over the weekend, the issues was caused by the system that handles the caching for internet traffic, it basically conked out and caused significant issues with internet traffic. HTTPS traffic was not handled by the affected system, which is why you would have seen some traffic working.
If you guys have any questions please let me know here or via PM.
Thanks!
They normally dont cache https traffic so it could be their caching proxy which normally runs on servers so there is most likely a power outage in a DC because of gen failure or something
Well that is my guess probably very wrong![]()
I see i guessed sorta right for once..it was quite logical though![]()
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.13.129 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Ping statistics for 105.236.13.129:
Packets: Sent = 30, Received = 19, Lost = 11 (36% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms
2014/12/08 21:11:45.10
Local Tracert
Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 7 ms 8 ms 41.181.51.182
4 8 ms 7 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 8 ms 8 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 9 ms 8 ms 8 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 8 ms 8 ms 8 ms 196.44.0.74
8 9 ms 9 ms 9 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 12 ms 11 ms 11 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 9 ms 10 ms 9 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
11 13 ms 9 ms 9 ms 196.28.178.66
12 10 ms 9 ms 9 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 10 ms 10 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 11 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 10 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]
Trace complete.
International Tracert
Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 7 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 8 ms 8 ms 66.8.11.186
5 9 ms 9 ms 9 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 173 ms 174 ms 171 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
7 171 ms 170 ms 173 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
8 152 ms 152 ms 152 ms linx-gw1.thn.ncuk.net [195.66.224.240]
9 152 ms 151 ms 152 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
10 175 ms 174 ms 172 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
11 174 ms 169 ms 165 ms www.thinkbroadband.com [80.249.99.130]
Trace complete.
International Speedtest
Downloaded 20.0 megabytes in 28 seconds. (718.50 KB/s)
Local Speedtest
Downloaded 15.6 megabytes in 16 seconds. (960.90 KB/s)

10M CPT
yet youtube is buffering every couple of seconds :/
https://www.youtube.com/watch?v=I46l-aoP2O8
What is going on Afri*
Still got major problems browsing and packet loss... getting worse as the evening progresses.
Ticket is STILL open with support, and there has been no action on this since 04 December. At the same time, AH handed my call to Telkom (not sure why), but they have already been out and confirmed that the line is fine... the Telkom tech was even kind enough to switch me between 2 other copper pairs to confirm.
@AfriPEOPLE
any ideas?
#ZUT-865-94656
Zertop's "Is it my Line" Results
Basic Report:
Your packet loss was 36 percent.
Your average ping was 7ms.
Your maximum ping was 8ms.
You have serious packet loss. Please post these results to the forum for advice.
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.13.129 with 32 bytes of data: Request timed out. Request timed out. Reply from 105.236.13.129: bytes=32 time=7ms TTL=254 Request timed out. Request timed out. Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Request timed out. Request timed out. Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=7ms TTL=254 Reply from 105.236.13.129: bytes=32 time=7ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Request timed out. Request timed out. Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Request timed out. Request timed out. Request timed out. Reply from 105.236.13.129: bytes=32 time=7ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=7ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Reply from 105.236.13.129: bytes=32 time=7ms TTL=254 Reply from 105.236.13.129: bytes=32 time=8ms TTL=254 Ping statistics for 105.236.13.129: Packets: Sent = 30, Received = 19, Lost = 11 (36% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 8ms, Average = 7ms 2014/12/08 21:11:45.10 Local Tracert Tracing route to news24.co.za [41.86.110.143] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254] 2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 3 8 ms 7 ms 8 ms 41.181.51.182 4 8 ms 7 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 5 8 ms 8 ms 8 ms compj-cpt-1.mtnns.net [196.44.18.2] 6 9 ms 8 ms 8 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134] 7 8 ms 8 ms 8 ms 196.44.0.74 8 9 ms 9 ms 9 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141] 9 12 ms 11 ms 11 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1] 10 9 ms 10 ms 9 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238] 11 13 ms 9 ms 9 ms 196.28.178.66 12 10 ms 9 ms 9 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 13 10 ms 10 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 14 11 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146] 15 10 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143] Trace complete. International Tracert Tracing route to thinkbroadband.com [80.249.99.130] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254] 2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 3 8 ms 8 ms 7 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 4 8 ms 8 ms 8 ms 66.8.11.186 5 9 ms 9 ms 9 ms compj-cpt-1.mtnns.net [196.44.18.2] 6 173 ms 174 ms 171 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113] 7 171 ms 170 ms 173 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201] 8 152 ms 152 ms 152 ms linx-gw1.thn.ncuk.net [195.66.224.240] 9 152 ms 151 ms 152 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17] 10 175 ms 174 ms 172 ms te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 11 174 ms 169 ms 165 ms www.thinkbroadband.com [80.249.99.130] Trace complete. International Speedtest Downloaded 20.0 megabytes in 28 seconds. (718.50 KB/s) Local Speedtest Downloaded 15.6 megabytes in 16 seconds. (960.90 KB/s)
As things stand at the moment, a few users have reported exactly what you are experiencing, in some cases users are being routed to the European Servers for Google services instead of the local cache as it should be. Our Team is working to get the routing correctly running through to the local caches, you should see significant improvements soon.
I'm having the same issue. Can't stream SD videos on 10Mb.
Your explanation makes no sense though. Even if it is routing to servers in Europe, I should still be able to stream in HD. I can stream HD Netflix from America just fine.