- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hello yale k
first off ty for the reply
i was told i would get a call on friday long wait time due to thanksgiving
never got a reply. not even a text auto reply not cool
you ask for my area code ok even though its on file there for past 10 years
my zipcode is 03598
indoors and outdoors you ask if you read the prior post i said i was disabled and the phone dont move around alot
but the answer is indoors
current signal is
1x= -77dbm
4g= -95dbm
4 out of 5 bars on signal meter
you ask about real time performance,
performance is great when i can get to a page
my problem is getting to a page without it timing out after 2 to 5 reloads it will find the page and works fine once the server/html5 can figure out the route / hops to me.
happens on phone, tethered and hotspot
today seems a little better with the drop and reconnect issue. but is still there
here is todays test results
C:\Documents and Settings\Owner.YOUR-XHTR8HVC4P>tracert 74.125.224.147
Tracing route to lax02s20-in-f19.1e100.net [74.125.224.147]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms 192.168.43.1
2 * * * Request timed out.
3 38 ms 39 ms 39 ms 49.sub-69-83-13.myvzw.com [69.83.13.49]
4 157 ms 38 ms 38 ms 194.sub-69-83-13.myvzw.com [69.83.13.194]
5 155 ms 40 ms 39 ms 180.sub-69-83-2.myvzw.com [69.83.2.180]
6 * * * Request timed out.
7 158 ms 39 ms 39 ms 101.sub-66-174-17.myvzw.com [66.174.17.101]
8 532 ms 38 ms 39 ms TenGigE0-0-1-0.GW14.BOS4.ALTER.NET [152.179.2.97
]
9 58 ms 43 ms 36 ms TenGigE0-5-0-0.GW8.NYC4.ALTER.NET [152.63.21.65]
10 * 2158 ms 88 ms google-gw.customer.alter.net [152.179.72.62]
11 158 ms 39 ms 108 ms 209.85.255.68
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 237 ms 117 ms 125 ms 64.233.174.189
18 242 ms 118 ms 121 ms 209.85.250.251
19 115 ms 120 ms 119 ms lax02s20-in-f19.1e100.net [74.125.224.147]
Trace complete.
C:\Documents and Settings\Owner.YOUR-XHTR8HVC4P>
still hop 2, the phone fails like always
hop 2 ping test
C:\Documents and Settings\Owner.YOUR-XHTR8HVC4P>ping 10.166.21.208
Pinging 10.166.21.208 with 32 bytes of data:
Reply from 10.166.21.208: bytes=32 time=2ms TTL=64
Reply from 10.166.21.208: bytes=32 time=2ms TTL=64
Reply from 10.166.21.208: bytes=32 time=2ms TTL=64
Reply from 10.166.21.208: bytes=32 time=2ms TTL=64
Ping statistics for 10.166.21.208:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
the other hops like alter.net(aka) vzw 2000+ ms response time and the other timeouts are due to hop 2 issue
i think
the new html5 has a lot of loop back features for updating menu choices or getting connection type and speed for videos ext... i think this loopback call is whats timing out and the problems getting worst because more webpages are starting to use the html5 loopback
if the phone hop 2 is timing out then the html5 loopback will fail,i would think.
thanks for your time and trouble shooting this issue
ron seavey
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
oh and the yahoo vzw 1st tier guy i talked to on the phone last week put a bandwidth limit thinking i had a 50 dollar unlimited talk text data plan and now i have low bandwidth since that call like 100k or less download speeds.it was 6 to 10 mb till that call. last week
please remove the limited bandwidth as this is a grandfarthered unlimited data acct that costs 150 bucks with the 30 dollar extra hotspot.
high data usage is because
this line is medically necessary for my cardiac monitors and other medically related data going in real time and is causing problems now
thanks again
ron
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the higher data is your fault because we are having to re download failed downloads or a 1 meg webpage takes 5 times reloading to have it open that's a 400% increase just to get a webpage. my browsing and downloads have been about the same for the past 5 years.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the reply ronzos. The information that you provided will be proven to be a great help as we customize a solution for you. Rest assured as we are committed to your wireless happiness. I want to take a look at your data transmissions from your device. May I have you send a private message with your full name and mobile number so we can take a look for you internally. I'm looking forward to your reply.
ArnettH_VZW
Follow us on Twitter @VZWSupport
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no idea how to do that
all i see is your email is private you have 21232 points level diamond
hes today problem no 4g
1x= -76dbm
3g= -65dbm
booted phone
tried safe mode
PLEASE FIX THE TOWER
and please don't give me the default answer "buy a home repeater my signal is not weak" --its the tower
setting to global or lte same results
hers todays info
Tracing route to lax02s20-in-f19.1e100.net [74.125.224.147]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.43.1
2 * * * Request timed out.
3 260 ms 107 ms 85 ms 49.sub-69-83-15.myvzw.com [69.83.15.49]
4 265 ms 111 ms 88 ms 226.sub-69-83-15.myvzw.com [69.83.15.226]
5 64 ms 112 ms 85 ms 160.sub-69-83-3.myvzw.com [69.83.3.160]
6 * * * Request timed out.
7 83 ms 90 ms 86 ms 129.sub-66-174-18.myvzw.com [66.174.18.129]
8 265 ms 94 ms 94 ms ge5-0-3d0.cir1.nyc-ny.us.xo.net [209.220.16.13]
9 280 ms 97 ms 89 ms 209.220.16.110.ptr.us.xo.net [209.220.16.110]
10 267 ms 98 ms 136 ms 72.14.238.232
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 355 ms 172 ms 160 ms 64.233.174.189
17 336 ms 187 ms 153 ms 209.85.250.251
18 334 ms 164 ms 142 ms lax02s20-in-f19.1e100.net [74.125.224.147]
Trace complete.
again hop 2 times out and many others
i have seen a 33.6 dailup modem with better results than this.
all vzw uscellular straight talk users in the area are having no signal / weak signal / dropped signal / 3g intermittently on this tower.
you can find my acct info under user name (username)
For information on how to Direct Message, please visit: https://community.verizonwireless.com/docs/DOC-1011
Private info removed as required by the Terms of Service.
Message was edited by: Admin Moderator
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi tech guy Jim
i have done as you asked on the phone call today 12/28/13
set to lte / cdma
roaming set to allow access for all trips
the problem still here
here is today's info
Tracing route to lax02s20-in-f19.1e100.net [74.125.224.147]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.43.1
2 * * * Request timed out.
3 21 ms 39 ms 40 ms 49.sub-69-83-13.myvzw.com [69.83.13.49]
4 34 ms 38 ms 42 ms 194.sub-69-83-13.myvzw.com [69.83.13.194]
5 26 ms 38 ms 40 ms 180.sub-69-83-2.myvzw.com [69.83.2.180]
6 * * * Request timed out.
7 43 ms 39 ms 39 ms 101.sub-66-174-17.myvzw.com [66.174.17.101]
8 48 ms 36 ms 38 ms TenGigE0-0-1-0.GW14.BOS4.ALTER.NET [152.179.2.97
]
9 34 ms 41 ms 38 ms 0.ge-0-3-0.XL4.BOS4.ALTER.NET [152.63.17.134]
10 34 ms 43 ms 36 ms 0.xe-6-1-2.XT2.NYC4.ALTER.NET [152.63.3.90]
11 58 ms 57 ms 50 ms TenGigE0-5-4-0.GW8.NYC4.ALTER.NET [152.63.18.206
]
12 * 35 ms 48 ms google-gw.customer.alter.net [152.179.72.62]
13 42 ms 45 ms 42 ms 72.14.238.232
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 220 ms 120 ms 118 ms 64.233.174.193
20 128 ms 114 ms 116 ms 209.85.250.251
21 216 ms 107 ms 111 ms lax02s20-in-f19.1e100.net [74.125.224.147]
Trace complete.
still hop 2 fails
hop 2 the phone is 10.179.55.0
Pinging 10.179.55.0 with 32 bytes of data:
Reply from 10.179.55.0: bytes=32 time=3ms TTL=64
Reply from 10.179.55.0: bytes=32 time=2ms TTL=64
Reply from 10.179.55.0: bytes=32 time=2ms TTL=64
Reply from 10.179.55.0: bytes=32 time=1ms TTL=64
Ping statistics for 10.179.55.0:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms
again why is it timing out all the time ?
i really feel this is a Google problem with the android system not a Verizon or Motorola problem
these time outs are causing webpage timeout problems streaming is next to impossible and when i get a stream started it dies in a few mins i have to load and reload a standard webpage many time sometimes to get the full page
using large amounts of data just in re requested info and streams and re downloading failed downloads.
again i see the default reply was buy a home repeater for weak signal
this is not the case and has not been the case for the past few years its all worked fine this is a resent problem that started up a few months ago and is getting worst as time goes by
the pc hop 1 to phone hop 2 are internal ip addresses and has nothing to do with signal strength hop 3 and on yes but not hop 1 computer and hop 2 the phone
again the ticket was closed as weak signal buy repeater
open yet another ticket please and don't reply with default answers the screen in front of you says PLEASE !!!
MODERATOR do not delete any part of this post as none of this info is private and all ip info is static and changes on each boot and is needed by your tech guy tomorrow TY
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
well after about a dozen times i was able to log in
maybe go look at login at vzw to see how many failed attempts just to log in
this is getting old and i have been more then patient
please stop closing the tickets as this problem is not resolved
here lets try something a bit differant for todays test
lets try google ip as the test
here are the results
Tracing route to 64.233.160.0 over a maximum of 30 hops
1 2 ms 2 ms 2 ms 192.168.43.1
2 * * * Request timed out.
3 34 ms 35 ms 34 ms 49.sub-69-83-13.myvzw.com [69.83.13.49]
4 39 ms 25 ms 33 ms 194.sub-69-83-13.myvzw.com [69.83.13.194]
5 32 ms 38 ms 40 ms 180.sub-69-83-2.myvzw.com [69.83.2.180]
6 * * * Request timed out.
7 41 ms 23 ms 40 ms 101.sub-66-174-17.myvzw.com [66.174.17.101]
8 34 ms 37 ms 41 ms TenGigE0-0-1-0.GW14.BOS4.ALTER.NET [152.179.2.97
]
9 30 ms 31 ms 34 ms 0.ge-7-3-0.XL4.BOS4.ALTER.NET [152.63.17.81]
10 37 ms 48 ms 34 ms 0.ae1.XL4.NYC1.ALTER.NET [140.222.226.33]
11 51 ms 37 ms 46 ms 0.xe-9-3-0.GW13.NYC1.ALTER.NET [152.63.5.5]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
again hop 2 fails like always
heres the test for the ip you say to use see post above
Tracing route to lax02s20-in-f19.1e100.net [74.125.224.147]
over a maximum of 30 hops:
1 1 ms 2 ms 1 ms 192.168.43.1
2 * * * Request timed out.
3 157 ms 38 ms 46 ms 49.sub-69-83-13.myvzw.com [69.83.13.49]
4 145 ms 40 ms 46 ms 194.sub-69-83-13.myvzw.com [69.83.13.194]
5 169 ms 39 ms 48 ms 180.sub-69-83-2.myvzw.com [69.83.2.180]
6 * * * Request timed out.
7 36 ms 41 ms 46 ms 101.sub-66-174-17.myvzw.com [66.174.17.101]
8 50 ms * 42 ms TenGigE0-0-1-0.GW14.BOS4.ALTER.NET [152.179.2.97
]
9 176 ms 41 ms 39 ms 0.ge-0-3-0.XL4.BOS4.ALTER.NET [152.63.17.134]
10 166 ms 38 ms 38 ms 0.xe-6-1-2.XT2.NYC4.ALTER.NET [152.63.3.90]
11 160 ms 59 ms 59 ms TenGigE0-7-1-0.GW8.NYC4.ALTER.NET [152.63.21.125
]
12 157 ms 56 ms 41 ms google-gw.customer.alter.net [152.179.72.62]
13 49 ms 40 ms 39 ms 209.85.255.68
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 215 ms 117 ms 160 ms 64.233.174.189
20 237 ms 115 ms 124 ms 209.85.250.251
21 233 ms 118 ms 119 ms lax02s20-in-f19.1e100.net [74.125.224.147]
Trace complete.
hop 2 fails
also looks like hop 6 is failing most of the time think that's Manchester NH to Boston Mass
possibly a lvl3 problem?
oh todays test was on a vista home premime computer sp2
other computers used winxp sp3, vista sp2, win7, win8
4g- 74db at time of test.
dap10 seems to help with sites that support resume for downloads but will not help with html or streams
do you know of any software that will help with resume on streaming or html ? in the mean time
till you find and fix the problem!
pretty sad total failure just going to google on todays test
thanks for looking into this but can we PLEASE do more then look into this time.
perhaps fix the problem would be nice.
Ron
Private info removed as required by the Terms of Service.
Message was edited by: Admin Moderator
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
heres some speed test results from last year to this year
same phone same location same computer
take a look vzw
http://www.dslreports.com/testhistory/819809/7e605
from 10 mb downloads to 82k
please fix me please please please i beg
calling in to open yet another ticket
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
speed is much better past 24 hours Ty but
still having timeout issue
and failing hops still
streaming is a bit more stable past 24 hours only have to reload 2 or 3 times an hour.
keep poking at it
thanks Ron
- « Previous
-
- 1
- 2
- Next »