US Cable Support > Time Warner Internet Services > [TWC] packet loss / service degraded - amp in rockaway park, ny

reply to kilrathi

Re: [TWC] packet loss / service degraded - amp in rockaway park,

reply to kilrathi
»mcs2.reliablehosting.com/myspeed···ype=voip

Oh and I spoke with t3 and they also logging me and since thursday when noise was fixed upstream snr showing lowest 27 where before it would drop every night to 20.... however error rate on upstream and only upstream is back on today, and at same time the 2 higher modulation channels keep showing either 64QAM or 16QAM where during day its always 64QAM, t3 guy said that most likely channels are hopping on upstream and may cause this but he sees error rate between modem and plant on the upstream.

I actually have 2 lines ran 1 from each pole/tap on street and tried both same problem right now.

»www.pingtest.net/result/66813391.png

It may not sound bad when its 2-3% packet loss but for gaming wise its horrible especially since its upstream only sometimes you feel like you not even controlling anything further I normally broadcast and cast games for tourneys and other vs games but with this issue the broadcasts keeps cutting off and/or dropping frames.

I may have to give up broadcasting and shoutcasting games which is a shame because it was fun and I actually received some hardware from some tournament sponsors in return.

I may have to also go to lower tw package which is rr turbo 20/2 which uses docsis 2 modem and does not use upstream channel bonding to get rid of the packet loss so I can at least use voice communication and play games without constant problems.

I will call customer rep again tomorrow and maybe the plant tech to see if anything else can be done.

Only thing I have to find out whether rr turbo uses the 2.560 Msym/sec 16qam or 5.120 Msym/sec 64qam channel for upstream, I hope it is the lower modulation one as based on my observations for past 2 months and ever since upstream channel bonding kicked in those higher modulation ones at least here have packet loss issues. Few times I was locked only on the lower modulation channel or when all other T4 time out and when I was locked at only the 16QAM channel for a night there was 0 packet loss problems.

Yes speeds would be big let down from what I am getting now but at least I could game and voice comm without constant problems and packet loss, I could still cast games after I record them and upload them after the fact.

reply to kilrathi
sigh I guess there must be something else causing this packet loss maybe its simply occuring on the node itself since 10pm last night constant packet loss on the upstreadm, now its 5am and its still going:



morning 9 am and now I actually noticed when I traceroute on 5th hop of tw it actually stalls (and no i have name resolution off) and currently packet loss is actually getting worse:

reply to kilrathi
Not sure whats going on but having hard time browsing and some voip tests or packet loss tests simply freeze.

In addition since last evening the modem is having constant spam of T3 errors (No Ranging Response received - T3 time-out).....

Now friday and saturday night and day everything was fine(after noise was fixed and upstream snr corrected) but this thing that started sunday evening could be maybe something else that just occured maybe on tw network here regionally or node.... not sure whats going on but I hope some time at least a week can go without problems...

Test Type: Voice over IP
Downstream Jitter: 0.5ms
Downstream Loss: 0 %
Upstream Jitter: 0.2ms
Upstream Loss: 5.2 %

It seems this maybe differnet problem than before because its going on into the day now..... before with the noise days were clean but this is going on and on...

Oh and signal levels etc are all same as for past 2 months except upstream snr now never drops below 27 since thursday night fixes(reading provided by t3 techs). So more and more points to something going on in tw network/plant/node or misconfiguration.....

reply to kilrathi

negative, t3 escalation center told me if I downgraded I would have to use docsis2 modem and only 1 channel is used, I asked him last night.

Further, I noticed this:

Red 7/23/2012 2:25:39 PM THE 5700 BLOCK OF SHORE FRONT PKY THE 100 BLOCK OF BEACH 59TH ST THE 5700 BLOCK OF SHORE FRONT PKWY under mainteance page, this is not far from here so I truly hope this is related because today all day I have t3 errors and packet loss, before today I didnt have issues like this during the day.

I spoke with client relations today and old issue is considered closed since back then packet loss was result of upstream snr being out of range, since that was fixed everything was great for 2 days. However this new problem is happening constantly since last night 9pm EST and its been happening entire day, upstream snr is within range(above 27) and all other signal levels are perfect and not changed. Thus bascially this is considered a *new issue* even though its affecting me in similar way a constant upstream packet loss.

Really really dissapointed that I only had 2 days of good service before another problem kicked in. The modem had about 200 or more T3 timeout errors through the day as well....

you maybe right is just an idea I have because frankly for 2 months now all I had is problems and now I had 2 days of good net was happy and now again a problem except now its constantly not just during nighttime.... currently packet loss is constant 2-7% and t3 timeout errors constantly, it took me 2 months to get plant tech to fix previous problem with upstream snr but this looks like new problem and i pray is something they are aware of because if I have to wait another 2 months to fix this problem then this is gotta be one of the worst isp experiences I could think of.

