Sorry to hear this
Has our team reverted back with any feedback?You can apply for the refund here http://www.afrihost.com/site/page/60_day_complete_satisfaction_guarantee
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Have you ever flown Business Class or First Class?
Afrihost Business Uncapped Feedback
- Thread starter Lino
- Start date
- Status
Sorry to hear this
Has our team reverted back with any feedback?You can apply for the refund here http://www.afrihost.com/site/page/60_day_complete_satisfaction_guarantee
Bursty-dude
Expert Member
Speedtest results show 4-6Mb constantly, line supposedly syncing at 8Mb (no clue as to why this is so), yet I cannot watch a 360p vid without it buffering like mad. Yet there are Afrihost customers with 2Mb ADSL lines that can stream Youtube vids at 720p or 1080p with no issues at all with buffering.
I have 3 friends who have AH 2Mb ADSL lines, and no issues at all with streaming videos. Here I sit with a 6Mb line, and it sucks gorilla gonads.
Hopefully Hellscum gets off their asses and fix things for a change instead of lying to Afrihost that they have fixed the line issues.
Bursty-dude
Expert Member
Just got another SMS from Telkom saying line is restored.
Bull*****...... http://www.speedtest.net/my-result/3204836539
100% Realtime Speed? No. Double that speed, then it would be true.
Afriman, Afriguy, Afrigirl, Afriwhoever, this has gone on for the last 10 months already. Is it fair for me to be paying over 1K per month for this? I am maybe getting half of what I pay for, if not less.
Everything was perfect in January 2013 with 10Mb speeds, stable connection, no issues at all. I was estatic at finally having decent internet, but one year later, I am seriously considering cancelling everything with AH and moving on.
I know Telkom is giving you guys the finger, but this is not fair at all.
Bull*****...... http://www.speedtest.net/my-result/3204836539
100% Realtime Speed? No. Double that speed, then it would be true.
Afriman, Afriguy, Afrigirl, Afriwhoever, this has gone on for the last 10 months already. Is it fair for me to be paying over 1K per month for this? I am maybe getting half of what I pay for, if not less.
Everything was perfect in January 2013 with 10Mb speeds, stable connection, no issues at all. I was estatic at finally having decent internet, but one year later, I am seriously considering cancelling everything with AH and moving on.
I know Telkom is giving you guys the finger, but this is not fair at all.
F
Fudzy
Guest
Why aren't any of the other ISPs having issues with Telkom?
We've constantly been in contact with you around this - we simply cannot expect stable internet access until we have communicated with you that the Telkom fault has been resolved.
If there is a Telkom issue, all ISPs will be affected.
Are you having troubles with anything?
Bursty-dude
Expert Member
And for all the feedback and help I am extremely grateful.
I suggest you tell Telkom techs to stop lying to you and your customers that faults have been fixed. Every single fault logged so far has been closed without them doing anything about it. Also from feedback that I got, they have also said they have been to our house to check lines and connections, when they have not. They lie, plain and simple.
I just checked the current fault (6BTK221213), and it is miraculously still open.
The fact remains that in the last 10 months, nothing has been done from Telkom's side and I have not had any contact from anyone at Telkom (besides the lying SMS saying faults are fixed) regarding this issue. No phone calls, no visits to the property to physically check things, nothing.
I don't think Telkom or us are intentionally lying to you. Changes happen on the fault either on our end or with Telkom and you're notified. Our two systems are linked, maybe you're getting the incorrect SMS notification? That's something we need to look at.
Our hands become tied in situations like this - we need to wait for Telkom to action something on their side to sort this out. We've done our absolute best on our side.
ranger
Expert Member
If you can speedtest fine, without issues, and get decent results, then it doesn't sound like a Telkom issue.
I would say, let's see the output (copy/paste of the text output is fine, no need for a screenshot):
- a constant ping to youtube, e.g. 'ping -n 100 v1.lscache1.c.youtube.com'
- a traceroute to the same place (e.g. 'tracert v1.lscache1.c.youtube.com')
- or, if you have winmtr (http://winmtr.net), winmtr resutls for v1.lscache1.c.youtube.com
This is what I get from mtr on my linux box at home:
Code:
$ mtr -rwn v1.lscache1.c.youtube.com
HOST: media.ranger Loss% Snt Last Avg Best Wrst StDev
1.|-- 105.224.76.1 0.0% 10 10.8 10.8 10.5 11.1 0.2
2.|-- 105.228.0.6 0.0% 10 14.8 14.8 14.6 15.4 0.2
3.|-- 105.228.0.13 0.0% 10 15.7 15.0 14.7 15.7 0.4
4.|-- 165.165.216.217 0.0% 10 15.0 14.8 14.4 15.2 0.3
5.|-- 196.43.11.218 0.0% 10 36.9 37.1 36.5 38.1 0.5
6.|-- 196.43.26.58 0.0% 10 37.4 37.1 36.5 37.7 0.3
7.|-- 165.165.38.12 0.0% 10 39.4 39.2 38.7 39.8 0.3Youtube does do funky geo-load-balancing, that sometimes does weird things, like serving video from London when it is available in SA, which usually should not have a significant impact on experience. So, what we are looking for is not the lowest latency, but the least jitter (or deviation).
If the deviation is low on the first two or three hops, then usually this indicates the problem is on the ISP side.
If the traceroute or mtr results shows no problems, but you still can't stream youtube, then this could be caused by protocol-based shaping.
Bursty-dude
Expert Member
Thanks ranger.
Pinging v1.lscache1.c.youtube.com [208.117.249.38] with 32 bytes of data:
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=199ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=196ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=199ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=191ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Ping statistics for 208.117.249.38:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 199ms, Average = 193ms
Traceroute:
Tracing route to v1.lscache1.c.youtube.com [208.117.249.38]
over a maximum of 30 hops:
1 2 ms 4 ms 1 ms 192.168.0.1
2 8 ms 9 ms 8 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 11 ms 15 ms 11 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 13 ms 11 ms 11 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 14 ms 13 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 15 ms 14 ms 11 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 182 ms 178 ms 178 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
8 180 ms * 178 ms 195.50.122.181
9 177 ms 178 ms 177 ms vl-3605-ve-229.csw2.London1.Level3.net [4.69.166
.18]
10 * * * Request timed out.
11 179 ms 179 ms 179 ms 195.50.116.210
12 192 ms 192 ms 192 ms 208.117.249.38
Trace complete.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 24 | 24 | 0 | 2 | 7 | 0 |
| 105-236-11-193-esr-lo.mtnbusiness.co.za - 0 | 23 | 23 | 7 | 9 | 15 | 8 |
| ipc-recieve-rb-3a.za.mtnbusiness.net - 0 | 24 | 24 | 10 | 15 | 40 | 11 |
| rb-dca-2.za--rb-cr-1.za-a.mtnns.net - 0 | 23 | 23 | 11 | 13 | 15 | 12 |
| jh-cr-1.za--rb-cr-2.za.mtnns.net - 0 | 24 | 24 | 11 | 15 | 23 | 11 |
| qux-jh-dca-2.za-b.za.mtnbusiness.net - 0 | 24 | 24 | 10 | 13 | 23 | 10 |
| ls-pr-2.uk--ls-cr-1.uk-a.mtn.net - 0 | 24 | 24 | 177 | 182 | 211 | 179 |
| 195.50.122.181 - 0 | 24 | 24 | 178 | 183 | 200 | 181 |
| vl-3607-ve-231.csw2.London1.Level3.net - 0 | 24 | 24 | 178 | 181 | 187 | 178 |
| No response from host - 100 | 5 | 0 | 0 | 0 | 0 | 0 |
| 195.50.116.210 - 0 | 24 | 24 | 178 | 181 | 204 | 180 |
| 208.117.249.6 - 5 | 20 | 19 | 178 | 180 | 195 | 179 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Pinging v1.lscache1.c.youtube.com [208.117.249.38] with 32 bytes of data:
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=199ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=196ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=199ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=194ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=193ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Reply from 208.117.249.38: bytes=32 time=191ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Reply from 208.117.249.38: bytes=32 time=192ms TTL=50
Request timed out.
Reply from 208.117.249.38: bytes=32 time=195ms TTL=50
Ping statistics for 208.117.249.38:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 199ms, Average = 193ms
Traceroute:
Tracing route to v1.lscache1.c.youtube.com [208.117.249.38]
over a maximum of 30 hops:
1 2 ms 4 ms 1 ms 192.168.0.1
2 8 ms 9 ms 8 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 11 ms 15 ms 11 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 13 ms 11 ms 11 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 14 ms 13 ms 12 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 15 ms 14 ms 11 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 182 ms 178 ms 178 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
8 180 ms * 178 ms 195.50.122.181
9 177 ms 178 ms 177 ms vl-3605-ve-229.csw2.London1.Level3.net [4.69.166
.18]
10 * * * Request timed out.
11 179 ms 179 ms 179 ms 195.50.116.210
12 192 ms 192 ms 192 ms 208.117.249.38
Trace complete.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 24 | 24 | 0 | 2 | 7 | 0 |
| 105-236-11-193-esr-lo.mtnbusiness.co.za - 0 | 23 | 23 | 7 | 9 | 15 | 8 |
| ipc-recieve-rb-3a.za.mtnbusiness.net - 0 | 24 | 24 | 10 | 15 | 40 | 11 |
| rb-dca-2.za--rb-cr-1.za-a.mtnns.net - 0 | 23 | 23 | 11 | 13 | 15 | 12 |
| jh-cr-1.za--rb-cr-2.za.mtnns.net - 0 | 24 | 24 | 11 | 15 | 23 | 11 |
| qux-jh-dca-2.za-b.za.mtnbusiness.net - 0 | 24 | 24 | 10 | 13 | 23 | 10 |
| ls-pr-2.uk--ls-cr-1.uk-a.mtn.net - 0 | 24 | 24 | 177 | 182 | 211 | 179 |
| 195.50.122.181 - 0 | 24 | 24 | 178 | 183 | 200 | 181 |
| vl-3607-ve-231.csw2.London1.Level3.net - 0 | 24 | 24 | 178 | 181 | 187 | 178 |
| No response from host - 100 | 5 | 0 | 0 | 0 | 0 | 0 |
| 195.50.116.210 - 0 | 24 | 24 | 178 | 181 | 204 | 180 |
| 208.117.249.6 - 5 | 20 | 19 | 178 | 180 | 195 | 179 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Seems you have some packet loss. Possibly a line fault. Try connecting to the router via Ethernet instead of wifi
Bursty-dude
Expert Member
That is via Ethernet.
Bursty-dude
Expert Member
What I do not understand is this:
6Mb Business Uncapped, right? Like this:
But then why are these other line specs 8Mb and 10Mb:
And then a Speedtest result:
These screenshots were just taken.
In my mind, if it's supposed to be a 6Mb line, then why are there 8Mb and 10Mb results from the Clientzone? I suspect this is where most of my issues are coming from.
Sigh......
6Mb Business Uncapped, right? Like this:
But then why are these other line specs 8Mb and 10Mb:
And then a Speedtest result:
These screenshots were just taken.
In my mind, if it's supposed to be a 6Mb line, then why are there 8Mb and 10Mb results from the Clientzone? I suspect this is where most of my issues are coming from.
Sigh......
Then there is definitely something wrong with your router - which could be the cause of all your issues. Is there no way for you to get another router somehow?
Firstly, Could you please type this into cmd.
Let it run for +-5 minutes and post a summary here.
Secondly - could you post a screenshot of your routers status page please
Thirdly - regarding the line speeds. Telkom dont offer 6MB sync's so you have to pay for a 10meg line. This means that you have more line capacity than your account speed - which is a good thing
F
Fudzy
Guest
I've come back to lunch to very intermittent connectivity. Anyone else have the same issue? Took about 3 refreshes to get this site up.
F
Fudzy
Guest
Just ran the same ping that Zertop suggested:
F
Fudzy
Guest
Okay, seems to be running better now. Is this the type of connection I should get used to? :erm:
GarethY
Well-Known Member
Problem?
Code:
C:\Windows\system32>tracert themorningpint.com
Tracing route to themorningpint.com [66.147.244.155]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 10.1.1.10
2 27 ms 25 ms 37 ms 105-236-7-65-esr-lo.mtnbusiness.co.za [105.236.7.65]
3 36 ms 42 ms 44 ms 41.181.51.182
4 66 ms 36 ms 55 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 74 ms 50 ms 59 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 68 ms 82 ms * 196.44.31.106
7 58 ms 55 ms 41 ms ct-nas-1--ct-ad-1-a.mtnns.net [196.44.18.86]
8 64 ms 66 ms * 196.44.18.89
9 44 ms 48 ms 40 ms 196.44.18.90
10 * * * Request timed out.
11 68 ms 39 ms 69 ms 196.44.18.90
12 39 ms 60 ms 47 ms 196.44.18.89
13 57 ms 58 ms 46 ms 196.44.18.90
14 * 49 ms 45 ms 196.44.18.89
15 84 ms 61 ms 71 ms 196.44.18.90
16 67 ms 61 ms * 196.44.18.89
17 40 ms 56 ms 41 ms 196.44.18.90
18 47 ms 40 ms 48 ms 196.44.18.89
19 53 ms 69 ms 38 ms 196.44.18.90
20 60 ms * * 196.44.18.89
21 38 ms 38 ms 62 ms 196.44.18.90
22 * * * Request timed out.
23 85 ms 50 ms 67 ms 196.44.18.90
24 * * * Request timed out.
25 75 ms 79 ms 53 ms 196.44.18.90
26 * 54 ms 111 ms 196.44.18.89
27 39 ms 40 ms 53 ms 196.44.18.90
28 * 53 ms 39 ms 196.44.18.89
29 43 ms 44 ms 58 ms 196.44.18.90
30 * 66 ms 62 ms 196.44.18.89
Trace complete.
C:\Windows\system32>
Yes, Durban has been acting badly since middle December.
http://www.speedtest.net/my-result/3207303901
10Mb business account. I mean really.
- Status