Pings going over 1000ms just before 8pm

A

Adenoid Hynkel

Executive Member
Joined
Oct 15, 2008
Messages
6,154
Reaction score
1,794
Location
:)
Latency going over 1000ms at times

Im sitttin on a 4096 line.

App im about 2.5km away from the exchange. My SNR is about 44-46 (high) line Att is about 13. I know the values arent great.

During the day I get normal pings. average of 34-45 on local servers. Every night, I mean every nigtht just before 8pm my ping starts becoming unstable and rises over 1000ms at times. But mostly between 200-600ms. At about 10ish it calms down and is back to normal.

No one else using the line besides me. Nothing runnign in the backgorund.
Telkom tells me there is nothing wrong.

How do I get a telkom technician out here to test the line? I really do not understand why it only happens in those times.

I tested 3 diff accounts. MWEB, afrihost and telkom unshaped. Ping stays the same at those times.

Any Ideas?

Thanks
 
Last edited:
I think there's more issues with Seacom, I know Mweb has been having issues with the international link all day!

I'm hoping for it all to be sorted out by tomorrow. :(
 
blogbytes said:
During the day I get normal pings. average of 34-45 on local servers. Every night, I mean every nigtht just before 8pm my ping starts becoming unstable and rises over 1000ms at times. But mostly between 200-600ms. At about 10ish it calms down and is back to normal.
Click to expand...

Are you saying local ping goes dreadfully high? That wouldn't be affected by Seacom or any other international cable, this is a problem with the local connection. Can you get other people in your area to confirm this? Since it doesn't seem to be a problem generally, I'm thinking it might be a problem with your local exchange, or some other part of your area-specific network, or possibly your line itself.
 
Been struggling with MTN the last few days (multiple sites in Bfn) - even local sites load erratically. Back home my WebAfrica ADSL is also not as snappy as I am used to.

???
 
blogbytes said:
Im sitttin on a 4096 line.

App im about 2.5km away from the exchange. My SNR is about 44-46 (high) line Att is about 13. I know the values arent great.

During the day I get normal pings. average of 34-45 on local servers. Every night, I mean every nigtht just before 8pm my ping starts becoming unstable and rises over 1000ms at times. But mostly between 200-600ms. At about 10ish it calms down and is back to normal.

No one else using the line besides me. Nothing runnign in the backgorund.
Telkom tells me there is nothing wrong.

How do I get a telkom technician out here to test the line? I really do not understand why it only happens in those times.

I tested 3 diff accounts. MWEB, afrihost and telkom unshaped. Ping stays the same at those times.

Any Ideas?

Thanks
Click to expand...

Sounds like your exchange is also running over capacity like mine in Langenhoven Park in Bloemfontein. No matter which account I use, my download speed and ping remains the same for all of my accounts. I can really see a change in browsing and download speeds from 7pm till about 10pm. I don't suffer from such a large latencies though, however, I'll put all my money on an overloaded exchange in your case.
 
Hi,

I had the same issue for more than a year..no matter what I tried, Telkom could not address the problem.
Until recently....another fault made them connect me to an older/different DSLAM in the exchange and now the problem seems to be gone. My take on it is that the DSLAM (not the port), cannot handle all the activity.

Sad thing is, to get Telkom to fix it for you is near to impossible. Good luck.
blogbytes said:
Im sitttin on a 4096 line.

App im about 2.5km away from the exchange. My SNR is about 44-46 (high) line Att is about 13. I know the values arent great.

During the day I get normal pings. average of 34-45 on local servers. Every night, I mean every nigtht just before 8pm my ping starts becoming unstable and rises over 1000ms at times. But mostly between 200-600ms. At about 10ish it calms down and is back to normal.

No one else using the line besides me. Nothing runnign in the backgorund.
Telkom tells me there is nothing wrong.

How do I get a telkom technician out here to test the line? I really do not understand why it only happens in those times.

I tested 3 diff accounts. MWEB, afrihost and telkom unshaped. Ping stays the same at those times.

Any Ideas?

Thanks
Click to expand...
 
Same problem here - Durban. Telkom technician been to my place about 5 times this week, still no luck.
 
Telkom tech was here sat morning, ran a couple of tests with his toy he had with him. "All looks good" he mentioned. I asked him too please go checkout the dslam and exchange, which he did. No issues found by him.
How do I take this further? There is def a fault somewhere. It is getting worse. I can call myslef lucky if my latency was below 500 today.

I will go knock on doors in my complex and area to ask people if they have adsl and if they have issues so they can report that to telkom.
It takes me 1min to open up mybb website.

Reply from 196.43.22.222: bytes=32 time=1077ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1141ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1224ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1330ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1427ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1281ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1395ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1510ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1543ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1457ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1445ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1461ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1596ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1465ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1441ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1357ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1438ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1661ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1520ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1025ms TTL=245
Reply from 196.43.22.222: bytes=32 time=827ms TTL=245
Reply from 196.43.22.222: bytes=32 time=733ms TTL=245
Reply from 196.43.22.222: bytes=32 time=878ms TTL=245
Reply from 196.43.22.222: bytes=32 time=967ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1037ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1160ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1234ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1056ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1078ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1098ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1136ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1202ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1342ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1448ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1451ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1533ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1528ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1595ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1593ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1564ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1611ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=245
 
Ping is simply a message being sent to a destination host, which then gets echoed back. The idea behind ping (icmp protocol) is to either check if the destination host is online OR to get the latency/response time that it took for the packet to travel to the destination host and back. Anything less than 50ms is pretty decent for ADSL and less than 20ms is outstanding. To play FPS (first person shooters) you need a latency of 100ms or less, otherwise you'll struggle a lot!

blogbytes, perhaps your DSLAM is saturated with traffic from other people downloading. It sounded pretty much like what happened to mbvdl http://mybroadband.co.za/vb/showthr...r-client-is-using-it-all-quot&highlight=600gb
 
Blogbytes, I have exactly the same problem! Although its not limited to 8PM, It seems to be completely random. Anyway, what's interesting is that you are in the Somerset West Area - I am in Strand. Something must be up with the exchange.
 
This can also be caused by an exchange that's just literally overloaded, meaning too many people trying to access the Internet at the same time.

We have a 20:1 contention ratio in SA, so if there's 400 users on the exchange and more than 20 try to Access it at the same time, your pings will start going higher.
BUT: With a 4mb line, I'm also thinking crossed line.
 
@ruknroller
I moved to Gordons Bay recently. I did not experience this issue at my old home.

Another tech actually had a look at the Exchange and dslam. They have told they will pput me on a diff dslam port, which they havent, as they could not find any issues. Again I am at square 1. I have told them its only at certain times, mostly at night between 7-10pm.
The techie said he needs to speak to his Supervisor to get a techie out at night - which I think aint going to happen. Its getting worse and worse. It started in those hours I mentioned, but now I'm getting it during the day as well. Its very frustrating, specially if Telkom cant find the fault.

@Frag, what is a crossed line?

Guys look what Im going through - I recorded my pings on Sunday - http://upload.blogbytes.co.za/uploads/pings.txt
Other days look very similiar.
 
Update: They have switched me to a new port on a different DSLAM and the high pings are history :D
 
blogbytes said:
Telkom tech was here sat morning, ran a couple of tests with his toy he had with him. "All looks good" he mentioned. I asked him too please go checkout the dslam and exchange, which he did. No issues found by him.
How do I take this further? There is def a fault somewhere. It is getting worse. I can call myslef lucky if my latency was below 500 today.

I will go knock on doors in my complex and area to ask people if they have adsl and if they have issues so they can report that to telkom.
It takes me 1min to open up mybb website.

Reply from 196.43.22.222: bytes=32 time=1077ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1141ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1224ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1330ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1427ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1281ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1395ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1510ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1543ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1457ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1445ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1461ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1596ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1465ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1441ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1357ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1438ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1661ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1520ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1025ms TTL=245
Reply from 196.43.22.222: bytes=32 time=827ms TTL=245
Reply from 196.43.22.222: bytes=32 time=733ms TTL=245
Reply from 196.43.22.222: bytes=32 time=878ms TTL=245
Reply from 196.43.22.222: bytes=32 time=967ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1037ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1160ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1234ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1056ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1078ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1098ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1136ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1202ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1342ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1448ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1451ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1533ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1528ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1595ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1593ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1564ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1611ms TTL=245
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=245
Click to expand...

well that is extremely slow pings my 384Kbps is 28ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X