- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just talked to support (30 minutes to get through). they knew about the issues in maryland, but he said 4 more states just popped up. no reports in texas until me, but i'm definitely having these issues. i can't go to anything that is https.
he said they always give a 24 hour resolution window but it is usually only a few hours. I should get an automated call when it's resolved.
their queue of callers is hugh and growing fast, so they definitely know about the issue now.
thank goodness i have a backup cellular data plan.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here in Everett, WA, at 98.117.107.xxx
Can't get to sites like CNN nor log onto AIM.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Having the same problem connecting to a subset of web sites such as www.cnn.com, it does not appear to be a DNS issue as the direct IP address for cnn also fails.
It would be nice if verizon would put up a message on the support site/page indicating they were have a problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Its a DNS issue that is affecting Verizon customers nation wide at the moment. They are trying to track it down now.
I found a work around that seems to work. If you go into your adaptor settings. you can set static DNS. Leave the IP as "obtain automatically" but if you go to the DNS and say "use the following"... use these servers
4.2.2.1
4.2.2.2
they seem to be working. at least right now anyway