Verizon wireless really needs a way to easily contact tech support with problems. When I call all I get is "your in a high traffic area".......
I think packet loss in our area is way out of specs!
DATA FROM PINGS AND TRACERT 02MAR18 2030 TO 2130
APN VZWINTERNET IP 100.87.139.158 GATE 100.87.139.157
Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\>ping google.com -n 50
Pinging google.com [216.58.194.46] with 32 bytes of data:
Ping statistics for 216.58.194.46:
Packets: Sent = 50, Received = 43, Lost = 7 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 391ms, Average = 78ms
C:\>ping google.com -n 50
Pinging google.com [216.58.194.46] with 32 bytes of data:
Packets: Sent = 50, Received = 35, Lost = 15 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 312ms, Average = 74ms
C:\>ping yahoo.com -n 50
Pinging yahoo.com [98.139.180.180] with 32 bytes of data:
Ping statistics for 98.139.180.180:
Packets: Sent = 50, Received = 39, Lost = 11 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 367ms, Average = 114ms
C:\>ping bing.com -n 50
Pinging bing.com [204.79.197.200] with 32 bytes of data:
Ping statistics for 204.79.197.200:
Packets: Sent = 50, Received = 43, Lost = 7 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 401ms, Average = 79ms
C:\>ping bing.com -n 50
Pinging bing.com [204.79.197.200] with 32 bytes of data:
Ping statistics for 204.79.197.200:
Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 331ms, Average = 80ms
C:\>ping google.com -n 50
Pinging google.com [216.58.194.110] with 32 bytes of data:
Ping statistics for 216.58.194.110:
Packets: Sent = 50, Received = 37, Lost = 13 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 374ms, Average = 95ms
C:\>ping google.com -n 50
Pinging google.com [216.58.194.110] with 32 bytes of data:
Ping statistics for 216.58.194.110:
Packets: Sent = 50, Received = 39, Lost = 11 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 400ms, Average = 100ms
C:\>ping google.com -n 50
Pinging google.com [216.58.194.110] with 32 bytes of data:
Ping statistics for 216.58.194.110:
Packets: Sent = 50, Received = 37, Lost = 13 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 181ms, Average = 67ms
C:\>ping yahoo.com -n 50
Pinging yahoo.com [206.190.39.42] with 32 bytes of data:
Ping statistics for 206.190.39.42:
Packets: Sent = 50, Received = 36, Lost = 14 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 245ms, Average = 123ms
C:\>ping yahoo.com -n 50
Ping statistics for 206.190.39.42:
Packets: Sent = 50, Received = 32, Lost = 18 (36% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 363ms, Average = 136ms
*****************************************************************************
C:\>tracert yahoo.com
Tracing route to yahoo.com [206.190.39.42]
over a maximum of 30 hops:
1 * 3 ms 1 ms 26.250.125.1
2 * * * Request timed out.
3 Benlinco-1.Benlinco [26.250.125.248] reports: Destination host unreachable.
Trace complete.
C:\>tracert yahoo.com
Tracing route to yahoo.com [206.190.39.42]
over a maximum of 30 hops:
1 42 ms 1 ms <1 ms 26.250.125.1
2 * * * Request timed out.
3 49 ms 80 ms 78 ms 145.sub-66-174-43.myvzw.com [66.174.43.145]
4 84 ms 66 ms 76 ms 82.sub-69-83-106.myvzw.com [69.83.106.82]
5 54 ms 40 ms 38 ms 67.sub-69-83-106.myvzw.com [69.83.106.67]
6 69 ms 51 ms 66 ms 2.sub-69-83-107.myvzw.com [69.83.107.2]
7 107 ms 116 ms * 70.sub-69-83-98.myvzw.com [69.83.98.70]
8 41 ms 79 ms 77 ms 112.sub-69-83-96.myvzw.com [69.83.96.112]
9 71 ms 81 ms 84 ms 112.sub-69-83-96.myvzw.com [69.83.96.112]
10 55 ms 54 ms 87 ms 69.sub-69-83-96.myvzw.com [69.83.96.69]
11 63 ms 38 ms * et-1-1-2.GW18.DFW9.ALTER.NET [157.130.131.9]
12 92 ms 111 ms 117 ms 0.ge-5-2-0.XL3.SEA1.ALTER.NET [140.222.229.175]
13 86 ms 126 ms 102 ms 0.xe-10-2-0.GW2.SEA1.ALTER.NET [152.63.105.118]
14 * 120 ms 119 ms verizon.com.customer.alter.net [157.130.186.250]
15 84 ms 119 ms 106 ms ae-7.pat2.gqb.yahoo.com [216.115.101.109]
16 141 ms 104 ms 120 ms et-18-1-0.msr1.gq1.yahoo.com [66.196.67.103]
17 114 ms 119 ms 135 ms et-0-0-0.clr1-a-gdc.gq1.yahoo.com [67.195.37.69]
18 112 ms 142 ms 121 ms et-18-1.fab5-1-gdc.gq1.yahoo.com [67.195.1.235]
19 170 ms 152 ms 166 ms po-13.bas2-7-prd.gq1.yahoo.com [206.190.32.37]
20 133 ms 113 ms 100 ms media-router-fp1.prod.media.vip.gq1.yahoo.com [206.190.39.42]
Trace complete.
C:\>
Looks like your chasing your tail on hop 8 and 9!
