# Verizon coverage blows

**URL:** <https://forums.speedlife.net/t/verizon-coverage-blows/195782>\
**Category:** PittSpeed Off Topic\
**Created:** [February 27, 2008, 8:00pm UTC](https://forums.speedlife.net/t/verizon-coverage-blows/195782 "2008-02-27T20:00:04Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![beat90tsi](https://avatars.discourse-cdn.com/v4/letter/b/43a26b/32.png) [@beat90tsi](https://forums.speedlife.net/u/beat90tsi)\
**Post date:** [February 28, 2008, 8:07am UTC](https://forums.speedlife.net/t/verizon-coverage-blows/195782/11 "2008-02-28T08:07:26Z")

</div>

> [@Saab Turbo X (56k warn)](https://forums.speedlife.net/t/saab-turbo-x-56k-warn/35168/3):
>
> what you just described is a hardware problem. It’s like having a rod blow out the side of your engine and then bitching about how your car won’t run because the gasoline you’re running sucks.

I don’t see how that’s the case. First, I don’t see how you know it’s a hardware problem, the Verizon employees can’t even figure it out. Secondly, I’m blaming Verizon, it could be their software, hardware, or some fag with glasses who forgot to travel to Phoenix with a broadband card. I don’t really know or care what the real problem was, but for a week while in the 5th largest city in the U.S. I couldn’t connect to Verizon’s “National Access.” I could however connect just fine upon returning to Pittsburgh, with my same beat up, abused card that she was convinced was my problem in Phoenix.

---

_[View the full topic](https://forums.speedlife.net/t/verizon-coverage-blows/195782)._
