Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Anybody else Having issues in Amanzimtoti or durban areas? No internationals and local is almost non-existent.
 
Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 * 176 ms 174 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 173 ms 174 ms * dbn-in1.ip.adsl.co.za [169.1.5.204]
5 * 175 ms 174 ms optinet.db1.napafrica.net [196.10.141.75]
6 190 ms 188 ms 187 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
7 187 ms * * te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
8 * 207 ms 205 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
9 203 ms * 203 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
10 * * 188 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
11 203 ms 203 ms 204 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
12 188 ms 186 ms 189 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
13 205 ms * 204 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Pinging www.afrihost.co.za [41.86.112.68] with 32 bytes of data:
Request timed out.
Reply from 41.86.112.68: bytes=32 time=205ms TTL=48
Reply from 41.86.112.68: bytes=32 time=204ms TTL=48
Reply from 41.86.112.68: bytes=32 time=204ms TTL=48

Ping statistics for 41.86.112.68:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 204ms, Maximum = 205ms, Average = 204ms
 
Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 * 176 ms 174 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 173 ms 174 ms * dbn-in1.ip.adsl.co.za [169.1.5.204]
5 * 175 ms 174 ms optinet.db1.napafrica.net [196.10.141.75]
6 190 ms 188 ms 187 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
7 187 ms * * te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
8 * 207 ms 205 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
9 203 ms * 203 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
10 * * 188 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
11 203 ms 203 ms 204 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
12 188 ms 186 ms 189 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
13 205 ms * 204 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Pinging www.afrihost.co.za [41.86.112.68] with 32 bytes of data:
Request timed out.
Reply from 41.86.112.68: bytes=32 time=205ms TTL=48
Reply from 41.86.112.68: bytes=32 time=204ms TTL=48
Reply from 41.86.112.68: bytes=32 time=204ms TTL=48

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

Latency is all over the place here, can you grab a ping to bras.afrihost.com please?
 
Hi there, I have noticed a "slight" improvement with my throughput @Afriguy. Internationals are still a bit spotty though...

Here is the ping for "bras":

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=101ms TTL=63
Reply from 155.239.255.250: bytes=32 time=102ms TTL=63
Reply from 155.239.255.250: bytes=32 time=102ms TTL=63
Reply from 155.239.255.250: bytes=32 time=103ms 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 = 101ms, Maximum = 103ms, Average = 102ms

.... so sorry talked too soon, internationals are still atrocious...
 
Last edited:
Hi there, I have noticed a "slight" improvement with my throughput @Afriguy. Internationals are still a bit spotty though...

Here is the ping for "bras":

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=101ms TTL=63
Reply from 155.239.255.250: bytes=32 time=102ms TTL=63
Reply from 155.239.255.250: bytes=32 time=102ms TTL=63
Reply from 155.239.255.250: bytes=32 time=103ms 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 = 101ms, Maximum = 103ms, Average = 102ms

.... so sorry talked too soon, internationals are still atrocious...

This is latency to your exchange, which could indicate congestion or other issues.
Any services running in the background?
 
Seems to load up OK for me, is there a traceroute I can take a look at?

Also checked standardbank on my side... Also not loading. Locals is slow, facebook loads two posts then stops, youtube is non-existent.

@Afriguy, seems there is a problem on your KZN side, as myself and @Hummercellc wont be on the same exchange but will be on the same route most probably.
 
Also checked standardbank on my side... Also not loading. Locals is slow, facebook loads two posts then stops, youtube is non-existent.

@Afriguy, seems there is a problem on your KZN side, as myself and @Hummercellc wont be on the same exchange but will be on the same route most probably.

I can't pick up any general issues in the area, I'm afraid I'll need to take a look at some data in order to comment further.
From your previous tests you look to be affected by a congested exchange though.
 
Also checked standardbank on my side... Also not loading. Locals is slow, facebook loads two posts then stops, youtube is non-existent.

@Afriguy, seems there is a problem on your KZN side, as myself and @Hummercellc wont be on the same exchange but will be on the same route most probably.

Yip Internet almost non-existent, but it seems to be fine for 5 mins then nothing.

Also I noticed Afrihost DNS servers are now 169.1.1.10 and 169.1.1.11?

Can we please stick to a permanent set of IP's?
 
Yip Internet almost non-existent, but it seems to be fine for 5 mins then nothing.

Also I noticed Afrihost DNS servers are now 169.1.1.10 and 169.1.1.11?

Can we please stick to a permanent set of IP's?

Auto-assigned DNS will change when/ if our IP's change :)
 
You guys should be on top of this to be honest...its not the customers problem. We have given you evidence that it only happens on your network so i think it's time for you to investigate...

^^ This... I pay for my data and line to be with you guys... I can't phone Mweb and flame at them for it... It makes no sense to me. It's actually easier for me to just move back to telkom. Less hassles...
 
^^ This... I pay for my data and line to be with you guys... I can't phone Mweb and flame at them for it... It makes no sense to me. It's actually easier for me to just move back to telkom. Less hassles...

Our peering links are in order, I'm afraid we can't control traffic outside of our network.
 
Our peering links are in order, I'm afraid we can't control traffic outside of our network.

That's a shocking response. No empathy or willingness to help or fix the issue (there CLEARLY is an issue that only happens on YOUR network). That's the nail in the coffin for me, luckily before the 25th so I can cancel.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X