PIERRE VAN RYNEVELD ADSL Users please assist

[kobusvdv]

I have been having the same problem and it seem even worst the last week or 2.

http://www.speedtest.net/result/1010338149.png

1 minute later

http://www.speedtest.net/result/1010340229.png

This was actually not to bad a result, just an hour before I did these tests I could not get the Ping below 700ms and the download speed over 0.6MB/s.

The problem with monopolies is you can do absolutely nothing. I have spoken to dozens of people on the helpdesk but they just test the line and close the call because the line IS UP.
Is there no help out there or even a promise that things may improve. I also spoke to them in July and the where apparently busy upgrading the exchange for 10mb/s lines. Wonder how long it takes………

EXTREMELY FRUSTRATED!!!

 

[kobusvdv]

4MB DSL line with telkom as SP. Also an unshaped account with Axxess. Pierre van Ryneveld needs help. Will the problem be solved when they eventually upgrade to 10MB lines? I wonder.

 

[ichigo]

10 meg lines make it worse

 

[EricBusy]

Since my previous post I moved to Afrihost.

Pinging www.afrihost.com [196.38.88.139] with 32 bytes of data:
Reply from 196.38.88.139: bytes=32 time=93ms TTL=53
Reply from 196.38.88.139: bytes=32 time=98ms TTL=53
Reply from 196.38.88.139: bytes=32 time=100ms TTL=53
Reply from 196.38.88.139: bytes=32 time=134ms TTL=53
Reply from 196.38.88.139: bytes=32 time=75ms TTL=53
Reply from 196.38.88.139: bytes=32 time=110ms TTL=53
Reply from 196.38.88.139: bytes=32 time=115ms TTL=53
Request timed out.
Reply from 196.38.88.139: bytes=32 time=127ms TTL=53
Reply from 196.38.88.139: bytes=32 time=37ms TTL=53
Reply from 196.38.88.139: bytes=32 time=70ms TTL=53
Reply from 196.38.88.139: bytes=32 time=159ms TTL=53
Reply from 196.38.88.139: bytes=32 time=122ms TTL=53
Reply from 196.38.88.139: bytes=32 time=92ms TTL=53
Reply from 196.38.88.139: bytes=32 time=66ms TTL=53
Reply from 196.38.88.139: bytes=32 time=75ms TTL=53
Request timed out.
Reply from 196.38.88.139: bytes=32 time=99ms TTL=53
Reply from 196.38.88.139: bytes=32 time=113ms TTL=53
Reply from 196.38.88.139: bytes=32 time=80ms TTL=53
Reply from 196.38.88.139: bytes=32 time=84ms TTL=53
Reply from 196.38.88.139: bytes=32 time=70ms TTL=53
Reply from 196.38.88.139: bytes=32 time=170ms TTL=53
Reply from 196.38.88.139: bytes=32 time=91ms TTL=53
Reply from 196.38.88.139: bytes=32 time=85ms TTL=53
Reply from 196.38.88.139: bytes=32 time=124ms TTL=53
Reply from 196.38.88.139: bytes=32 time=160ms TTL=53
Reply from 196.38.88.139: bytes=32 time=99ms TTL=53
Reply from 196.38.88.139: bytes=32 time=87ms TTL=53
Reply from 196.38.88.139: bytes=32 time=81ms TTL=53
Reply from 196.38.88.139: bytes=32 time=129ms TTL=53
Reply from 196.38.88.139: bytes=32 time=59ms TTL=53
Reply from 196.38.88.139: bytes=32 time=93ms TTL=53
Reply from 196.38.88.139: bytes=32 time=108ms TTL=53
Reply from 196.38.88.139: bytes=32 time=49ms TTL=53
Reply from 196.38.88.139: bytes=32 time=137ms TTL=53
Reply from 196.38.88.139: bytes=32 time=168ms TTL=53
Reply from 196.38.88.139: bytes=32 time=66ms TTL=53
Reply from 196.38.88.139: bytes=32 time=76ms TTL=53
Request timed out.
Reply from 196.38.88.139: bytes=32 time=69ms TTL=53
Reply from 196.38.88.139: bytes=32 time=65ms TTL=53
Reply from 196.38.88.139: bytes=32 time=45ms TTL=53
Reply from 196.38.88.139: bytes=32 time=107ms TTL=53
Reply from 196.38.88.139: bytes=32 time=80ms TTL=53
Reply from 196.38.88.139: bytes=32 time=91ms TTL=53
Reply from 196.38.88.139: bytes=32 time=120ms TTL=53
Reply from 196.38.88.139: bytes=32 time=106ms TTL=53
Reply from 196.38.88.139: bytes=32 time=76ms TTL=53
Reply from 196.38.88.139: bytes=32 time=36ms TTL=53
Reply from 196.38.88.139: bytes=32 time=78ms TTL=53
Reply from 196.38.88.139: bytes=32 time=56ms TTL=53
Reply from 196.38.88.139: bytes=32 time=76ms TTL=53
Reply from 196.38.88.139: bytes=32 time=116ms TTL=53
Reply from 196.38.88.139: bytes=32 time=56ms TTL=53
Reply from 196.38.88.139: bytes=32 time=113ms TTL=53
Reply from 196.38.88.139: bytes=32 time=134ms TTL=53
Reply from 196.38.88.139: bytes=32 time=52ms TTL=53
Reply from 196.38.88.139: bytes=32 time=87ms TTL=53
Reply from 196.38.88.139: bytes=32 time=131ms TTL=53
Reply from 196.38.88.139: bytes=32 time=132ms TTL=53
Reply from 196.38.88.139: bytes=32 time=67ms TTL=53
Reply from 196.38.88.139: bytes=32 time=66ms TTL=53
Reply from 196.38.88.139: bytes=32 time=76ms TTL=53
Reply from 196.38.88.139: bytes=32 time=58ms TTL=53

