Afrihost New Network Feedback

Status
Not open for further replies.
I'm pinging 8.8.8.8 -t and this after I restarted my router - I have just over 10GB data left.

Packets sent: 26
Packets received: 3
Packets lost: 23

WTF AfriGuy !!!

Hard to tell what the issue is off the bad here, is there a traceroute you can post here?
 
Hard to tell what the issue is off the bad here, is there a traceroute you can post here?

What would you like me to traceroute to?

Restarted my router again and it's the same, but now the "time=300 on average"

12:45PM: no more packet drops - time is HIGH though, 200ms +-
12:47PM: Spoke too soon... packet drops are back! :mad:
 
Last edited:
What would you like me to traceroute to?

Restarted my router again and it's the same, but now the "time=300 on average"

12:45PM: no more packet drops - time is HIGH though, 200ms +-
12:47PM: Spoke too soon... packet drops are back! :mad:

tracert mybroadband.co.za

and to bbc.co.uk
 
What would you like me to traceroute to?

Restarted my router again and it's the same, but now the "time=300 on average"

12:45PM: no more packet drops - time is HIGH though, 200ms +-
12:47PM: Spoke too soon... packet drops are back! :mad:

Please run a traceroute to google.co.za.
 
Just sent a follow-up query to clarify one or two things, since your reply.

Thanks, AfriMan !

Thanks again, this time for getting back to me yesterday ; will try one or both option out sometime in the (relatively) near future .. ie. topup and/or a dedicated 10GB.

Seems weird though, that "Free GB data is treated as paid data" in context of free counted as being used first ... regarding scenario of free 1GB vs. 1GB topup.
 
Thanks again, this time for getting back to me yesterday ; will try one or both option out sometime in the (relatively) near future .. ie. topup and/or a dedicated 10GB.

Seems weird though, that "Free GB data is treated as paid data" in context of free counted as being used first ... regarding scenario of free 1GB vs. 1GB topup.

Glad we were able to help out the other day :)
Regarding the 1GB account, I'm not sure I follow around what's paid vs paid and topups?
 
Regarding the 1GB account, I'm not sure I follow around what's paid vs paid and topups?

Here's the text in full, you sent me :

Our rule of thumb is that paid data is used before promotional data, but I think Free GB data is treated as paid data. So I would think it would be monthly data first and then topup (whichever data link is older)

... so once I get going with it, I'll see how it pans out in practice.

More than anything, I wish you'd allow for EFTs ; Vox do, it works well, and the whole process seems to be automated.

I don't think they rely on someone physically checking for those EFTs, but the system alerts (them), and definitely you, if you slip-up. Has happened to me only once, when I thought I'd paid, but with everything else going on at month-end, I hadn't, so got a generic looking SMS reminder around the 2nd of the following month, after which I promptly paid.
 
Here's the text in full, you sent me :



... so once I get going with it, I'll see how it pans out in practice.

More than anything, I wish you'd allow for EFTs ; Vox do, it works well, and the whole process seems to be automated.

I don't think they rely on someone physically checking for those EFTs, but the system alerts (them), and definitely you, if you slip-up. Has happened to me only once, when I thought I'd paid, but with everything else going on at month-end, I hadn't, so got a generic looking SMS reminder around the 2nd of the following month, after which I promptly paid.

I think AfriMan may have sent that to you :)
I do share AfriMan's sentiments around which data link is used first though, if you topup then that topup data should be used before the monthly allocation does. Either way, the data is there for you to use.

We used to offer EFTs years ago but it didn't work out, and does involve a lot of backend admin from our end. Automated EFT systems could allow us to read the validity of the POP and have that amount allocated to your account, but previously we've seen a lot of late payments via EFT, or clients forgetting to use the correct ref#.

EFTs allow too much room for error and isn't an efficient payment method to fit into a fully automated billing system.
 
I think AfriMan may have sent that to you :)

Apologies - "Guy" and "Man" are so closely related, I didn't take notice of the diff. !
Thanks for the detailed explanation regarding Afri's position on EFTs.
 
Anything that'll give me an idea on where you're seeing the issues come in.
Link tests to where you're streaming from, or even a speedtest and traceroute to start :)

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.



C:\Users\Anthony-PC>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 * 41 ms 42 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 * * * Request timed out.
5 41 ms 41 ms 42 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
6 42 ms 66 ms 41 ms 169-1-5-194.ip.afrihost.co.za [169.1.5.194]
7 42 ms 41 ms 42 ms 41.169.57.218
8 * * * Request timed out.
9 210 ms 209 ms 228 ms if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net [216.6.55.85]
10 216 ms 220 ms 215 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
11 183 ms 182 ms 184 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
12 224 ms 212 ms 212 ms if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
13 216 ms 215 ms 218 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
14 205 ms 206 ms 228 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
15 212 ms 212 ms 212 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
16 216 ms 218 ms 217 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
17 211 ms 211 ms 212 ms 195.219.83.102
18 * * * Request timed out.
19 213 ms 213 ms 213 ms unknown.Level3.net [212.187.139.230]
20 * * * Request timed out.
21 217 ms 215 ms 215 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
22 211 ms 211 ms 212 ms 132.185.255.148
23 217 ms 216 ms 216 ms 212.58.244.22

Trace complete.
 
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.



C:\Users\Anthony-PC>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:

-snip

Trace complete.

Seems like quite a bit of packet loss here - is any packet loss reported when running a ping to bras.afrihost.com?
 
When do I have to change CC details in Client Zone? By what date? Switching cards to a new one for payment
 
Seems like quite a bit of packet loss here - is any packet loss reported when running a ping to bras.afrihost.com?

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Anthony-PC>tracert bras.afrihost.com

Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 40 ms 40 ms 43 ms 155.239.255.250

Trace complete.

C:\Users\Anthony-PC>

but then local speed is as it should be.
 
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Anthony-PC>tracert bras.afrihost.com

Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 40 ms 40 ms 43 ms 155.239.255.250

Trace complete.

C:\Users\Anthony-PC>

but then local speed is as it should be.

Can you run a ping to bras.afrihost.com instead of a traceroute please?
 
C:\Users\Anthony-PC>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=40ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms 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 = 40ms, Maximum = 44ms, Average = 41m
C:\Users\Anthony-PC>ping bbc.co.uk

Pinging bbc.co.uk [212.58.244.22] with 32 bytes of data:
Reply from 212.58.244.22: bytes=32 time=218ms TTL=39
Reply from 212.58.244.22: bytes=32 time=216ms TTL=39
Request timed out.
Reply from 212.58.244.22: bytes=32 time=217ms TTL=39

Ping statistics for 212.58.244.22:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 216ms, Maximum = 218ms, Average = 217ms

C:\Users\Anthony-PC>
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X