Afrihost New Network Feedback

Status
Not open for further replies.
Luke7777 said:
Would be nice if people can add their location to their profiles. City or town will do. At least then one can see where problems are experienced. But that's just my opinion :)
Click to expand...

It would help :)
Not always necessary though, we can at least narrow down the IPC region from a traceroute.
 
AfriGuy said:
We've given back to our clients in the past, this should be no different.
I believe we've discussed this before - the decision is with Management, I'm confident they'll make a good decision.
Click to expand...

As a Business client, I have never received a cent for the last 2 years of crap here in the SOUTH.... Capped clients have gotten plenty of freebies, mystery discounts/gifts...

BTW, I reported email issues a few days ago and was told it is my VPS. Yet, all of a sudden, my line dropped last night, and now port 587 is now accessible from an AH account. Before it would not work, unless I used a different ISP (YES... any other ISP - no issues).

Seems that was just a tell-tale sign of what we are experiencing now here in the SOUTH.
 
Last edited:
cortexenslaver said:
As a Business client, I have never received a cent for the last 2 years of crap here in the SOUTH.... Capped clients have gotten plenty of freebies, mystery discounts/gifts...

BTW, I reported email issues a few days ago and was told it is my VPS. Yet, all of a sudden, my line dropped last night, and now port 587 is now accessible from an AH account. Before it would not work, unless I used a different ISP (YES... any other ISP - no issues).

Seems that was just a tell-tale sign of what we are experiencing now here in the SOUTH.
Click to expand...

Not sure if you got my PM, but we had a pretty lengthy chat via PM around exactly this - which I believe you've been running some tests with your host. On top of this, our network team reached out to the hosts.

As per my PM last night, port 587. I need to stress that this was not an issue specific to Afrihost though. That should be backed up via the context of the PM though.
 
Been battling for most of the afternoon. Pietermaritzburg

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=52 time=3123 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=3155 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=2494 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=52 time=917 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=52 time=1289 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=52 time=2039 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=2262 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=3044 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=52 time=3488 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=52 time=1212 ms
 
al4bb said:
Been battling for most of the afternoon. Pietermaritzburg

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=52 time=3123 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=3155 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=2494 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=52 time=917 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=52 time=1289 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=52 time=2039 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=53 time=2262 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=53 time=3044 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=52 time=3488 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=52 time=1212 ms
Click to expand...

That latency is a bit extreme to what we've seen posted here before :(
Can you paste the details of a traceroute to mybroadband.co.za as well as a ping to bras.afrihost.com please?
 
AfriGuy said:
Are you sure your isn't at 4Mbps? Is the max line speed is 2Mbps it's pretty impossible to get anything higher than that.
Unless Mbps MB/s kbps and KB/s are being mixed up here :)
Click to expand...

:D im just messing with the guys Afriguy... Bit of humour and fun for a change around here :whistle:
 
AfriGuy said:
That latency is a bit extreme to what we've seen posted here before :(
Can you paste the details of a traceroute to mybroadband.co.za as well as a ping to bras.afrihost.com please?
Click to expand...

This is going to blow your mind:

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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 2887 ms 3547 ms 2911 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 2263 ms 2741 ms 1394 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 1839 ms 2521 ms * dbn-in1.ip.adsl.co.za [169.1.5.204]
6 971 ms 893 ms 1207 ms 41.162.84.192
7 2377 ms 3420 ms 3526 ms 172.18.1.162
8 1867 ms 2242 ms 2553 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
9 * 3684 ms 1974 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 2641 ms * 3837 ms if-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
11 2981 ms 2325 ms 3181 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 3029 ms 2825 ms 2762 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 2529 ms 2277 ms 2096 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
14 * 2372 ms 2411 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
15 * 2752 ms 2572 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 3099 ms 2890 ms 2737 ms 195.219.83.186
17 2945 ms 2364 ms 2650 ms 81.25.207.54
18 3261 ms 2649 ms 2767 ms 104.20.72.110

Trace complete.



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=459ms TTL=63
Reply from 155.239.255.250: bytes=32 time=702ms TTL=63
Reply from 155.239.255.250: bytes=32 time=441ms TTL=63
Reply from 155.239.255.250: bytes=32 time=461ms 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 = 441ms, Maximum = 702ms, Average = 515ms
 
al4bb said:
This is going to blow your mind:

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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 2887 ms 3547 ms 2911 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 2263 ms 2741 ms 1394 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 1839 ms 2521 ms * dbn-in1.ip.adsl.co.za [169.1.5.204]
6 971 ms 893 ms 1207 ms 41.162.84.192
7 2377 ms 3420 ms 3526 ms 172.18.1.162
8 1867 ms 2242 ms 2553 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
9 * 3684 ms 1974 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 2641 ms * 3837 ms if-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
11 2981 ms 2325 ms 3181 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 3029 ms 2825 ms 2762 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 2529 ms 2277 ms 2096 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
14 * 2372 ms 2411 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
15 * 2752 ms 2572 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 3099 ms 2890 ms 2737 ms 195.219.83.186
17 2945 ms 2364 ms 2650 ms 81.25.207.54
18 3261 ms 2649 ms 2767 ms 104.20.72.110

