Rockaway Park, NY
|reply to kilrathi |
Re: [TWC] packet loss / service degraded - amp in rockaway park,
I think I am pretty sure the issue lies in bad upstream power level/rf impairment. I remember always having T3 timeout errors in modem logs but never really thought of that much. Well it turns out those erorrs have to do with upstream problems and modem trying to correct rf/power levels. Considering my current problems deal with upstream packet loss only this fits.
Further, this problem is now occuring every night 9pm till 5-6 am so its possible combined with already weak power level on upstream path streelights at night could be emitting a lot of ingress into the upstream on the pole itself causing problem being more apparent in those hours. Plus you add the fact the problem became horrible ever since upstream bonding came into effect that could explain why ever since that occured problems magnified.
Tech will be here tomorrow, I will have him run brand new wire/connectors on the house and hopefully also have him take readings on the pole where my line is connected and maybe hook it up into different spot, I am lost as what else could be done to fix this.
-> Streetlights went ON around this time:
-> Middle of the night
->as soon as Streetlights went OFF things got pretty clean:
could be just coincidence who knows, either way i have upstream signal/power issues, I really wish I could see signals on this wideband modem because earlier in the week every time I called escalation center they told me signals are great but last night lady told me my upstream power levels/signals were bad yet entire week I had problems occur in similar fashion.
I spoke with escalation team right after and looking at the modem he did confirm that on 3 out of 4 upstream channels bonded power level is out of spec.
client relations person told me engineering team will be out here sometime today or tomorrow to correct upstream power noise/problem I am holding hope they can fix the problem.
so far friday 930pm est and problem is still present as the errors already starting as usual to grow at this hour: