Customers With Disabilities
  • RESIDENTIAL
  • BUSINESS

    Verizon Business Sites

  • WIRELESS
  • Services  
  • My Verizon  

    Email & Calls

    Check Email

    Verizon Visual 411

     

     

    Bill & Payment

    View Bill

    Pay Bill

    Pay Final Bill

    Manage Auto Pay

    Manage Paper Free Billing

    My Services

    Add or Change Services

    Renew or Change Bundle

    Review Account

    Manage My Internet

    Manage My Voice

     

  • Support  

    Community help

     

     

     

     

  • Watch FiOS  

    Watch thousands of your favorite TV shows and movies On Demand and Live. Rent or buy your favorites and watch them on any device. Or, check what's on tonight and program your DVR. You can do it all!

    Watch Free TV & Movies

     

     

    Rent or Buy

    Set your TV Viewing Experience

  • Trending  

    Check out this personalized, real-time feed featuring the latest content and entertainment from around the Web including new headlines, sports, entertainment and more.

     

     

     

     

     

    See what's Trending!

Reply
Contributor
pressureDrop
Posts: 2
Registered: ‎11-19-2013
0 Kudos
Accepted Solution

Ping times to router inconsistent and time out

Below is a log when pinging my router from a MacBook Air (2011) and then firing up AppleTV to stream a show.  I don't understand why the ping times just to the router are so high.  Eventually the show will buffer and then report an error ocurred.  I've tried all three channels 1,6,11.  Anyone else run into this type of problem?  I have the latest Actiontech router (red and black) and through support I've tried three routers in total all with the same result. I've also tried moving the router to different locations in the house and "reseated" the coax connections to no avail.  Phone, TV, and wired connections all seem to be working well, but all wireless devices (2 iphones, appleTV, 2 laptops all having issues).

 

64 bytes from 192.168.1.1: icmp_seq=1281 ttl=64 time=3.702 ms

64 bytes from 192.168.1.1: icmp_seq=1282 ttl=64 time=3.375 ms

64 bytes from 192.168.1.1: icmp_seq=1283 ttl=64 time=3.567 ms

64 bytes from 192.168.1.1: icmp_seq=1284 ttl=64 time=4.786 ms

64 bytes from 192.168.1.1: icmp_seq=1285 ttl=64 time=3.628 ms

64 bytes from 192.168.1.1: icmp_seq=1286 ttl=64 time=3.790 ms

64 bytes from 192.168.1.1: icmp_seq=1287 ttl=64 time=4.327 ms

64 bytes from 192.168.1.1: icmp_seq=1288 ttl=64 time=67.812 ms

64 bytes from 192.168.1.1: icmp_seq=1289 ttl=64 time=6.331 ms

64 bytes from 192.168.1.1: icmp_seq=1290 ttl=64 time=10.251 ms

64 bytes from 192.168.1.1: icmp_seq=1291 ttl=64 time=38.830 ms

64 bytes from 192.168.1.1: icmp_seq=1293 ttl=64 time=356.234 ms

Request timeout for icmp_seq 1294

Request timeout for icmp_seq 1295

Request timeout for icmp_seq 1296

64 bytes from 192.168.1.1: icmp_seq=1294 ttl=64 time=3430.752 ms

64 bytes from 192.168.1.1: icmp_seq=1295 ttl=64 time=2431.105 ms

64 bytes from 192.168.1.1: icmp_seq=1296 ttl=64 time=1430.679 ms

64 bytes from 192.168.1.1: icmp_seq=1297 ttl=64 time=430.490 ms

64 bytes from 192.168.1.1: icmp_seq=1298 ttl=64 time=388.085 ms

64 bytes from 192.168.1.1: icmp_seq=1299 ttl=64 time=228.999 ms

64 bytes from 192.168.1.1: icmp_seq=1300 ttl=64 time=1112.201 ms

64 bytes from 192.168.1.1: icmp_seq=1302 ttl=64 time=708.840 ms

64 bytes from 192.168.1.1: icmp_seq=1303 ttl=64 time=1802.629 ms

64 bytes from 192.168.1.1: icmp_seq=1304 ttl=64 time=802.700 ms

64 bytes from 192.168.1.1: icmp_seq=1305 ttl=64 time=1031.164 ms

64 bytes from 192.168.1.1: icmp_seq=1306 ttl=64 time=1055.803 ms

64 bytes from 192.168.1.1: icmp_seq=1307 ttl=64 time=341.111 ms

64 bytes from 192.168.1.1: icmp_seq=1308 ttl=64 time=896.705 ms

Request timeout for icmp_seq 1311

Request timeout for icmp_seq 1312

64 bytes from 192.168.1.1: icmp_seq=1312 ttl=64 time=1891.501 ms

Request timeout for icmp_seq 1314

Request timeout for icmp_seq 1315

Request timeout for icmp_seq 1316

64 bytes from 192.168.1.1: icmp_seq=1313 ttl=64 time=4803.134 ms

Request timeout for icmp_seq 1318

64 bytes from 192.168.1.1: icmp_seq=1314 ttl=64 time=5007.117 ms

64 bytes from 192.168.1.1: icmp_seq=1315 ttl=64 time=5844.100 ms

64 bytes from 192.168.1.1: icmp_seq=1316 ttl=64 time=4843.650 ms

Request timeout for icmp_seq 1322

Request timeout for icmp_seq 1323

Request timeout for icmp_seq 1324

Request timeout for icmp_seq 1325

Request timeout for icmp_seq 1326

Request timeout for icmp_seq 1327

Request timeout for icmp_seq 1328

64 bytes from 192.168.1.1: icmp_seq=1317 ttl=64 time=12273.609 ms

Request timeout for icmp_seq 1330

Request timeout for icmp_seq 1331

Request timeout for icmp_seq 1332

64 bytes from 192.168.1.1: icmp_seq=1318 ttl=64 time=15021.241 ms

Request timeout for icmp_seq 1334

64 bytes from 192.168.1.1: icmp_seq=1319 ttl=64 time=16265.572 ms

64 bytes from 192.168.1.1: icmp_seq=1320 ttl=64 time=15267.633 ms

64 bytes from 192.168.1.1: icmp_seq=1321 ttl=64 time=15092.940 ms

64 bytes from 192.168.1.1: icmp_seq=1322 ttl=64 time=14092.629 ms

64 bytes from 192.168.1.1: icmp_seq=1323 ttl=64 time=13091.566 ms

64 bytes from 192.168.1.1: icmp_seq=1324 ttl=64 time=12090.316 ms

Contributor
pressureDrop
Posts: 2
Registered: ‎11-19-2013
0 Kudos

Re: Ping times to router inconsistent and time out

I think I may have finally figured out the root cause! It's a set of wireless headphones (TurtleBeach EarForce X41).  

 

The receiver for the headphones sits next to the TV and the AppleTV is in a cabinet below both of them.  When the receiver is plugged in AND the AppleTV is streaming content or I am attempting a high bandwidth download on any of the other devices the WIFI ping times to the router shoot up over 1000ms and occassionally timeout.  When I unplug the receiver the ping times return to a more acceptable (though not great) 3-8ms range.  I'm not sure why the XBox 360 isn't affected since thats in the same cabinet/room as the AppleTV and my laptop but I've been able to play games on that relatively trouble free.  Perhaps its Apple's Bonjour protocol which is more succeptable to the RF interference of the headphones?  In any case, I was reliably able to prove out that the headphones were at least some part of the issue by pinging the router from my mac while plugging and unplugging the receiver for the headphones.  Below are the results.  Can you tell when the receiver was on/off (hint: the ping log starts when its off and ends off and I plugged it in 3 times)?

 

$ ping 192.168.1.1 | tee ping.txt

PING 192.168.1.1 (192.168.1.1): 56 data bytes

64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=7.398 ms

64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=8.331 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=6.373 ms

64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=5.561 ms

64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=3.953 ms

64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=5.154 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=4.899 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.157 ms

64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=6.543 ms

64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.281 ms

64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.744 ms

64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=4.447 ms

64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=49.492 ms

64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=326.097 ms

64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=328.170 ms

64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=490.890 ms

Request timeout for icmp_seq 16

64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1444.173 ms

64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=682.149 ms

64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1468.538 ms

64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=467.483 ms

64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=72.789 ms

64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=528.337 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=8.260 ms

64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=3.316 ms

64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=5.043 ms

64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=3.384 ms

64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=3.384 ms

64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=4.667 ms

64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=1.092 ms

64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=1.292 ms

64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=13.867 ms

64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=3.321 ms

64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=9.205 ms

64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=3.678 ms

64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=39.144 ms

Request timeout for icmp_seq 36

64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=2067.310 ms

64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=1066.216 ms

64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=67.672 ms

64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=2146.863 ms

64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=1145.767 ms

64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=145.362 ms

64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=359.188 ms

64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=1630.737 ms

64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=629.884 ms

64 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=1625.214 ms

64 bytes from 192.168.1.1: icmp_seq=45 ttl=64 time=958.188 ms

64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=829.962 ms

64 bytes from 192.168.1.1: icmp_seq=47 ttl=64 time=1008.010 ms

64 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=7.801 ms

64 bytes from 192.168.1.1: icmp_seq=49 ttl=64 time=3.735 ms

64 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=1.156 ms

64 bytes from 192.168.1.1: icmp_seq=51 ttl=64 time=4.345 ms

64 bytes from 192.168.1.1: icmp_seq=52 ttl=64 time=4.019 ms

64 bytes from 192.168.1.1: icmp_seq=53 ttl=64 time=9.302 ms

64 bytes from 192.168.1.1: icmp_seq=54 ttl=64 time=22.385 ms

64 bytes from 192.168.1.1: icmp_seq=55 ttl=64 time=12.103 ms

64 bytes from 192.168.1.1: icmp_seq=56 ttl=64 time=4.834 ms

64 bytes from 192.168.1.1: icmp_seq=57 ttl=64 time=6.645 ms

64 bytes from 192.168.1.1: icmp_seq=58 ttl=64 time=14.584 ms

64 bytes from 192.168.1.1: icmp_seq=59 ttl=64 time=6.850 ms

64 bytes from 192.168.1.1: icmp_seq=60 ttl=64 time=290.746 ms

64 bytes from 192.168.1.1: icmp_seq=61 ttl=64 time=2508.208 ms

64 bytes from 192.168.1.1: icmp_seq=62 ttl=64 time=1538.850 ms

64 bytes from 192.168.1.1: icmp_seq=63 ttl=64 time=547.558 ms

64 bytes from 192.168.1.1: icmp_seq=64 ttl=64 time=1190.224 ms

64 bytes from 192.168.1.1: icmp_seq=65 ttl=64 time=189.123 ms

64 bytes from 192.168.1.1: icmp_seq=66 ttl=64 time=113.995 ms

64 bytes from 192.168.1.1: icmp_seq=67 ttl=64 time=158.522 ms

64 bytes from 192.168.1.1: icmp_seq=68 ttl=64 time=1241.926 ms

64 bytes from 192.168.1.1: icmp_seq=69 ttl=64 time=240.829 ms

64 bytes from 192.168.1.1: icmp_seq=70 ttl=64 time=1657.784 ms

64 bytes from 192.168.1.1: icmp_seq=71 ttl=64 time=656.727 ms

64 bytes from 192.168.1.1: icmp_seq=72 ttl=64 time=1004.473 ms

64 bytes from 192.168.1.1: icmp_seq=73 ttl=64 time=4.233 ms

64 bytes from 192.168.1.1: icmp_seq=74 ttl=64 time=6.961 ms

64 bytes from 192.168.1.1: icmp_seq=75 ttl=64 time=4.025 ms

64 bytes from 192.168.1.1: icmp_seq=76 ttl=64 time=9.646 ms

64 bytes from 192.168.1.1: icmp_seq=77 ttl=64 time=6.553 ms

64 bytes from 192.168.1.1: icmp_seq=78 ttl=64 time=6.700 ms

64 bytes from 192.168.1.1: icmp_seq=79 ttl=64 time=13.679 ms

64 bytes from 192.168.1.1: icmp_seq=80 ttl=64 time=3.802 ms

64 bytes from 192.168.1.1: icmp_seq=81 ttl=64 time=4.157 ms

64 bytes from 192.168.1.1: icmp_seq=82 ttl=64 time=4.075 ms

64 bytes from 192.168.1.1: icmp_seq=83 ttl=64 time=3.835 ms

64 bytes from 192.168.1.1: icmp_seq=84 ttl=64 time=5.332 ms

64 bytes from 192.168.1.1: icmp_seq=85 ttl=64 time=4.194 ms

 

Solution: Plug the receiver for my wireless headphones in only when I am using them (with the XBox 360).

 

Might be a good question to add to the Verizon support troubleshooting guide.  "Have you recently added any wireless RF devices like headphones?"

 

Hope this might help someone else.

 

 

My Verizon

Support Tools

Watch FiOS

Trending

  • Visual 411