reply to kilrathi
That issue in far rockaway shows closed now but the packet loss continues, entire day no change.

reply to kilrathi
Yesterday jul 23 at 8pm est t3 time out errors stopped and had no issues with packet loss at all, so far entire day today been great. I wasnt aware but plant techs came tonight to let me know they were dispatched to look at my issue, however I had to tell them since yesterday everything is great after whatever was done in far rockaway.

reply to kilrathi
I am on the ropes, 1 day everything is great and then next day today constant packet loss again on the upstream....

I spoke with plant tech again and they will try to dispatch someone again with the next shift, only thing I can think of right now is that when one specific channel is used with upstream it has issue while another when its used it doesnt and that could explain the packet loss. Signal levels are all perfect including upstream snr, this is simply something else thats going on maybe even at the node itself.

Constant 4-10% packet loss right now.

There were bunch of T3 timeout errors occuring at around 8pm and seems that time packet loss galore..... and they wonder why I dont call to report the issue is resolved.... well because I have to actually wait few days to be sure and bam same thing different day.



I am actually having problem to browse the internet some pages just stall/timeout.

reply to kilrathi

2 lower modulation channels no packet loss

reply to kilrathi
I spoke with client relations again and plant tech supposed to investigate again but I have low expectations at this point, I assume its very difficult issue where some ingress/egress such as microreflections is occuring thats affecting the higher modulation/symbol rate upstream channels thats causing packet loss. Maybe my upstream tx is too close to noise level (about 37-8db without splitter) and this basically makes those modulations not possible to work without excessive error rate. At this point I am trying to get them to push custom config for me so that I only use the 1/2 lower modulation channels if thats at all possible because clearly with those lower modulation channels there is no issue. There is no need for 50/5 package to use the higher modulation upstrem channels at all and its only causing problem for me. Its basically a sign of tw pushing tech thats not needed for current packages when the system/wiring here is not ready for it. Modem lost dhcp renew ability and had to reboot 12 hours after I did the 2 channel t4 trick. But at this point I will have to keep doing this if I want to have packet loss connection. Sad but this is reality.

Be nice if they're able to get the higher modulation to work as it makes for more upstream capacity, but you gotta do what you gotta do, I'd say until Timer Warner is able to get the plant cleaned up and fixed a bit more.

reply to kilrathi
Post erased.

reply to kilrathi
Correct, however the issue thats causing problem is they using higher modulation upstream channels when there is simply no need for it for even the 5mbit upstream pacakge, and thus its just really bad decision on their part. Basically my current solution is to reboot the modem after 12 hours when ip lease expires and then hook up extra splitters once modem boots and then switch one to 8db so that it causes 2 higher modulation channels to t4 and then quickly switch back so the 2 lower modulation channels stay working, this way modem will not try to properly renew its ip but for 12 hours i can use it without packet loss at all, i been doing this for past few days since this is only way i can have clean connection. I told client rep and plant tech the situation which clearly indicates the packet loss occurs on the higher modulation channels, maybe just 1 of them or both that I am not sure of. What I am sure of is when only those 2 lower modulation channels are used for upstream i have no issues at all.

when I do this the default channel which is one of the 64qam that i force to t4 I believe is responsible for communicating with cmts for stuff like renewing lease etc... so basically I have no way to keep this connection past 12 hours, thats the only downside.

Every time I reboot though I always check and there is always some upstream packet loss when higher modulation channels are locked(all 4). When only 16qam channels are used there is no packet loss on upstream. Its quite clear.

reply to kilrathi
I been using my method of T4 timing out atdma channels upstream and keeping only the 16qam tdma channels working and even got it to work without having to reboot every 12 hours, this way I been having 0 problems no packet loss at all and max speeds just fine for past 2 days. I will continue to do this until I cannot or they let me know somethin was done about ingress on higher modulation upstream channels.

reply to kilrathi
So something happened tonight where I can no longer block out the 2 higher modulation 64QAM upstream channels and only use the 2 16QAM with my methods, I thought maybe by now they fixed the problems but nope still packet loss on the upstream and its constant at regular intervals when doing voip tests. TW simply doesnt seem to care about some kind of ingress on the line here that simply makes 64qam upstream have packet loss here, I will be attempting to keep rebooting modem adding splitters back and forth and try to have only the 16qam upstream channels working, for 9 days I had it that way and had no issues at all, but once I am forced to use 64qam upstream channels thats when packet loss strikes. I spoke to plant techs 2 weeks ago I was told they will call me with regards if its possible to send custom config for me to only use those but never got call back and never got call back about the issue either. I been quiet since I had it working my way for over a week but it seems now I am unable to do this anymore(for past 2 hours).

What a bummer, i'm sorry to hear that man