These were from today. Financial District in SF. (300 Ft from Verizon store). This is starting to be the standard speeds I've been getting. A majority of the tests I've been doing don't even complete. If they do, I have a full grown beard by the time they're done.
@t2mobile Wow!!! Simply WOW! I didn't think it could get any worse at my location, but you've proved me wrong on just how bad it can get.
Yes indeed, Verizon is providing to their premium paying customers Grade F- service as seen above.
Account retention specialists, care to comment??? Your silence says volumes.
Thanks for your continued status updates c1ph3r2u. What make and model device are you using? What is your main zip code of use? Have you reported these concerns to us previously via another support channel? We definitely want to ensure we investigate as thoroughly as possible.
Asistencia de VZW
Follow Us on Twitter@VZWSupport
- Thank you for checking in. Yes, I have an unresolved NBR ticket submitted on July 19th. Ticket followup has been non-existent aside from nicholasb_vzw giving brief assistance.
Personally, I'm using a Galaxy Nexus device and zip code 95131 is especially problematic for Verizon customers. Please do understand however that my colleagues and friends are seeing all of the reported issues listed on this thread on their various Samsung, Motorola, and Apple phones. It's not a single phone type of issue, it's a network provider issue.
I've marked your account as "Followed" in case you need any additional information to provide follow up details.
Thank you c1ph3r2u. I've reached out to the representatives who you've worked with previously so we can ensure you get the follow up you've been expecting. We'll be following up with you later today and appreciate your continued patience.
Please follow us on Twitter @vzwsupport
zip code: 94105 on a new droid maxx
Speedtest results after 6 failed runs (communication issues)
ping: 531, 782, failed, failed, failed, 825
down: 21kbps, failed, failed, failed, failed, failed
up: failed, failed, failed, failed, failed, failed
I can say, at 7 am my speeds are noticeably better, will try a speedtest tomorrow morning i suppose.
Update on the issues in San Jose near 1st Street and Trimble Rd:
A Samsung R&D center where phone development occurs at Orchard Parkway and Plumeria Dr. is flooding the local cell tower with data and the tower is completely oversubscribed during business hours. Verizon has confirmed this as the root cause at this location and has started the process of getting an additional tower installed. The ETA for this new cell tower to come online is unknown; ever tried to get a permit from the city, county, and state? SWAG would be in the ballpark of 1 year, but there are too many variables to commit on that length of time.
In a nutshell, this issue will remain for at least another year.
Want to feel a bit better? Be thankful you're not on Sprint. Only a few of my colleagues are on Sprint and they are getting ping times of 1.4 seconds, 40kbps down, 8kpbs up. Is Samsung R&D mostly creating issues for CDMA phones?
Colleagues with T-Mobile service on Samsung GS4 devices are getting ping < 100ms, ~3Mbps down, ~1Mbps up at this location. They typically see 20+Mbps at their residences. I'm still trying to find some colleagues with AT&T service to test their speeds. I'll update this thread later if I do find that it's a CDMA vs. GSM issue.
Proactive note for Verizon:
I'd be surprised if Samsung did not move its phone R&D center to the new gigantic campus that it is building at 1st St. and Tasman Rd. in San Jose. I would strongly recommend that Verizon prepares extra capacity for that location as Cisco has a very substantial employee base there who will be significantly impacted by the Samsung phone R&D group. (Hint: Thanks to SEO, this thread has the top hit in Google for query "Verizon Silicon Valley" and Cisco employees will know you were warned in advance)
Other Silicon Valley locations with issues I've reported:
has created support tickets for all the locations I've listed in this thread. Verizon has an internal DB containing locations with known issues in coverage. Locations I've listed are already in their DB and they are aware of them. Fix ETA is unknown.
informed me that since I have good service at my home address where my Verizon bill is sent, I am not eligible for having an early termination fee waived. My work and home are in the same city, but it doesn't matter to Verizon's policies...
I'm simply waiting for some new Android phones to be released on other carries and I'll be leaving Verizon shortly thereafter. Their failure to build out an adequate 4G network in the San Francisco Bay Area is quite appalling and I can no longer justify paying a premium for such poor quality of coverage. The nation's largest carrier is over subscribed in urban areas, future customers should exercise caution.
Side note to : Try Password Safe (http://sourceforge.net/projects/passwordsafe/) or KeePass (http://sourceforge.net/projects/keepass/) to make your password management easier and more secure. Clients for both programs are available on Windows, Linux, Mac OSX, Android, and iOS.
a few tests at my location
7:59am 3491k down 1545 up ping 57ms
8:42am 312k down 1554 up ping 74ms
8:47am 207k down 129k up ping 116ms
8:49am 136k down 94k up ping 289ms
as it creeps ever closer to 9am here in San Francisco, Verizon service creeps ever closer to unusable.
Outage report - Dead zone, voice calls are dropped and no data connectivity.
San Jose, zip code 95136
Hwy 87 near Branham Ln overpass
I am seeing this same issue and unfortunately it's near my home. Verizon, when are you going to fix this?