Trace complete.



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=459ms TTL=63
Reply from 155.239.255.250: bytes=32 time=702ms TTL=63
Reply from 155.239.255.250: bytes=32 time=441ms TTL=63
Reply from 155.239.255.250: bytes=32 time=461ms 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 = 441ms, Maximum = 702ms, Average = 515ms
Click to expand...

Seeing huge latency to your exchange here, possibly due to congestion :(
 
AfriGuy said:
Thanks dude :)
Click to expand...

Just an update. Using Web Africa Account.

Haven't really noticed any major degradation in my speed.

Downloading at 1mbps still. Speed test looks fine too.

http://netgauge.ookla.com/share/307673784.png

Traceroute I'm guessing is not that great?

Tracing route to 180upload.com [185.57.82.116]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 57 ms 69 ms 8 ms cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]

4 9 ms 9 ms 9 ms 196.38.73.85
5 8 ms 9 ms 8 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 10 ms 11 ms 11 ms core1b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.62]

7 201 ms 198 ms 200 ms 168.209.201.85
8 182 ms 181 ms 182 ms xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net [83.23
1.235.221]
9 194 ms 192 ms 206 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
10 251 ms * 202 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.1
38]
11 204 ms 203 ms 211 ms ae-2.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.2
17]
12 * * * Request timed out.
13 200 ms 203 ms 249 ms fra-in3-02gw.voxility.net [5.254.88.13]
14 189 ms 194 ms 189 ms fra-in8-01c.voxility.net [5.254.88.6]
15 233 ms 239 ms 233 ms buc-ird-01c.voxility.net [5.254.88.198]
16 226 ms 226 ms 226 ms alistaro-19sw.alistaro.com [195.60.76.126]
17 230 ms 230 ms 230 ms 185.57.82.116

Trace complete.

Will post another update tonight too.
 
al4bb said:
This is going to blow your mind:

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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 2887 ms 3547 ms 2911 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 2263 ms 2741 ms 1394 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 1839 ms 2521 ms * dbn-in1.ip.adsl.co.za [169.1.5.204]
6 971 ms 893 ms 1207 ms 41.162.84.192
7 2377 ms 3420 ms 3526 ms 172.18.1.162
8 1867 ms 2242 ms 2553 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
9 * 3684 ms 1974 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 2641 ms * 3837 ms if-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
11 2981 ms 2325 ms 3181 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 3029 ms 2825 ms 2762 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 2529 ms 2277 ms 2096 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
14 * 2372 ms 2411 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
15 * 2752 ms 2572 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 3099 ms 2890 ms 2737 ms 195.219.83.186
17 2945 ms 2364 ms 2650 ms 81.25.207.54
18 3261 ms 2649 ms 2767 ms 104.20.72.110

Trace complete.



Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=459ms TTL=63
Reply from 155.239.255.250: bytes=32 time=702ms TTL=63
Reply from 155.239.255.250: bytes=32 time=441ms TTL=63
Reply from 155.239.255.250: bytes=32 time=461ms 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 = 441ms, Maximum = 702ms, Average = 515ms
Click to expand...

Deeeeefinitely exchange issues...
 
KoolDaffy said:
Just an update. Using Web Africa Account.

Haven't really noticed any major degradation in my speed.

Downloading at 1mbps still. Speed test looks fine too.

http://netgauge.ookla.com/share/307673784.png

Traceroute I'm guessing is not that great?

Tracing route to 180upload.com [185.57.82.116]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 57 ms 69 ms 8 ms cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]

4 9 ms 9 ms 9 ms 196.38.73.85
5 8 ms 9 ms 8 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 10 ms 11 ms 11 ms core1b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.62]

7 201 ms 198 ms 200 ms 168.209.201.85
8 182 ms 181 ms 182 ms xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net [83.23
1.235.221]
9 194 ms 192 ms 206 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
10 251 ms * 202 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.1
38]
11 204 ms 203 ms 211 ms ae-2.r03.frnkge03.de.bb.gin.ntt.net [129.250.6.2
17]
12 * * * Request timed out.
13 200 ms 203 ms 249 ms fra-in3-02gw.voxility.net [5.254.88.13]
14 189 ms 194 ms 189 ms fra-in8-01c.voxility.net [5.254.88.6]
15 233 ms 239 ms 233 ms buc-ird-01c.voxility.net [5.254.88.198]
16 226 ms 226 ms 226 ms alistaro-19sw.alistaro.com [195.60.76.126]
17 230 ms 230 ms 230 ms 185.57.82.116

Trace complete.

Will post another update tonight too.
Click to expand...

Please would you run this:

http://bit.ly/1lqvJpd

Z
 
Zertop said:
Please would you run this:

http://bit.ly/1lqvJpd

Z
Click to expand...

Zertop's "Is it my Line" Results
Date/Time: Wed Oct 28 16:36:12 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 11ms.
Your maximum ping was 124ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.

Detailed Report:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=124ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms 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=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 124ms, Average = 11ms

There you go.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X