i.got~issues
Expert Member
Hi AfriMan
Local throughput is always good it seems... it is just the international that tanks without warning... and it is not quite daily lately... every now and again / couple of days.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Which is the most hair-raising South African mountain pass you've driven?
Afrihost POC Network - Afrigreen Feedback
- Thread starter AfriGuy
- Start date
- Status
Hi AfriMan
Local throughput is always good it seems... it is just the international that tanks without warning... and it is not quite daily lately... every now and again / couple of days.
If it's limited to international that changes things, we'll need to investigate differently. Let's monitor this, we'll also test on our side
i.got~issues
Expert Member
If it's limited to international that changes things, we'll need to investigate differently. Let's monitor this, we'll also test on our side
Coolios... I will hola here then if it continues to do this... usually I just switch accounts and try again later...
I don't see why it would though, the network is quiet and local is fine, so I am guessing it could be something upstream. Does it seem to happen randomly or at specific times that you've noticed?
i.got~issues
Expert Member
Hmmmm... more random than specific... seems to be mornings mostly, from what I am trying to remember. A couple of weekends too.
I cannot say how long it is affected for, as I switch accounts after a few minutes of waiting for a recovery.
My streaming audio begins to buffer, this is the indicator that AfriGreen is about to hiccup... and then speedtests confirm the throughput tanking.
Weird, but definitely makes sense that it's random. Could be international backhaul, as we're using various options at the moment. We'll need to know the exact time and duration (with traces) to see which route the traffic could be taking and see if we can report that upstream
i.got~issues
Expert Member
Weird, but definitely makes sense that it's random. Could be international backhaul, as we're using various options at the moment. We'll need to know the exact time and duration (with traces) to see which route the traffic could be taking and see if we can report that upstream
I just assumed it was POC testing, tweaking and updates etc... thus just waited it out.
I will make a point of logging these here in future...
AfriGreen is still potentially awesome... and will be once the latency is sorted in future when the south IPC thing happens... so looking forward to Zen then again.
It could be testing, so the exact times and traceroutes could point to what is being testing or which upstream routing we used at that time which could be problematic - if that is the issue.
Really appreciate all the info - AfriGreen is definitely showing a lot of promise
i.got~issues
Expert Member
It could be testing, so the exact times and traceroutes could point to what is being testing or which upstream routing we used at that time which could be problematic - if that is the issue.
Really appreciate all the info - AfriGreen is definitely showing a lot of promise
Actually AfriGreen is awesome.
Loving it myself!
I must say that ever since I started using Afrigreen, I just cant complain. It meets my internet requirements. Thanks
Really good to hear. Is it pretty much working on all services for you?
Afriman I've explained this twice now...
The problem is around 20:30 till sometime after 00:00 - varies
Are you saying testing with Axxess is not sufficient???
What does including the first two lines of 192.168.1.1 and *** going to help when my query has to do with the low speed (shown in the saix ping test)? My line is syncing at 4094 yet speed test clearly shows I'm getting around 2Mbps...
This extends to both your Afrihost and Afrigreen accounts yet Axxess works perfectly fine...
Last edited:
The traces you submitted were both from Afrigreen. The Axxess test (which would also be on the MTN network as our regular network) also showed spikes in latency although your destination latency was better. From that data I would say it's highly unlikely for two discreet networks to exhibit similar latency intermittent symptoms unless the common factor, which could be the line or local network, is affected. The account which was first connected could be affected from a previous connection, where resetting the port when you change accounts could show briefly better results. We see this often with congested exchanges. Again, this is why we should troubleshoot further before making conclusions.
The first two hops of the trace would show if there is a problem on your local network (if pings to your router are also inconsistent. From your tests already submitted, the inconsistent pings seem to be across all the test results you submitted so I would guess it's a line problem at this stage, without seeing further data.
Hey, here's tests I've done now.
Download speeds going at full speed 700-800kbps but as it's been for the last 1 and a half weeks when my downloads go at full speed I'm unable to do any browsing.
Here's the tests:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 9ms, Average = 8ms
------------------
tracert to twitter while downloading
Tracing route to twitter.com [199.16.156.70]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 10 ms 9 ms 8 ms 41.170.79.236
6 11 ms 9 ms 10 ms 41.169.26.62
7 9 ms 9 ms 12 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [2
16.6.55.37]
8 189 ms 188 ms 187 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.1
78.2]
9 230 ms 168 ms 157 ms if-1-0-0-4.core2.PV9-Lisbon.as6453.net [195.219.
214.37]
10 189 ms 189 ms 189 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.2
31.158.1]
11 187 ms 204 ms 186 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
12 191 ms 202 ms 190 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138
.22]
13 188 ms 188 ms 186 ms if-2-2.tcore1.L78-London.as6453.net [80.231.131.
2]
14 189 ms 193 ms 188 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
15 192 ms 190 ms 189 ms 195.219.83.102
16 190 ms 189 ms 193 ms ae-124-3510.edge5.london1.Level3.net [4.69.166.3
7]
17 188 ms 189 ms 220 ms ae-124-3510.edge5.london1.Level3.net [4.69.166.3
7]
18 190 ms 191 ms 190 ms TWITTER-INC.edge5.London1.Level3.net [195.50.120
.66]
19 273 ms 272 ms 271 ms ae65.atl1-er2.twttr.com [192.133.76.19]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * 274 ms 199.16.156.70
Trace complete.
This looks mostly fine to me. Sounds like whatever is happening is a local problem. Maybe something to do with how you've setup QoS or the DNS you're using. If you can download at full speed there is nothing wrong with throughput, so not being able to browse is not the network being weird, from what I can see
This looks mostly fine to me. Sounds like whatever is happening is a local problem. Maybe something to do with how you've setup QoS or the DNS you're using. If you can download at full speed there is nothing wrong with throughput, so not being able to browse is not the network being weird, from what I can see
I haven't setup QoS and I'm using google DNS.
This problem with being unable to browse when downloading at full speed only started the previous week. Before I never had this issue.
So what should I do?
Couldn't say. Remember that when you're maxing your line, especially with torrents, you are going to delay packets being received or sent that are essential for browsing, which is why QoS is important to prioritise browsing traffic over downloads. Maybe try limiting your downloads and then raising the limit slowly to see exactly how much you can max out if you need to browse.
I'm not downloading with torrents, just normal downloads.
Also If the problem never happened before why would it all of a sudden start now?
Isn't the whole point of being unshaped that I should be able to download at full speed and browse?
- Status