- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've tried live chat a couple times and they keeping running tests or talking to network team and then i get disconnected. Are there outages in the MD area or am I having some other issue? Has been happening since at least 8PM last night.
To add they have already rebooted the router, had me reset the router, had me try to do speed tests, and had me provide RWIN numbers.
On rare occassions I am able to get through to speedtest.net it is <1mb/s and fails to connect on upload tests
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you having any other service problems besides poor Internet speeds?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no, TV is fine. I don't have phone. Ocassionally I can actually get a speed test to start sometimes it will jump to 15-20 mb/s then just stops dead and times out, most of the time it times out before i can even start the test
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I live in Md and haven't had any issues.
have you tried running test to here: http://my.verizon.com/services/speedtest/
That will check connection internally to the Verizon network.
Will go a long way to help troubleshoot problem if you have issues internally.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am experiencing the same problem yesterday and today. Obviously not a client-side issue, but Verizon is being very coy about what is going on. OP, did your issue resolve?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm experiencing this problem since Saturday evening (same as OP). I live in northern VA.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spoke with a tech specialist this evening after inforing the chat representative that I would not be paying Verizon anything until service was restored to the levels I pay for. The specialist advised he would contact the "network team" in our area to confirm what the problem was and provide a time table for a resolution. I was supposed to hear back from them again after an hour, but it has been 2 hours so far. We will see. I worked in claims for 6 years, I can do this all day...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am experiencing the same issues described in this thread since Saturday, March 7th. I am paying for FIOS 50/50 mb/s service in the DC area. Until this weekend I had never bothered to perform speed testing because, at least for my uses, I had no problems and my latencies in online gaming were good (30-65 ms). During peak hours since Saturday, however, I am getting download rates in the range 1.6 to 2.8 mb/s and upload of 0.6 to 0.9 mb/s. First thing in the morning on Monday I was able to get 10/1 mb/s for d/u.
Here is what the output from Verizon's network diagnostics tool looks like for me (I've run in 5 times now and this is comparable to any peak hours time I've run it):
Analysis information:
WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done checking for firewalls . . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client-to-server [C2S]) . . . . . 759.0kb/s running 10s inbound test (server-to-client [S2C]) . . . . . . 869.65kb/s ------ Client System Details ------ OS data: Name = Windows 8, Architecture = x86, Version = 6.2 Java data: Vendor = Oracle Corporation, Version = 1.8.0_40 ------ Web100 Detailed Analysis ------ Cable modem/DSL/T1 link found. Link set to Full Duplex mode Information: throughput is limited by other network traffic. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 36.84 msec; the Packet size = 1452 Bytes; and There were 73 packets retransmitted, 159 duplicate acks received, and 191 SACK blocks received The connection stalled 7 times due to packet loss The connection was idle 1.65 seconds (15.0%) of the time S2C throughput test: Packet queuing detected: 96.38% This connection is sender limited 7.39% of the time. This connection is network limited 92.60% of the time. Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ON RFC 896 Nagle Algorithm: ON RFC 3168 Explicit Congestion Notification: OFF RFC 1323 Time Stamping: OFF RFC 1323 Window Scaling: ON Current Send Buffer 255 Kbyte Current Receive Buffer 64 Kbyte Display Name = Intel(R) Ethernet Connection (2) I218-V MTU = 1500 Display Name = Teredo Tunneling Pseudo-Interface MTU = 1280 Display Name = Microsoft ISATAP Adapter #2 MTU = 1280 Server 'resfiosspeed2.west.verizon.net' is not behind a firewall. [Connection to the ephemeral port was successful] Client is probably behind a firewall. [Connection to the ephemeral port failed] Information: Network Middlebox is modifying MSS variable Information: Network Middlebox is modifying Window scaling option Server IP addresses are preserved End-to-End Information: Network Address Translation (NAT) box is modifying the Client's IP address Server says [censored by me] but Client says [192.168.1.2]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Since posting last night my internet speeds have plummeted even lower (DC metro area, to Reston local server). Off peak hours I'm getting at most 4 mb/s download, 0.6 mb/s upload. My base latency to websites/games is 300 ms with spikes that can cause websites to fail to load properly - Verizon's own network diagnostics tool crashed on me only a few minutes ago. When I was able to get it to run here's a portion of the output it gave me (note the absolutely ridiculous and insulting levels of packet loss!):
Web100 reports the Round trip time = 41.79 msec; the Packet size = 1452 Bytes; and There were 70 packets retransmitted, 129 duplicate acks received, and 160 SACK blocks received The connection stalled 9 times due to packet loss The connection was idle 2.32 seconds (21.09%) of the time S2C throughput test: Packet queuing detected: 97.53% This connection is sender limited 1.73% of the time. This connection is network limited 98.27% of the time.