Absolute Huge Latency on Axxess Uncapped

internaut

internaut

Senior Member
Joined
Oct 3, 2005
Messages
702
Reaction score
71
Location
Cape Town, Southern, Surrey Estate
Hey guys, ever since the "resolution" of the authentication issue with Axxess and Afrihost, im now experiencing super latency on my Axxess uncapped account. My Afrihost Capped and Webafrica Capped accounts perform nominally.
Also bearing in mind that it did work flawlessly before I, stupidly, decided to log-out out of my uncapped account to perform a weekend routine modem reset. Upon logging back in, I get a authentication error. Now that the authentication issue is resolved, I get this huge latency on the uncapped Axxess account. Anyone else with the same problem? :erm:
 
This is Axxess


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

Your average ping was 20ms
Your maximum ping was 174ms

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

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

Pinging 105.236.8.193 with 32 bytes of data:
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=174ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=92ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254

Ping statistics for 105.236.8.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 174ms, Average = 20ms
 
2014/05/02 17:10:40.70


This is Afrihost


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

Your average ping was 12ms
Your maximum ping was 22ms

Looking at your average ping, your line seems to be running perfectly :-)
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP :-(


Detailed Report

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

Pinging 105.236.8.193 with 32 bytes of data:
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=22ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=14ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=11ms TTL=254
Reply from 105.236.8.193: bytes=32 time=12ms TTL=254
Reply from 105.236.8.193: bytes=32 time=13ms TTL=254

Ping statistics for 105.236.8.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 22ms, Average = 12ms
 
2014/05/02 17:14:41.07

SNR Margin(Upstream) 6 dB
SNR Margin(Downstream) 6.0 dB
Line Attenuation(Upstream) 31.5 dB
Line Attenuation(Downstream) 63.5 dB
 
I also just called Axxess to downgrade my 4mb Uncapped Business account back to normal 4mb uncapped. I upgraded to business when they had the IPC issues. When on the website all network status is on green. When I spoke to the agent he informed me that he wouldn't downgrade if he was me because there are still some IPC issues in Cape Town and that the issue in his view has not been resolved yet. I asked him so why the F are they showing the network status a being green.

So it seems another month I have to pay R799 because these okes can't get it right.

Any ideas for alternative ISP's that don't have issues.?
 
http://mybroadband.co.za/vb/showthread.php/186156-Understanding-SNR-and-Attenuation-Rates

Extract:

"Heres is my table of comparisons
SNR:

6dB or below is very bad and will experience no synch or intermittent synch problems
7dB-10dB is fair but does not leave much room for variances in conditions
11dB-20dB is good with little or no sync problems
20dB-28dB is excellent
29dB or above is outstanding

Attenuation:

20dB and below is outstanding
20dB-30dB is excellent
30dB-40dB is very good
40dB-50dB is good
50dB-60dB is poor and may experience connectivity issues
60dB or above is bad and will experience connectivity issues

The following guide (distance vs. attenuation vs speed) gives you an guestimate what you can achieve:
<1km should be 23-24Mbit (nice speed, but doesn't it bug you that Telkom people walk through your bedroom?)
1.0km = 13.81dB = 23Mbit
1.5km = 20.7dB = 21Mbit
2.0km = 27.6dB = 18Mbit
2.5km = 34.5dB = 13Mbit
3.0km = 41.4dB = 8Mbit
3.5km = 48.3dB = 6Mbit
4.0km = 56dB = 4Mbit
4.5km = 62.1dB = 3Mbit
5.0km = 69dB = 2Mbit
>5.0km (you are pretty much poked --- sorry for you)"
 
Last edited:
Not only AXXESS! This is MWEB and Telkom on exchange (021)712-

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 540ms
Your maximum ping was 760ms

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 41.132.74.1 with 32 bytes of data:
Reply from 41.132.74.1: bytes=32 time=715ms TTL=254
Reply from 41.132.74.1: bytes=32 time=547ms TTL=254
Reply from 41.132.74.1: bytes=32 time=573ms TTL=254
Reply from 41.132.74.1: bytes=32 time=593ms TTL=254
Reply from 41.132.74.1: bytes=32 time=554ms TTL=254
Reply from 41.132.74.1: bytes=32 time=439ms TTL=254
Reply from 41.132.74.1: bytes=32 time=451ms TTL=254
Reply from 41.132.74.1: bytes=32 time=486ms TTL=254
Reply from 41.132.74.1: bytes=32 time=537ms TTL=254
Reply from 41.132.74.1: bytes=32 time=633ms TTL=254
Reply from 41.132.74.1: bytes=32 time=571ms TTL=254
Reply from 41.132.74.1: bytes=32 time=565ms TTL=254
Reply from 41.132.74.1: bytes=32 time=483ms TTL=254
Reply from 41.132.74.1: bytes=32 time=492ms TTL=254
Reply from 41.132.74.1: bytes=32 time=492ms TTL=254
Reply from 41.132.74.1: bytes=32 time=575ms TTL=254
Reply from 41.132.74.1: bytes=32 time=505ms TTL=254
Reply from 41.132.74.1: bytes=32 time=596ms TTL=254
Reply from 41.132.74.1: bytes=32 time=588ms TTL=254
Reply from 41.132.74.1: bytes=32 time=505ms TTL=254
Reply from 41.132.74.1: bytes=32 time=471ms TTL=254
Reply from 41.132.74.1: bytes=32 time=520ms TTL=254
Reply from 41.132.74.1: bytes=32 time=515ms TTL=254
Reply from 41.132.74.1: bytes=32 time=518ms TTL=254
Reply from 41.132.74.1: bytes=32 time=487ms TTL=254
Reply from 41.132.74.1: bytes=32 time=502ms TTL=254
Reply from 41.132.74.1: bytes=32 time=470ms TTL=254
Reply from 41.132.74.1: bytes=32 time=494ms TTL=254
Reply from 41.132.74.1: bytes=32 time=583ms TTL=254
Reply from 41.132.74.1: bytes=32 time=760ms TTL=254

Ping statistics for 41.132.74.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 439ms, Maximum = 760ms, Average = 540ms

2014/05/02 18:24:44.14
 
6db is definitely a bad line, you might experience worse issues with some providers but your hassles will never end if you don't AT LEAST double that figure.
 
My SNR and Line attenuation has been like that from the get go, 4 years now, something to do with length of copper winding around the suburbs toward the exchange even though Im less than 5kms from the exchange, as the crow flies. My Axxess account has always been alright with this SNR margin and Line attenuation, the problem is now only. I connect to a US server and can stand head to head with people who are virtually directly connected to the game box, where response is concerned. Something's not cooking with Axxess. WebAfrica and Afrihost capped accounts work like a charm.
 
internaut said:
My SNR and Line attenuation has been like that from the get go, 4 years now, something to do with length of copper winding around the suburbs toward the exchange even though Im less than 5kms from the exchange, as the crow flies. My Axxess account has always been alright with this SNR margin and Line attenuation, the problem is now only. I connect to a US server and can stand head to head with people who are virtually directly connected to the game box, where response is concerned. Something's not cooking with Axxess. WebAfrica and Afrihost capped accounts work like a charm.
Click to expand...

Test those accounts for an extended period of time as sometimes when you create a new session, it masks the problem but will gradually get worse the longer there is a connection.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X