Afrihost CAPPED ADSL Feedback (MTN)

[DrJohnZoidberg]

Not there.

MIA.

If only things were that simple.

Are you accepting promotional offers and are your contact details up to date?

 

[thewusman]

Are you accepting promotional offers and are your contact details up to date?

Yebo.

All ticked.

Bizarre. I receive every other piece of email/promo/correspondence/invoices etc.

Never the mystery bonus.

Last received one back in mid 2013 from Gian when there was a promo running.

Very WTF indeed.

 

[Calv]

These are the results I'm getting from my 4meg unshaped line which I got yesterday... I have pmed you afriman.

 

[DrJohnZoidberg]

These are the results I'm getting from my 4meg unshaped line which I got yesterday... I have pmed you afriman.



View attachment 117657

Your latency looks very high.

Run the testing tool from this thread: http://mybroadband.co.za/vb/showthread.php/607090-quot-Is-it-my-Line-quot-Report-Tool

Post the results here.

 

[sgs]

On a 2mbit line with Afrihost Capped today I get packet loss and high pings even on the first hop:

---
Pinging 105.236.4.193 with 32 bytes of data:
Reply from 105.236.4.193: bytes=32 time=135ms TTL=254
Reply from 105.236.4.193: bytes=32 time=165ms TTL=254
Reply from 105.236.4.193: bytes=32 time=115ms TTL=254
Reply from 105.236.4.193: bytes=32 time=137ms TTL=254
Reply from 105.236.4.193: bytes=32 time=159ms TTL=254
Reply from 105.236.4.193: bytes=32 time=54ms TTL=254
Reply from 105.236.4.193: bytes=32 time=72ms TTL=254
Reply from 105.236.4.193: bytes=32 time=74ms TTL=254
Request timed out.
Reply from 105.236.4.193: bytes=32 time=54ms TTL=254
Reply from 105.236.4.193: bytes=32 time=62ms TTL=254
....

Ping statistics for 105.236.4.193:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),

Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 165ms, Average = 74ms
---

Anyone else in Brackenfell area? Difficult to diagnose since first hop is already on MTN's network, so cannot say if this is exchange or Afrihost related. Line stats are fine, and no errors.

Thanks!

 

[jannier]

I am in Brackenfell and not issue for me.
There are multiple DSLAM's at the exchange so it could be only the one you connecting to, mine looks perfect.

Pinging 105.236.8.193 with 32 bytes of data:
Reply from 105.236.8.193: bytes=32 time=5ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=8ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254

Ping statistics for 105.236.8.193:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 8ms, Average = 6ms

 

[jannier]

And I just pinged your "DSLAM" and looks fine from my end.

Pinging 105.236.4.193 with 32 bytes of data:
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=7ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=7ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=7ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=7ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252
Reply from 105.236.4.193: bytes=32 time=6ms TTL=252

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

 

[Beri]

http://www.speedtest.net/my-result/i/845701674

Bad in pe

 

[sgs]

I am in Brackenfell and not issue for me.
There are multiple DSLAM's at the exchange so it could be only the one you connecting to, mine looks perfect.

Thanks - ruled out everything now (filters etc.) and changed ISPs to FNB Connect. Problem persists - looks like overloaded DSLAM so will have to report to Telkom I assume.

Thank you!

 

[nicki]

Must say, my Afrihost capped account is doing way better than my Vodacom 3G speedwise today, I really tried to use the Vodacom 1GB birthday gift, but the speed is terrible. Keeps on buffering on Youtube. Switched to my Wifi connected to ADSL, and no more buffering. Thanks Afrihost!

 

[Calv]

