Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
craigcul said:
Hi AfriMan here is the afrihost test program that i have run now my adsl line is still not usable i am using my 3g connection to post this test
Ping Test:

-snip
Click to expand...

Results are a bit up and down here - could you shoot me a PM with your details?
 
Apple OS X update download speed slow on Afrihost

3696ed1bc4f53078ccdc325038e68c72.png
 
AfriGuy
This is the bras trace route
operable program or batch file.

C:\Users\Craig Laptop>tracert bras.afrihost.com

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

1 3 ms 1 ms <1 ms 192.168.20.21
2 9 ms 8 ms 8 ms 169-0-55-1.ip.afrihost.co.za [169.0.55.1]
3 * * * Request timed out.
4 10 ms 12 ms 10 ms 169-1-5-202.ip.afrihost.co.za [169.1.5.202]
5 97 ms 102 ms 111 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 33 ms 37 ms 37 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 104 ms 102 ms 94 ms 41.169.57.216
8 * * 14 ms 41.160.2.69
9 11 ms 11 ms 11 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
10 196.43.26.106 reports: Destination host unreachable.

Trace complete.

C:\Users\Craig Laptop>
 
hi google tracerout
C:\Users\Craig Laptop>tracert google.co.za

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

1 3 ms <1 ms <1 ms 192.168.20.21
2 9 ms 8 ms 8 ms 169-0-55-1.ip.afrihost.co.za [169.0.55.1]
3 * * * Request timed out.
4 * 63 ms 33 ms 169-1-5-202.ip.afrihost.co.za [169.1.5.202]
5 * 58 ms 52 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 13 ms 10 ms 10 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 * * 10 ms 72.14.237.239
8 10 ms * 17 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\Users\Craig Laptop>
 
kohlhtor said:
Telkom full line speed

40daa332e70047a22dca93472265f675.png
Click to expand...
International http single threaded downloads generally do not go past 300kb/s, but local downloads seem to get full line speed 1200kb/s. If I switch to my Mweb account both max out my line. International is truly Afrihost's biggest problem/flaw.
 
Last edited:
AfriGenie said:
There shouldn't have been any spikes in latency, did you maybe get a traceroute so that I can check where the issue popped up?
Click to expand...

I don't have tracerts now but yesterday basicaly it was when it was hitting cpt-net1.ip.adsl.co.za [169.1.5.128], you would get consistent pings of around 20 then it would pump a 100-150 ms spike then back down to 20. In a game it feels like dropped packets. cpt-rx2.ip.adsl.co.za [169.1.5.82] and bras was low 12-15.
 
Vio said:
I don't have tracerts now but yesterday basicaly it was when it was hitting cpt-net1.ip.adsl.co.za [169.1.5.128], you would get consistent pings of around 20 then it would pump a 100-150 ms spike then back down to 20. In a game it feels like dropped packets. cpt-rx2.ip.adsl.co.za [169.1.5.82] and bras was low 12-15.
Click to expand...

What do you know, it just started again ~8pm: here's a ping to cpt-net1.ip.adsl.co.za [169.1.5.128] demonstrating the issue

Pinging 169.1.5.128 with 32 bytes of data:
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=20ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=17ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=60ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=15ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=17ms TTL=61
Reply from 169.1.5.128: bytes=32 time=23ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=20ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=75ms TTL=61
Reply from 169.1.5.128: bytes=32 time=16ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=17ms TTL=61
Reply from 169.1.5.128: bytes=32 time=14ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=12ms TTL=61
Reply from 169.1.5.128: bytes=32 time=13ms TTL=61
Reply from 169.1.5.128: bytes=32 time=21ms TTL=61

Ping statistics for 169.1.5.128:
Packets: Sent = 53, Received = 53, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 75ms, Average = 16ms

These spikes in game feel like dropped packets for like a quarter of a second to half a second as the ping spikes increase in latency so does the duration of the dropped packet feel in game.
 
Local latency is all over the place, hop 2 is bad, and I can't access Mweb sites again! :mad: 5th night in a row.

myaccount.mweb.co.za and mweb.co.za


Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 78 ms 74 ms 68 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 16 ms 17 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 15 ms 15 ms 15 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 26 ms 27 ms 23 ms optinet.db1.napafrica.net [196.10.141.75]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9
 
Hummercellc said:
Local latency is all over the place, hop 2 is bad, and I can't access Mweb sites again! :mad: 5th night in a row.

myaccount.mweb.co.za and mweb.co.za


Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 78 ms 74 ms 68 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 16 ms 17 ms 16 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 15 ms 15 ms 15 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
5 26 ms 27 ms 23 ms optinet.db1.napafrica.net [196.10.141.75]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9
Click to expand...

Latency looks pretty high to your exchange here.
What DNS servers are you using?
 
AfriGuy said:
Latency looks pretty high to your exchange here.
What DNS servers are you using?
Click to expand...

The standard Afrihost DNS servers, I have been reporting this every night?

I can access it from Mweb, Vox & IS accounts, and tried across 4 of my 12 DSL lines :whistle:

Clearly it has not be taken seriously?
 
Hummercellc said:
The standard Afrihost DNS servers, I have been reporting this every night?

I can access it from Mweb, Vox & IS accounts, and tried across 4 of my 12 DSL lines :whistle:

Clearly it has not be taken seriously?
Click to expand...

I can't trend any issues that others are seeing around this, have you submitted a Support ticket for us to escalate from there?
 
Hummercellc said:
Seriously? Never mind will route those sites over an ISP that works. ;)
Friend in PMB can't access Mweb sites either.
Click to expand...

I really do think it's best to have a query logged, it means your details are consolidated and can be much easier escalated where necessary.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X