- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since yesterday morning I've been having radom issues connecting to any number of websites (not all are impacted but most are). It ranges from fine, slow to never connecting. I am using an Apple Router (latest generation) via ethernet from the ONT. I've had FIOS since it was offered in my neighborhood and have always used some generation of Apple Router. I've never actually used the Verizon provided one. Until yesterday I've never actually had an issue. Now I am trying to understand where the problem is. This only seems to be impacting HTTP traffic. Other services using other protocols such as DNS are working fine. It also doesn't matter what device I am using as all show the same signs as far as normal, slow to never connecting.
Here is some curl output that depicts the actual issue:
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.046 FIRST_BYTE_TIME: 0.241 TOTAL_TIME: 0.241 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 67.062 FIRST_BYTE_TIME: 67.274 TOTAL_TIME: 67.274 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.045 FIRST_BYTE_TIME: 0.258 TOTAL_TIME: 0.258 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.046 FIRST_BYTE_TIME: 0.253 TOTAL_TIME: 0.253 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.048 FIRST_BYTE_TIME: 0.264 TOTAL_TIME: 0.264 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.000 FIRST_BYTE_TIME: 0.000 TOTAL_TIME: 74.424 REMOTE_IP:
DNS_LOOKUP: 0.014 CONNECT_TIME: 0.055 FIRST_BYTE_TIME: 0.264 TOTAL_TIME: 0.264 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.045 FIRST_BYTE_TIME: 0.244 TOTAL_TIME: 0.244 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.000 FIRST_BYTE_TIME: 0.000 TOTAL_TIME: 75.454 REMOTE_IP:
DNS_LOOKUP: 0.013 CONNECT_TIME: 0.053 FIRST_BYTE_TIME: 0.262 TOTAL_TIME: 0.262 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.047 FIRST_BYTE_TIME: 0.255 TOTAL_TIME: 0.255 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.005 CONNECT_TIME: 0.046 FIRST_BYTE_TIME: 0.255 TOTAL_TIME: 0.255 REMOTE_IP: 206.46.232.195
DNS_LOOKUP: 0.004 CONNECT_TIME: 0.046 FIRST_BYTE_TIME: 0.255 TOTAL_TIME: 0.255 REMOTE_IP: 206.46.232.195
Some sites are fine, but a majority I frequent are not. I've tried restarting my router and unplugging the power/battery to the ONT. The end results are still the same.
Anyone else expierencing this in the Northern Virginia area? Thoguhts on next steps?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Really spotty conncetion issues here too (since the 14th). I think it may be a verizon network issue.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I began noticing the same symptoms on April 14th. despite lack of any changes to hardware or software here since well before the problems began. Some sites will fail to load or exhibit an unusual delay in loading. It's most noticeable with streaming content. I have several Roku devices (different ages/models) which now all fail to play a lot of content (they'll buffer the first portion then fail to render the stream and abort the transfer).
I'd post curl output as well but I don't know the source addresses of the various streams the Roku devices have had trouble with so I'm glad someone here managed to do so.
The location of our FiOS drop is in Fairfax, VA.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here, also since yesterday morning. I frequently have to re-load websites, including Verizon's own Webmail. Signing in to Webmail also requires reloading the website repeatedly.
I'm in Silver Spring, MD
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue here as well. In Dale City, VA.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
same in Ashburn. I called Verizon and the tech on the phone said there is network issue. My traceroutes get past the residental network routers and then I start getting errors. As soon as trace leaves the verizon.net residental backbone router and it hits any of the gateway routers at alter.net the latency and drops start happening.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same thing happening here in Woodbridge. Can't connect to Xbox Live, most sites will load but only after 3 or 4 refresh attempts. Streaming is just unbearable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here in Manassas. IPNetMonitor (a very useful tool on the Mac) reports 33% packet loss, which is a crazy high number.
- 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
An update - as of 7.00 am this morning - eveything seems to beback to normal - not partial loads, nothing slow, no dropped connectivity, etc. If it changes again I'll post here.