Ping statistics for 196.38.88.139:
Packets: Sent = 65, Received = 62, Lost = 3 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 170ms, Average = 93ms

 

[kobusvdv]

Can we lay a complaint at ICASA? Telkom are selling services that they cannot deliver and taking our money. If there is no intent on solving this issue from their side surely they are in breach of .... something... maybe they should rather then admit that there are no 4BM/s andsl available in the neighborhood. Are there 512 or 384 users that have the same problem or is this limited to the 4mb/s links?

 

[phoneJunky]

I am on 384 at the moment and it is working fine. I want to upgrade to a 4Meg line but now I am not so sure..

 

[Mr.Jax]

Most of the weekend and last night latency was pretty good...excellent actually, but tonight its gone totally bonkers again and will probably stay this way for the rest of the week and weekend and only settle once most people's caps run out or they pace so that it lasts the month.
The pattern is pretty much: bad in the beginning of the month, gets better towards the middle of the month, then towards the end it gets really bad again and usually on the last few days of the months its pretty good.

 

[kobusvdv]

Most of the weekend and last night latency was pretty good...excellent actually, but tonight its gone totally bonkers again and will probably stay this way for the rest of the week and weekend and only settle once most people's caps run out or they pace so that it lasts the month.
The pattern is pretty much: bad in the beginning of the month, gets better towards the middle of the month, then towards the end it gets really bad again and usually on the last few days of the months its pretty good.

I tried playing tonight but it is absolutely useless. I can just as well cancel the line and get 3G. It can only be better. Last night was good as you mentioned I wonder if it has something to do with the heavy weather. I think most people switch their PC's off during thunderstorms.

 

[Mr.Jax]

I tried playing tonight but it is absolutely useless. I can just as well cancel the line and get 3G. It can only be better. Last night was good as you mentioned I wonder if it has something to do with the heavy weather. I think most people switch their PC's off during thunderstorms.

Agreed, people probably disconnect their phone lines with thunderstorms. I don't lol, I want lightning to hit my line hard, very hard

 

[phoneJunky]

Yes, I actually only put back my phone line yesterday because I left it out because of the thunder. Where in PvR do you guys experience this problem, is it the whole PvR because my connection is ok. but then again I only have 384, will upgrade my line at the end of the month.

 

[Mr.Jax]

Yes, I actually only put back my phone line yesterday because I left it out because of the thunder. Where in PvR do you guys experience this problem, is it the whole PvR because my connection is ok. but then again I only have 384, will upgrade my line at the end of the month.

Hard to say if its the whole area, only 4MB or all.
If latency is not a concern, you won't notice the issue, especially on 384. Upgrade to 4MB is still worth it (if you don't play online games), you will still get much higher speeds. E.g. I still get around 1Mbps throughput when the latency is bad.

 

[phoneJunky]

I only play dota online, and the 384 is more than enough for that. I have to wait a day to get a 350Meg file though, so hopefully the upgrade will be good. But then again, won't I degrade your line-speed if I also upgrade?

 

[Mr.Jax]

I don't think one more 4MB line will make much of a difference, its one of several 100 existing lines, so it would be like adding e.g. 1% (or less, or more, just guessing here) more traffic on the back-haul.

 

[Mr.Jax]

Really bad again tonight....sigh...*censored*.....

 

[phoneJunky]

okay, this weekend I experienced some trouble with my line. This was the first time I had really bad lag for online gaming. I had to quit the game to let the other people play without any frustrations.

 

[Mr.Jax]

Interesting.

For a change I didn't have a single lagging moment this whole weekend. Had a perfect ping in-game Fri-Sun...hope it stays that way.

 

[jellievis]

http://www.speedtest.net/result/1022377205.png

This is tonight on my 4 Meg line.

 

[phoneJunky]

I would still love that speed, if that is the worst you get. I am upgrading my line at the end of this month

 

[Mr.Jax]

Last night I had a pristine connection; latency was excellent.

This seems to be dslam specific (you and I aren't on the same dslam)

 

[Mr.Jax]

It's been almost a week of excellent latency.
Seen a lot of telkom activity at the exchange too.

Been here before, but, cautiously optimistic that something was fixed.