Afrihost New Network Feedback

Status
Not open for further replies.
speed test is still shocking though.. barely getting above 4mbps

Tracing route to mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 15 ms 12 ms 14 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 13 ms 13 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 14 ms 14 ms 14 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 15 ms 14 ms 13 ms africainx.ct1.napafrica.net [196.10.140.7]
7 67 ms 72 ms 73 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za [41.84.13.228]
8 68 ms 48 ms 51 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 38 ms 34 ms 34 ms 104.20.72.110

Trace complete.

C:\Users\Dell>
 
Anyone else having serious connection issues atm? Even when my connection works, the latency is terrible.

Edit: Rebooted several times and tried Google's DNS to no avail. Then tried out my backup 10GB ISPAfrika account and it connected almost instantly and my connection is running like The Flash.

Wtf Afrihost?
 
Last edited:
Morning guys

First off, very sorry about the erratic international latency/ packet loss yesterday :(
The issue seemed to be isolated to the East initially, but did move across all POPs. We managed to get things fixed up by mid-afternoon yesterday and seeing good results this morning.

If anyone is still seeing packet loss or high latency to international destinations please let me know :)
Otherwise I hope everyone had a rocking weekend!
 
Jola said:
OK, so someone from AH came in this morning and reset the line, so all is fine again.

But this leaves a few questions :

1) Why do AH lines often die on Saturday afternoons ? This also happened a few weeks ago.

2) Why is there no support to resolve this ? Yesterday there was absolutely nothing, no phone support, no chat support, no e-mail support.

3) Why does the "Fix my line" function just set the line to 65kbps and effectively kill it stone dead. This used to be a valuable tool in the past, AFAIK it used to perform a port reset and often fixed the line, now it just kills it, so one should under no circumstances run this tool.

Is it just "all fall down" at AH ?
Click to expand...

Happy to look at why the line's dropping, but it shouldn't happen from a data side. If the line itself is an issue then that would be the cause.
The fix my line runs through various checks and actions - part of which runs an API call to Telkom to drop the line completely and bring it back up again - with lines that have comms issues on the DSLAM - the API isn't always responsive to bring things back up again.

Either way, sounds like a fault needs to be logged here.
 
bigboy529 said:
My sister moved in to a new place and I helped her with the ADSL setup. Currently a 2 MB line but waiting for Telkom to change it to 4 MB and capped Afrihost account.
What does it mean if the router reports error packets and how can it be fixed?
The router reports something like 40 upstream and 7 downstream error packets.

Also, if a router gives a certain upstream and downstream speed in this case 508 and 2508, why can't I get close to that speeds doing a speed test through a browser?
Click to expand...

Error packets shouldn't be much of a concern for WAN, these are basically colliding TCP packets.
From the sync speeds you're describing, you're on a 2Mbps line run via ASSIA, hence the extra 508kbps - you should see anywhere from 1.5Mbps to 2Mbps on speedtests.
 
Bryn said:
Anyone else having serious connection issues atm? Even when my connection works, the latency is terrible.

Edit: Rebooted several times and tried Google's DNS to no avail. Then tried out my backup 10GB ISPAfrika account and it connected almost instantly and my connection is running like The Flash.

Wtf Afrihost?
Click to expand...

Sorry to hear :(
We did see some international issues when you posted, but these where fixed up by then.

Did you manage to grab a traceroute or some pings you can post up here?
 
I swear if Telkom again sends me an sms saying they have resolved my issue, then im going to explode.

How do you resolve an issue like congestion, without actually physically sending out a technician to attend to it?

I ran a speed test this morning and got around 16.8mbps , but last night it was at 3.9mbps. So clearly evenings is a problem in terms of speed, but then i look at the latency and jitter and then i think is it exchange because my latency last night was at 13ms and Jitter 1
 
Icemanbrfc said:
I swear if Telkom again sends me an sms saying they have resolved my issue, then im going to explode.

How do you resolve an issue like congestion, without actually physically sending out a technician to attend to it?

I ran a speed test this morning and got around 16.8mbps , but last night it was at 3.9mbps. So clearly evenings is a problem in terms of speed, but then i look at the latency and jitter and then i think is it exchange because my latency last night was at 13ms and Jitter 1
Click to expand...

From the previous tests you ran on your 10Mbps (or 8Mbps?) sync profile, throughput didn't seem so great there either - so sounds like the area isn't able to sufficiently support throughput. This only becomes more obvious at higher sync rates.
 
AfriGuy said:
Sorry to hear :(
We did see some international issues when you posted, but these where fixed up by then.

Did you manage to grab a traceroute or some pings you can post up here?
Click to expand...

Unfortunately not. My normal latency to Google has drastically increased since a few days ago though. Used to be a quarter of what it is now.

C:\WINDOWS\System32>tracert www.google.com

Tracing route to www.google.com [216.58.208.228]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 22 ms 21 ms 18 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 29 ms 26 ms 26 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 27 ms * 27 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 23 ms 22 ms 22 ms 41.164.52.40
7 40 ms 43 ms 42 ms 172.18.1.162
8 42 ms 42 ms 44 ms 72.14.194.206
9 207 ms 207 ms 207 ms 216.239.54.57
10 221 ms 213 ms 210 ms 209.85.143.219
11 218 ms 219 ms 219 ms 216.239.47.186
12 211 ms 211 ms 211 ms 209.85.143.243
13 220 ms 218 ms 219 ms par10s22-in-f4.1e100.net [216.58.208.228]

Trace complete.

C:\WINDOWS\System32>
Click to expand...
 
Bryn said:
Unfortunately not. My normal latency to Google has drastically increased since a few days ago though. Used to be a quarter of what it is now.
Click to expand...

Weird that traffic is routing internationally here, my results show about 45ms to google.com.
What DNS servers are you using?
 
The way Afrihost shows data usage is so confusing. I can't tell the difference between normal and zero rated usage on the graph :(

Could you ask the devs to please change the way its displayed.
 
MikeKee said:
The way Afrihost shows data usage is so confusing. I can't tell the difference between normal and zero rated usage on the graph :(

Could you ask the devs to please change the way its displayed.
Click to expand...

The after hours traffic won't be displayed on the graph as it doesn't contribute to your overall monthly usage. There is a data link under the graph that shows how many GBs have been used though :)

EDIT: My bad, slow Monday. After hours usage does display in the usage graphs.
 
Last edited:
AfriGuy said:
The after hours traffic won't be displayed on the graph as it doesn't contribute to your overall monthly usage. There is a data link under the graph that shows how many GBs have been used though :)
Click to expand...

Capture.PNG

I am having trouble reading this graph if what you said is true.

The after hours traffic won't be displayed on the graph
Click to expand...
 
AfriGuy said:
Thanks.
What happens when you traceroute google.co.za?
Click to expand...

Same thing.

C:\WINDOWS\System32>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.208.227]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 13 ms 14 ms 14 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 14 ms 14 ms 14 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 20 ms * 19 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 12 ms 14 ms 14 ms 41.164.52.40
7 36 ms 35 ms 36 ms 172.18.1.162
8 36 ms 35 ms 34 ms 72.14.194.206
9 206 ms 201 ms 203 ms 216.239.54.57
10 212 ms 210 ms 210 ms 216.239.58.3
11 204 ms 207 ms 206 ms 209.85.248.30
12 206 ms 206 ms 207 ms 209.85.143.243
13 212 ms 210 ms 211 ms par10s22-in-f3.1e100.net [216.58.208.227]

Trace complete.

C:\WINDOWS\System32>
Click to expand...
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X