Observer

Re: Internet issues at night while gaming

Ground block is grounded to the telephone panel on the side of the house not to the electrical panel not sure if its new. Yeah it seems like its feeding to 11 houses.

So with this information how should i explain the situation because im not trying to get charged for a technican to come out.

Expert

Re: Internet issues at night while gaming

The cable,  telco and electrical services must be bonded to the same point . If not, there's a potential noise issue as well as lightning or electrical spike fire hazzard.

 

 What needs to be done is your neighbor on that splitters connections need to be cleaned up.

as I doubt twc will have the brains to add another 4 port tapoff on the pole and get rid of the splitters...

 

 If you have docs of the levels jumping around, that proves the point.

 

Spectrum Employee

Re: Internet issues at night while gaming

The tech telling you that you will be charged if we come out again for the same issue was sadly, a scare tactic. Techs are graded on if another tech has to "go back" to a house within a certain time frame from the last technician. The technicians have no say on if you are charged or not, and as long as you are not upgrading or downgrading a service, adding a cable box or some such, you should never be charged. Service related issues are done as a service call, and a service call never generates a charge. The RARE cases a service call turns into a charged call is if a customer has a botched up self-install job done like, trying to get cable or internet in a room of the house that didn't have it before and they put some splitters on and ran their own cabling, then we would charge to properly activate the outlet(s). Don't let that techs words scare you from calling for another tech. And honestly, I would call just to report that he said that to you so his supervisor can be made aware he is making those statements.


I am a Spectrum employee but my posts are my own thoughts and opinions
Expert

Re: Internet issues at night while gaming

Is that the last tap off block on the trunk line or does it feed to a further pole with some empty ports they could feed you from? An additional 100' of coax isn't going to kill you.

 

Observer

Re: Internet issues at night while gaming

It's not the last tap on the block. Sorry i completely forgot about this thread. I'm still dealing with the issue a tech came out the other day and checked the lines and drop and told me nothing is wrong, but clearly it is. I'm not sure what he did, but my levels have changed

ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 2561615000000 Hz2.2 dBmV37.6 dB17712
2LockedQAM 2563627000000 Hz1.9 dBmV38.2 dB0565
3LockedQAM 2564633000000 Hz2.4 dBmV37.9 dB01441
4LockedQAM 2565639000000 Hz2.1 dBmV38.2 dB01350
5LockedQAM 2567651000000 Hz2.8 dBmV38.9 dB14670
6LockedQAM 2568657000000 Hz2.6 dBmV37.9 dB121421
7LockedQAM 2569663000000 Hz3.2 dBmV38.6 dB101625
8LockedQAM 25610669000000 Hz2.7 dBmV38.2 dB531484

<tabindex=-1>Upstream Bonded Channels

ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedTDMA92560 Ksym/sec18500000 Hz44.5 dBmV
2LockedATDMA105120 Ksym/sec23300000 Hz45.8 dBmV
3LockedATDMA115120 Ksym/sec30600000 Hz46.3 dBmV
4LockedTDMA122560 Ksym/sec37000000 Hz47.3 dBmV

Current System Time: Wed May 11 22:06:17 2016




and now I'm having major issues with packet loss 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\ek>ping -n 30 twc.com

Pinging twc.com [71.74.183.9] with 32 bytes of data:
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=80ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=81ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=79ms TTL=51
Request timed out.
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=81ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=77ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51

Ping statistics for 71.74.183.9:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 81ms, Average = 74ms

C:\Users\ek>ping -n 30 twc.com

Pinging twc.com [71.74.183.9] with 32 bytes of data:
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=82ms TTL=51
Reply from 71.74.183.9: bytes=32 time=77ms TTL=51
Request timed out.
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=79ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=83ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=82ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51

Ping statistics for 71.74.183.9:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 83ms, Average = 74ms

C:\Users\ek>ping -n 30 twc.com

Pinging twc.com [71.74.183.9] with 32 bytes of data:
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=71ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=87ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=77ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=81ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=87ms TTL=51
Request timed out.
Reply from 71.74.183.9: bytes=32 time=81ms TTL=51
Reply from 71.74.183.9: bytes=32 time=80ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=82ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51

Ping statistics for 71.74.183.9:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 87ms, Average = 75ms

C:\Users\ek>ping -n 30 twc.com

Pinging twc.com [71.74.183.9] with 32 bytes of data:
Reply from 71.74.183.9: bytes=32 time=82ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=88ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Request timed out.
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Request timed out.
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=71ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Request timed out.
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=82ms TTL=51
Reply from 71.74.183.9: bytes=32 time=72ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=75ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=125ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=73ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51
Reply from 71.74.183.9: bytes=32 time=76ms TTL=51
Reply from 71.74.183.9: bytes=32 time=74ms TTL=51

Ping statistics for 71.74.183.9:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 125ms, Average = 76ms


I tried explaining to the tech, that i believe either the tap is bad, or possibly there is some type of ingress somewhere causing this issue, but he just told me to run a speedtest and said i was good to go and clearly didn't even fix the problem.

Expert

Re: Internet issues at night while gaming

I'd remove the 2 way splitter and run another drop to the pole to isolate what's going on next door.

 

And install another 4 ports on the pole. but i'm not TWC