LATENCY!!!

[Gordon_R]

I was away from my desk, so I didn't notice the drop in latency. It's glaringly obvious on the PingPlotter graph between 20h10 and 20h25. Probably some ISP went down briefly (like on the weekend). Back to 'normal' again...

http://www.imagehost.co.za/image-6B8B_4CC5D22C.gif

 

[_Jack_]

wait, i just thought of something, quite a few telkom users (including me ) are not getting capped this month for some reason so they are downloading as much as they can... could that have anything to do with the congestion?

 

[dagwood4455]

how is this ... i pay for a 4Meg line but i get 0,26Mbs !!! I have phoned Telkom for weeks now and they just talk in circles ... I hate the bastards

 

[Anthro]

C:\Users\*>tracert [url]www.google.com[/url]

Tracing route to [url]www.l.google.com[/url] [155.232.240.19]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     *        *        *     Request timed out.
  3   720 ms   730 ms   305 ms  tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
  4   329 ms   342 ms   374 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5   486 ms   593 ms   619 ms  tengig-0-0-0-0-11.vic-up-2.mweb.co.za [196.22.16
9.226]
  6   686 ms   408 ms   237 ms  jx2621-1-S1-AP.mweb.net [196.22.163.5]
  7   643 ms   272 ms   286 ms  tenet.jinx.net.za [198.32.142.33]
  8   237 ms   362 ms   415 ms  cpt1-t101-bfn1-t100.net.tenet.ac.za [155.232.6.3
8]
  9   333 ms   271 ms   440 ms  gc-cpt-bree-g21-23-19.uni.net.za [155.232.240.19
]
Trace complete.

C:\Users\*>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     *        *        *     Request timed out.
  3   740 ms   707 ms   624 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   477 ms   453 ms   517 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5   404 ms   429 ms   288 ms  196.22.169.62
  6   518 ms   566 ms   728 ms  196.22.169.42
  7   300 ms   316 ms   113 ms  196.41.144.36
  8    57 ms   118 ms   134 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

 

[Will@MWEB]

i just got off the phone with telkom and their latest answer is that my port is being shaped by my isp. they say mweb are no longer just shaping my account, but the whole port itself. if i change isp for more than a day then the port should get reset and pings return to normal. i dont know if thats true, but i think its worth a shot. if i do find mweb was at fault all along im going to be ****ing angry and will cancel my contract immediately. but this could just be another excuse from telkom to buy them more time.

how many of you pay line rental to your isp instead of to telkom? and how many of you download a lot? telkom guy said mwebs original "uncapped quota" (an oxymoron if i ever heard one) is 70GB/month and i know for fact i use a lot more than that. now to test if thats affecting the quality of my line.

@Will, care to comment?

Hi Peter

Apologies I missed this comment earlier. I'm sorry but that's just downright ridiculous. We don't have any control over the DSLAM ports other than the ability to do port resets and stabilize line speeds for our all inclusive customers. Also we have no control over which DSLAMS our customers are on, so could you even begin to imagine the logistical nightmare you would have in implementing that type of shaping if it were even possible. If you just spoke to someone in the call centre I can chalk this up to simple ignorance. If you spoke to someone more senior please tell me that you have the contact details and PM them to me so that I can take this up with someone tomorrow.

 

[Lounger]

Been doing this for most of my clients in the area as its all of them who have the same problem.
Keep logging the faults as this makes them look at it quicker.
They are looking into it but they will not acknowledge anything to you as a customer as they cannot comit to how long it will take to be fixed. and when loggin the fault put emphasis on the fact that you DO NOT want to be downgraded on your line coz they will do it automatically.

Won't they just charge you the unnecessary callout fee?

 

[peTerp00n]

i dont know if observatory has been mentioned yet, but my friend is having the same problem. his line is laggy from 8am-5pm though... http://i.imgur.com/q3I3S.png if i remember correctly thats how mine started, and it just got worse and worse over time. i predict his graph will look as bad as the rondebosch one in a month or two if nothing is done.

@will i just spoke to the guy who answered the phone. it was definitely not ignorance... it was a blatant lie. i argued with him. told him "im sure thats not possible", but he was adamant and he started quoting my usage saying that i am being shaped because i am downloading so much.

i am spamming telkom with fault logs... im on about my 5th one now. but from now on i am going to insist i speak to someone more senior. i am even considering paying a visit to clareinch exchange (if that is even possible) to speak to someone in person. i dont like being taken for a fool.

 

[jpmonster]

Yeah i was playing Some TF2 and at exactly 8:25/30 around there, my Ping went to 40ms and stayed that way for about 10min, It felt so awesome Then it went back to 180ms.

Weird?

 

[Anthro]

C:\Users\*>tracert news.mweb.co.za

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     *        *        *     Request timed out.
  3  1163 ms   982 ms   398 ms  tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
  4   584 ms   637 ms   617 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5   827 ms  1088 ms  1067 ms  tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
  6  1239 ms  1007 ms   841 ms  news.mweb.co.za [196.28.78.229]

Trace complete.

C:\Users\*>tracert smtp.mweb.co.za

Tracing route to smtp.mweb.co.za [196.28.80.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     *        *        *     Request timed out.
  3   952 ms   882 ms   854 ms  tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
  4   892 ms   858 ms   855 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   691 ms  1107 ms  1202 ms  tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
  6  1177 ms  1834 ms   603 ms  relay.smp.mweb.co.za [196.28.80.20]

Trace complete.

 

[teRRRier]

Nobody move, don't even breathe - it's back to normal at the moment. One of those steep dives (usually followed by a steep climb though)

 

[acidrain]

And its dipped again... hold onto your seats guys, this is gonna get bumpy

 

[raVid]

*holds breath*

 

[WAJeff]

C:\Users\*>tracert news.mweb.co.za

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     *        *        *     Request timed out.
  3  1163 ms   982 ms   398 ms  tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
  4   584 ms   637 ms   617 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5   827 ms  1088 ms  1067 ms  tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
  6  1239 ms  1007 ms   841 ms  news.mweb.co.za [196.28.78.229]

Trace complete.

C:\Users\*>tracert smtp.mweb.co.za

Tracing route to smtp.mweb.co.za [196.28.80.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2     *        *        *     Request timed out.
  3   952 ms   882 ms   854 ms  tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
  4   892 ms   858 ms   855 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   691 ms  1107 ms  1202 ms  tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
  6  1177 ms  1834 ms   603 ms  relay.smp.mweb.co.za [196.28.80.20]

Trace complete.

Heya Anthro!
A friendly face I know in this thread

By the looks of things, thats off an Mweb account yes? If you have a Web Africa account, would you mind posting up or PM'ing me some details please?

 

[acidrain]

Definitely doing better than previously at this time, and seems to be holding *touch wood*

 

[ajules]

Ok just spoke to Telkom and they have finally rectified the problem.Apparently the latency switch was on high latency iso low latency.They picked up the error after someone called PeterPoon sent them 4.3 million e-mails today.
The tea lady has been instructed to use a different switch when doing the vacuuming from now on.

You can flame me if you want but after endless staring at the PingPlotter graph I think I am finally losing my marbles.
In any case this depressing thread need some humour injected into it!

 

[Johand]

Its funny - definitely the best line conditions this side of twelve in a while:

I wonder whether the person who downloads the internet went to bed early tonight. Pretty sure he will press the resume button tomorrow :-(

 

[Johand]

Ok just spoke to Telkom and they have finally rectified the problem.Apparently the latency switch was on high latency iso low latency.They picked up the error after someone called PeterPoon sent them 4.3 million e-mails today.
The tea lady has been instructed to use a different switch when doing the vacuuming from now on.

You can flame me if you want but after endless staring at the PingPlotter graph I think I am finally losing my marbles.
In any case this depressing thread need some humour injected into it!

Don't be ridiculous - there is no such thing as a latency switch. The router didn't have enough RAM - so they obviously just downloaded more RAM for the router - http://www.downloadmoreram.com.

 

[jacquesm]

Same issues here in Rondebosch - thank goodness I'm not alone! A technician is coming round today to check my line, as the operator at Telkom told me the line between my house and the exchange is borked, but your guys' reasoning here seems much more plausable

Rondebosch is where the ESR in question is living. Clareinch, Wynberg, etc. all terminate on the Rondebosch ESR2. Somewhere between Rondebosch and Barrack Street the problem with the latency exists - most likely Telkom have not enough capacity between Rondebosch and Barrack Street - there was some mention here that there will be a maintenance window for Telkom to bump the circuit speed.

 

[jacquesm]

Hi Peter

Apologies I missed this comment earlier. I'm sorry but that's just downright ridiculous. We don't have any control over the DSLAM ports other than the ability to do port resets and stabilize line speeds for our all inclusive customers. Also we have no control over which DSLAMS our customers are on, so could you even begin to imagine the logistical nightmare you would have in implementing that type of shaping if it were even possible. If you just spoke to someone in the call centre I can chalk this up to simple ignorance. If you spoke to someone more senior please tell me that you have the contact details and PM them to me so that I can take this up with someone tomorrow.

You are aware you can pass some radius attributes to the cisco gear of telkom and tell it to rate limit to 64Kbit/s and some other stuff like only allow users to visit www.mweb.co.za and query your dns servers.

 

[Anthro]

C:\Users\*>tracert jinx.net.za

Tracing route to jinx.net.za [160.124.112.27]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2   905 ms   707 ms   569 ms  41-133-124-1.dsl.mweb.co.za [41.133.124.1]
  3   674 ms   509 ms   798 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   353 ms   206 ms   426 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   195 ms   411 ms   450 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   505 ms   618 ms   640 ms  g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
  7   571 ms   852 ms   836 ms  posix.jinx.net.za [198.32.142.22]
  8   649 ms   966 ms   757 ms  hostnet.posix.co.za [160.124.2.21]
  9   535 ms   560 ms   794 ms  honey.hivemind.net [160.124.112.27]

Trace complete.

C:\Users\*>tracert cinx.net.za

Tracing route to cinx.net.za [160.124.112.27]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  unknown [192.168.1.1]
  2   575 ms   439 ms   312 ms  41-133-124-1.dsl.mweb.co.za [41.133.124.1]
  3   643 ms  1044 ms  1107 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4  1127 ms   782 ms   529 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   942 ms   514 ms   474 ms  tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
  6   437 ms   366 ms   311 ms  g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
  7   902 ms   753 ms  1121 ms  posix.jinx.net.za [198.32.142.22]
  8   804 ms  1162 ms  1078 ms  hostnet.posix.co.za [160.124.2.21]
  9  1274 ms  1223 ms  1136 ms  honey.hivemind.net [160.124.112.27]

Trace complete.

C:\Users\*>tracert news.mweb.co.za

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
^C
C:\Users\XBearer>tracert news.mweb.co.za

Tracing route to news.mweb.co.za [196.28.78.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2   825 ms   587 ms  1118 ms  41-133-124-1.dsl.mweb.co.za [41.133.124.1]
  3   874 ms   828 ms   842 ms  tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
  4   872 ms   645 ms   736 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5   482 ms   254 ms   202 ms  tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
  6   431 ms   908 ms   291 ms  news.mweb.co.za [196.28.78.229]

C:\Users\*>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2   601 ms   580 ms   385 ms  41-133-124-1.dsl.mweb.co.za [41.133.124.1]
  3   315 ms   326 ms   244 ms  tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
  4   226 ms   353 ms   373 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5   211 ms   262 ms   369 ms  196.22.169.62
  6   684 ms   999 ms  1102 ms  196.22.169.42
  7   402 ms   313 ms   964 ms  196.41.144.36
  8  1158 ms  1315 ms  1161 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\*>tracert smtp.mweb.co.za

Tracing route to smtp.mweb.co.za [196.28.80.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2   836 ms   765 ms   959 ms  41-133-124-1.dsl.mweb.co.za [41.133.124.1]
  3   864 ms  1009 ms   659 ms  tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
  4   705 ms   763 ms   690 ms  vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
  5   810 ms   843 ms   724 ms  tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
  6   722 ms   777 ms   778 ms  relay.smp.mweb.co.za [196.28.80.20]

Trace complete.