odogCable Centric Vendor BiasedPremium,VIPReviews:
|reply to caa100 |
Re: [VA] Frequent, Short Disruptions in Connectivity
Open up a few command prompt windows. Setup perpetual pings to the following IPs
the internal gateway IP of the Apple router
the public default gateway IP(the gateway of your WAN IP in the router)
then after seeing the issue, connect one computer directly to the modem and try it.
Hey, just noticed a Cox truck across the street. My neighbor has been getting disruptions during phone calls, about every 15 minutes. (Sound familiar?)
This is their second truck roll, a tech yesterday told them it was fixed.
Just relayed that info to the tech who visited me today. His supervisor is going to come out and check our node tomorrow.
odogCable Centric Vendor BiasedPremium,VIP
The every 13 minutes is the weird thing. Normally plant abnormalities don't do stuff like that.
I suppose it could be ingress from someone on your node, but every 13 minutes on the dot?
Agreed, thats why I was open to the idea that Carbonite or something on my computers may be causing it. But we've ruled all that out.
Just talked to the technician who was working across the street. He's also set up a visit to our node. His theory is the same as yours -- that there is a house somewhere on our node where some sort of home appliance is introducing interference back out to our node.
Thanks for your interest, I will certainly post back whatever happens.
Just an update in case anyone with similar issues is following this thread.
Every 12-13 minutes, for a period of about 6 seconds, my latency spikes as high as 8 seconds. Pings will come back, if wait time is set long enough. (See example below.)
The field service contractor returned to my neighborhood 2 days after the first visit, and replicated the problem by connecting a modem direct to the node at the pedestal in our area.
They have finally agreed to escalate this as it is clearly a problem outside the house. (Something they promised to do 2 days ago.)
As it is the day before christmas, they said not to expect any activity until Wednesday.
64 bytes from 126.96.36.199: icmp_seq=10 ttl=48 time=27.490 ms
64 bytes from 188.8.131.52: icmp_seq=11 ttl=48 time=24.427 ms
64 bytes from 184.108.40.206: icmp_seq=12 ttl=48 time=23.951 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
64 bytes from 220.127.116.11: icmp_seq=13 ttl=48 time=7530.234 ms
64 bytes from 18.104.22.168: icmp_seq=16 ttl=48 time=4528.144 ms
64 bytes from 22.214.171.124: icmp_seq=17 ttl=48 time=3527.409 ms
64 bytes from 126.96.36.199: icmp_seq=18 ttl=48 time=2526.372 ms
64 bytes from 188.8.131.52: icmp_seq=14 ttl=48 time=6530.137 ms
64 bytes from 184.108.40.206: icmp_seq=15 ttl=48 time=5529.069 ms
64 bytes from 220.127.116.11: icmp_seq=20 ttl=48 time=524.995 ms
64 bytes from 18.104.22.168: icmp_seq=19 ttl=48 time=1535.224 ms
Field supervisor duplicated problem at the tap, 3 days ago. Multiple calls to Cox, multiple promises that someone will call me back, still no progress.
Neighbor experiencing same runaround....
Wife calling Verizon....
Problem was fixed sometime yesterday. What a relief.
Thanks to those on this thread who offered help and suggestions.
To those with similar issues: stay at it, keep calling, and dont accept "this is normal" for an answer.