Afrihost New Network Feedback - Part 3

Status
Not open for further replies.
moedawood said:
Traceroute from the East:

Through VOX:

traceroute to news24.com (41.86.110.143), 30 hops max, 40 byte packets
1 * * *
2 41.193.73.214 (41.193.73.214) 36.348 ms 14.057 ms 14.445 ms
3 41.193.73.220 (41.193.73.220) 15.686 ms 15.456 ms 15.573 ms
4 mweb.dinx.net.za (196.223.30.32) 15.409 ms 15.97 ms 15.96 ms
5 197-82-7-1.dbn.mweb.co.za (197.82.7.1) 48.317 ms 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 46.499 ms 197-82-7-1.dbn.mweb.co.za (197.82.7.1) 44.899 ms
6 te0-0-0-0.vic-p-1.optinet.net (197.84.4.38) 47.123 ms te0-7-0-1.vic-p-2.optinet.net (197.84.4.44) 49.808 ms 45.605 ms
7 te0-0-0-0.cpt-p-2.optinet.net (197.84.4.46) 46.919 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 49.949 ms te0-0-0-0.cpt-p-2.optinet.net (197.84.4.46) 47.115 ms
8 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 67.346 ms 46.449 ms 44.965 ms
9 196.28.178.66 (196.28.178.66) 47.331 ms 47.62 ms 44.778 ms
10 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 46.592 ms 46.316 ms 47.647 ms
11 OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 45.701 ms 48.522 ms 45.426 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 45.312 ms 48.144 ms 47.336 ms
13 41-86-110-143.mweb.co.za (41.86.110.143) 52.107 ms 46.011 ms 47.951 ms

Through Afrihost:

traceroute to news24.com (41.86.110.143), 30 hops max, 40 byte packets
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.174) 18.544 ms 14.477 ms 14.628 ms
3 dbn-in1.ip.adsl.co.za (169.1.5.204) 18.315 ms 15.646 ms 16.403 ms
4 optinet.ixp.durban (196.10.141.75) 15.872 ms 16.543 ms 25.544 ms
5 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 45.594 ms 197-82-7-1.dbn.mweb.co.za (197.82.7.1) 47.714 ms 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 67.545 ms
6 te0-7-0-1.vic-p-2.optinet.net (197.84.4.44) 50.357 ms te0-0-0-0.vic-p-1.optinet.net (197.84.4.38) 47.002 ms 46.183 ms
7 te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 51.602 ms 197-84-4-101.cpt.mweb.co.za (197.84.4.101) 47.683 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 49.278 ms
8 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 48.385 ms te0-0-0-0.cpt-p-1.optinet.net (197.84.4.34) 48.034 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238) 46.909 ms
9 196.28.178.66 (196.28.178.66) 47.789 ms te0-7-0-0.cpt-p-2.optinet.net (197.84.4.32) 50.9 ms 196.28.178.66 (196.28.178.66) 48.698 ms
10 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 44.364 ms 45.153 ms 62.735 ms
11 OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 49.733 ms 196.28.178.66 (196.28.178.66) 45.916 ms 46.115 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 51.635 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 52.019 ms 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 49.113 ms
13 41-86-110-143.mweb.co.za (41.86.110.143) 51.066 ms OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 46.112 ms 41-86-110-143.mweb.co.za (41.86.110.143) 49.057 ms
Click to expand...

That looks good! How is the overall performance feeling at the moment?
 
AfriGenie said:
:(

I just checked on your DSL Line sync, and it looks like the actual line sync is still 3,7Mbps.

The SNR is on 7.8dB and the Attentuation is 48.6dB, so that shouldn't prevent you from getting the full 4Mbps sync.

I see that there was an open fault that was closed on the 17th of January. Did you receive any sort of feedback from Telkom?
Click to expand...

Nothing .... nada.
 
HelterSkelter said:
Eish this shaping on capped sucks. Luckily month end, changed it to 1/2 cap, no shaping from Feb. What was said before the shaping started, and what realized when the shaping started, are very different. Like day and night, and the shaping is the dark cold night.

I was always happy with AH and 99.999% a positive AH customer, even during their bad times, but this time... I feel cheated and lied to. Not cool AH, not cool.

If next month the 1/2 cap and no shaping prove to be a anything less than a 9/10 experience, I am dropping AH. Grrrr....
Click to expand...

:(

The shaping on your Capped account shouldn't have been that bad, especially since you are in the North. Which services weren't running great for you?
 
DeatheCore said:
You don't see anything local besides one hop giving 170ms? That fact alone is that there seems to be an issue at play here. I even gave a comparison of that same trace from another ISP to show you that the high latency only exists when tracing from Afrihost.

See @standerr's results above, that's exactly what I'm seeing, and it definitely impacts gaming performance (jitter or spikes).

And yes, it applies to any site or service that involves the MWEB network.
Click to expand...

We need to focus on your experience itself, the traceroutes and MTRs can be a bit misleading as you may see spikes in latency on certain routers or hops that aren't affecting the latency to the final destination. Each successive hop of the traceroute shows the latency to that hop. It's entirely possible that the hop where you are seeing the higher latency has de-prioritized ICMP traffic, but doesn't mean your actual traffic is experiencing that same latency.

If you were seeing latency spikes of 280ms in-game, then it's something we need to look into.
 
last night after 11pm the internet went totally down the crapper and we could not even browse speeds were up and down till this morning and then it started working properly again
browsing has now started to become very jerky again
 
electrofreeze said:
last night after 11pm the internet went totally down the crapper and we could not even browse speeds were up and down till this morning and then it started working properly again
browsing has now started to become very jerky again
Click to expand...

Anything specific that wasn't running as well as it should have been?
 
AfriGenie said:
We need to focus on your experience itself, the traceroutes and MTRs can be a bit misleading as you may see spikes in latency on certain routers or hops that aren't affecting the latency to the final destination. Each successive hop of the traceroute shows the latency to that hop. It's entirely possible that the hop where you are seeing the higher latency has de-prioritized ICMP traffic, but doesn't mean your actual traffic is experiencing that same latency.

If you were seeing latency spikes of 280ms in-game, then it's something we need to look into.
Click to expand...

Fair enough, I'll continue to test and relay feedback.
 
wingnut771 said:
130ms international is not possible.
Click to expand...

The lowest ping I ever seen to London is ~168ms on my brothers Vumatel Gigabit fiber in JHB, so I think you're quite right there. No way is 130ms ping to any international possible... unless we're talking about other African countries.
 
TEXTILE GUY said:
Thats sounds VERY cool

Thanks man.
Click to expand...

I've logged the fault for the sync, and I've handed the query over to our Critical Care Team. They will be in contact with you on Monday. We should be able to immediately escalate the fault on Monday.
 
Shaun108 said:
The lowest ping I ever seen to London is ~168ms on my brothers Vumatel Gigabit fiber in JHB, so I think you're quite right there. No way is 130ms ping to any international possible... unless we're talking about other African countries.
Click to expand...

It could actually have been at a breakout point on the African coast before the routing continued onto Europe. We'll need to keep an eye on the latency to make sure it doesn't result in a poor experience.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X