dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
5
caa100
join:2004-04-02
Annandale, VA

caa100

Member

Re: [VA] Frequent, Short Disruptions in Connectivity

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.

Sample Ping:
=========
64 bytes from 173.194.73.104: icmp_seq=10 ttl=48 time=27.490 ms
64 bytes from 173.194.73.104: icmp_seq=11 ttl=48 time=24.427 ms
64 bytes from 173.194.73.104: 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 173.194.73.104: icmp_seq=13 ttl=48 time=7530.234 ms
64 bytes from 173.194.73.104: icmp_seq=16 ttl=48 time=4528.144 ms
64 bytes from 173.194.73.104: icmp_seq=17 ttl=48 time=3527.409 ms
64 bytes from 173.194.73.104: icmp_seq=18 ttl=48 time=2526.372 ms
64 bytes from 173.194.73.104: icmp_seq=14 ttl=48 time=6530.137 ms
64 bytes from 173.194.73.104: icmp_seq=15 ttl=48 time=5529.069 ms
64 bytes from 173.194.73.104: icmp_seq=20 ttl=48 time=524.995 ms
64 bytes from 173.194.73.104: icmp_seq=19 ttl=48 time=1535.224 ms
caa100

1 edit

caa100

Member

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....
caa100

caa100

Member

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.