Anyone else having issues browsing?
What issues are you seeing?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Anyone else having issues browsing?
Sometimes it's slow.. But I'm not sure if problem on my side.. Did notice tho that it happens mostly in peak hrs
What issues are you seeing?
Shortly before 12 last night it just went belly up. On AH and Axxess, seems to happen pretty frequently. I couldn'y open any sites, local or otherwise, streaming was terrible, when speedtest did however load, the download speed was maxing out at 8mb. but browsing was very very poor. Tracert showed nothing out of the ordinary either
Your international latency is excellent, but local could definitely be better. It depends on the server you're pinging I guess.
We definitely want to ensure our clients get a good experience. I totally agree that prices and value are meaningless if your core experience is unsatisfying. We've been shaping very little over the past few weeks, so I don't think this is related to shaping at all, and we'll need to troubleshoot with you to see what your throughput is so poor.
Please drop me a PM so we can get started on this.
Will do so.
Perhaps you can find a root cause behind this.
/shortened
** server can't find thisshouldfail.com: NXDOMAIN
Will do so.
Perhaps you can find a root cause behind this.
CAPE TOWN:
Last Result:
Download Speed: 114 kbps (14.3 KB/sec transfer rate)
Upload Speed: 396 kbps (49.5 KB/sec transfer rate)
Latency: 44 ms
2/9/2015, 6:44:16 PM
INTERNATIONAL:
Last Result:
Download Speed: 262 kbps (32.8 KB/sec transfer rate)
Upload Speed: 372 kbps (46.5 KB/sec transfer rate)
Latency: 178 ms
2/9/2015, 6:49:53 PM
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=32 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=38 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=36 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=42 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=43 ms
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=50 time=172 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=50 time=179 ms
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=50 time=170 ms
Trace Test:
traceroute -n 197.242.144.102
1 192.168.0.1 1 ms 1 ms
2 105.236.5.1 6 ms 12 ms
3 41.181.201.9 8 ms
196.44.18.8 8 ms
4 41.181.198.1 8 ms
196.44.31.6 32 ms
5 196.44.18.8 9 ms
196.44.31.2 33 ms
6 196.44.31.6 38 ms
196.44.31.9 32 ms
7 196.44.31.9 33 ms
196.31.220.2 38 ms
8 196.31.220.2 36 ms
196.31.63.2 32 ms
9 196.31.63.2 32 ms
Request timed out *
10 196.30.42.1 33 ms
197.242.144.1 33 ms
11 197.242.144.1 33 ms
traceroute -n 8.8.8.8
1 192.168.0.1 1 ms 1 ms
2 41.181.53.2 8 ms
105.236.5.1 9 ms
3 66.8.11.1 9 ms
41.181.53.2 8 ms
4 196.44.18.2 10 ms
66.8.11.1 15 ms
5 72.14.238.1 157 ms
196.44.18.2 10 ms
6 72.14.238.1 156 ms
DNS Test:
nslookup www.afrihost.com
Name: www.afrihost.com
Address: 197.242.144.102
nslookup www.google.com
Name: www.google.com
Address: 66.8.14.24
Name: www.google.com
Address: 66.8.14.27
Name: www.google.com
Address: 66.8.14.35
Name: www.google.com
Address: 66.8.14.31
Name: www.google.com
Address: 66.8.14.46
Name: www.google.com
Address: 66.8.14.16
Name: www.google.com
Address: 66.8.14.42
Name: www.google.com
Address: 66.8.14.59
Name: www.google.com
Address: 66.8.14.20
Name: www.google.com
Address: 66.8.14.53
Name: www.google.com
Address: 66.8.14.49
Name: www.google.com
Address: 66.8.14.38
Name: www.google.com
Address: 66.8.14.57
Name: www.google.com
Address: 66.8.14.37
Name: www.google.com
Address: 66.8.14.48
Name: www.google.com
Address: 66.8.14.26
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAIN
We are heading back to the level we were last year, not quite as bad yet but heading that way.
From 8 PM to 11pm, for a week now, streaming is virtually impossible in Cape Town.
Are we starting to reach IPC capacity again already or is it just that the MTN network is not up to the Job?
All of the issues with Afrihost reliability and throughput seam to Post date the merger announcement and a few of them actually stem from the switchover from IS.
An no Rolling Blackout or Congested Exchange excuses, I loaded up the Web Africa 1GB account and streamed with no issues.
We are heading back to the level we were last year, not quite as bad yet but heading that way.
From 8 PM to 11pm, for a week now, streaming is virtually impossible in Cape Town.
Are we starting to reach IPC capacity again already or is it just that the MTN network is not up to the Job?
All of the issues with Afrihost reliability and throughput seam to Post date the merger announcement and a few of them actually stem from the switchover from IS.
An no Rolling Blackout or Congested Exchange excuses, I loaded up the Web Africa 1GB account and streamed with no issues.
What sort of speeds are you getting on speedtest.net? Are you seeing any spikes in latency along with the drops in performance?
Speed tests on the MyBroadband speed test are normal and I am not noticing latency but that is hard to judge in a stream.
What I can say for sure is that HTTP downloads are running at less than a Quarter of what they were this afternoon, same server, same files (or actually PDF documents I use for work).
should speedtest.net show a different result to a localy hosted one?
If I try and access several PDF's simultaneously the line maxes out at ~300KBs vs the ~600KBS during the day
Same for me streaming at night is almost impossible
Same for me streaming at night is almost impossible
Speed tests on the MyBroadband speed test are normal and I am not noticing latency but that is hard to judge in a stream.
What I can say for sure is that HTTP downloads are running at less than a Quarter of what they were this afternoon, same server, same files (or actually PDF documents I use for work).
should speedtest.net show a different result to a localy hosted one?
If I try and access several PDF's simultaneously the line maxes out at ~300KBs vs the ~600KBS during the day
Same for me streaming at night is almost impossible
And at the risk of becoming monotonous, same here. For the last two weeks, every evening, streaming deteriorates at around 7-8pm and from 9-11 it is impossible (as it is now). Around midnight things go back to normal. I have a 10Gbps line and the Ookla test shows that everything is flying (25-30ms ping - ~8mbps DL/0.80mbps UL) - yet it's not.
I have tried three different streaming services to make sure it's not a problem on their side. All show the same symptoms.
I have just given up trying to stream stuff with my AH account in the evenings. Streaming in the mornings works with no problems. Have just tried a WA account and works flawlessly!
AFRI.... please don't use Load shedding to pass the blame on to TELKOM. This really doesn't fly and is rather disingenuous.
I totally agree with Caroper that there may be a capacity issue looming. Remember how this was strongly denied previously and then slowly the truth emerged. I have had a couple of weeks of great service but things are rapidly, once again, going down the tubes.
It seems that as the service starts getting better more and more people start using it and capacity then becomes strained. Please AH - get this sorted out once and for all without all the meaningless explanations which, personally, don't interest me. All I want is the service you have contracted to supply me.
I am on a CapeTown exchange with 10Mbps ADSL account and have a 50+50 Gb AH capped account.
julian@gateway:~$ traceroute -n github.com
traceroute to github.com (192.30.252.130), 30 hops max, 60 byte packets
1 172.16.4.193 0.666 ms 0.688 ms 0.781 ms
2 * * *
3 41.181.178.18 125.489 ms 125.516 ms 126.303 ms
4 41.181.178.17 39.706 ms 41.797 ms 43.724 ms
5 41.181.165.115 46.000 ms 48.925 ms 51.222 ms
6 41.181.165.114 54.180 ms 196.31.180.4 55.606 ms 41.181.165.114 57.892 ms
7 41.181.180.10 259.789 ms 222.107 ms 222.515 ms
8 196.44.31.114 223.047 ms 222.950 ms 223.467 ms
9 209.212.111.187 224.216 ms 221.291 ms 223.788 ms
10 195.50.122.181 223.511 ms * 224.601 ms
11 4.69.149.82 310.594 ms 4.69.149.146 355.372 ms 4.69.149.82 354.032 ms
12 4.69.149.18 351.675 ms * 4.69.149.146 347.122 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
julian@gateway:~$ ^C
julian@gateway:~$ traceroute -n rdio.com
traceroute to rdio.com (206.217.198.146), 30 hops max, 60 byte packets
1 172.16.4.193 0.732 ms 0.755 ms 0.843 ms
2 * * *
3 41.181.178.18 302.743 ms 303.208 ms 304.031 ms
4 41.181.178.17 62.899 ms 64.084 ms 66.159 ms
5 41.181.165.115 94.129 ms 94.151 ms 94.139 ms
6 41.181.165.114 76.527 ms 196.31.180.4 78.312 ms 41.181.165.114 80.373 ms
7 41.181.180.10 307.890 ms 266.250 ms 265.492 ms
8 196.44.31.114 287.107 ms 280.844 ms 278.778 ms
9 209.212.111.201 303.337 ms 290.450 ms 290.626 ms
10 208.48.238.185 290.517 ms 219.320 ms 224.695 ms
11 * 77.67.95.173 234.494 ms 222.862 ms
12 141.136.107.117 312.290 ms 309.588 ms 309.836 ms
13 173.205.61.138 313.380 ms 310.141 ms 312.663 ms
14 69.31.110.254 320.304 ms * 317.882 ms
15 69.31.110.82 312.143 ms 312.066 ms 311.237 ms
16 * * *
17 * * *
18 * * *
19 * *^C
International seems a bit slow today. Streaming audio is buffering and github is slow with pulls.
traceroutes are all over the place