Sorry this took a while I was out for the weekend, here are the results


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 116ms
Your maximum ping was 171ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.5.65 with 32 bytes of data:
Reply from 105.236.5.65: bytes=32 time=114ms TTL=254
Reply from 105.236.5.65: bytes=32 time=76ms TTL=254
Reply from 105.236.5.65: bytes=32 time=72ms TTL=254
Reply from 105.236.5.65: bytes=32 time=146ms TTL=254
Reply from 105.236.5.65: bytes=32 time=136ms TTL=254
Reply from 105.236.5.65: bytes=32 time=91ms TTL=254
Reply from 105.236.5.65: bytes=32 time=142ms TTL=254
Reply from 105.236.5.65: bytes=32 time=114ms TTL=254
Reply from 105.236.5.65: bytes=32 time=164ms TTL=254
Reply from 105.236.5.65: bytes=32 time=126ms TTL=254
Reply from 105.236.5.65: bytes=32 time=155ms TTL=254
Reply from 105.236.5.65: bytes=32 time=151ms TTL=254
Reply from 105.236.5.65: bytes=32 time=171ms TTL=254
Reply from 105.236.5.65: bytes=32 time=104ms TTL=254
Reply from 105.236.5.65: bytes=32 time=151ms TTL=254
Reply from 105.236.5.65: bytes=32 time=155ms TTL=254
Reply from 105.236.5.65: bytes=32 time=151ms TTL=254
Reply from 105.236.5.65: bytes=32 time=89ms TTL=254
Reply from 105.236.5.65: bytes=32 time=121ms TTL=254
Reply from 105.236.5.65: bytes=32 time=123ms TTL=254
Reply from 105.236.5.65: bytes=32 time=156ms TTL=254
Reply from 105.236.5.65: bytes=32 time=158ms TTL=254
Reply from 105.236.5.65: bytes=32 time=147ms TTL=254
Reply from 105.236.5.65: bytes=32 time=84ms TTL=254
Reply from 105.236.5.65: bytes=32 time=128ms TTL=254
Reply from 105.236.5.65: bytes=32 time=50ms TTL=254
Reply from 105.236.5.65: bytes=32 time=101ms TTL=254
Reply from 105.236.5.65: bytes=32 time=21ms TTL=254
Reply from 105.236.5.65: bytes=32 time=60ms TTL=254
Reply from 105.236.5.65: bytes=32 time=48ms TTL=254

Ping statistics for 105.236.5.65:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 171ms, Average = 116ms
 
Sun 05/11/2014 16:30:27.69

 

[froot]

Is there an issue somewhere?

I'm getting crazy pings, but it's not my exchange:

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    6 ms     8 ms     7 ms  105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
  3   215 ms   221 ms   226 ms  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
  4   233 ms   234 ms   234 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]

 

[Madhawk]

Is there an issue somewhere?]

I'm getting crazy pings too....

 

[mystic007]

Getting high pings as well, even though Afrihost's status page indicates everything is fine. (http://www.afrihost.com/site/network_status)

 

[jannier]

There seems to be an IPC issue in Gauteng.

Cape Town is looking good.

 

[Madhawk]

Back to normal on my 2Mb line...

 

[froot]

I asked Axxess (same issue there) and they said "lots of people in Pta/Jhb are complaining", and promptly closed my ticket.

 

[AfriMan]

Morning Guys

There's been an intermittent issue with Latency on the North network, seems to have gotten worse over Sunday evening. We're busy investigating the issue with MTN, but the cause seems to be a failure of a small portion of the IPC. Once we've confirmed this with Telkom we should be able to restore full capacity again. For now we're shaping as hard as possible (on Uncapped accounts) to control latency - especially with many people back at work after the string of long weekends and holidays.

If all goes well, shaping (on Uncapped) should control latency and should give mostly normal performance on unshaped services. Clients in the affected region may experience slightly higher latency - we're hoping this will not be excessive - we'll have to see as demand continues.

We're hoping to have this all sorted out as quickly as possible.

 

[OMB]

Nice to know, really buggered up my gaming experience yesterday

 

[AfriMan]

Nice to know, really buggered up my gaming experience yesterday

I can imagine. It took us a while to figure out where the latency was coming from. Now that we know, we have tweaked the network to adjust, so gaming could actually be pretty normal. Might have some intermittent spike, but otherwise mostly normal.