- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So I spoke with Verizon about my Internet dropping all the time, and I have to wait for it to pick back up. This is on every computer, tablet, IPOD, Cell Phone. She told me that I needed to go up on my Internet speed. I was at 50/50, so she bumped me up to 75/75. WoW, I thought I would be flying, nope, complete opposite. It is slower, it continues to drop, and I ran the speed test from the Verizon site, I got a reading of 41/35. So I pay more for 75/75 and get worse service. I even have a newer router.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the test I ran.
Analysis information:
WEB100 Enabled Statistics: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done checking for firewalls . . . . . . . . . . . . . . . . . . . Done running 10s outbound test (client-to-server [C2S]) . . . . . 6.40Mb/s running 10s inbound test (server-to-client [S2C]) . . . . . . 11.44Mb/s ------ Client System Details ------ OS data: Name = Windows 8, Architecture = x86, Version = 6.2 Java data: Vendor = Oracle Corporation, Version = 1.8.0_51 ------ Web100 Detailed Analysis ------ 10 Mbps Ethernet 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 = 77.81 msec; the Packet size = 1460 Bytes; and There were 4 packets retransmitted, 38 duplicate acks received, and 39 SACK blocks received The connection stalled 3 times due to packet loss The connection was idle 0.76 seconds (6.90%) of the time S2C throughput test: Packet queuing detected: 64.38% This connection is receiver limited 2.94% of the time. This connection is sender limited 74.36% of the time. This connection is network limited 22.68% of the time. 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 = Microsoft Wi-Fi Direct Virtual Adapter MTU = 1500 Display Name = Realtek PCIe FE Family Controller MTU = 1500 Display Name = Qualcomm Atheros AR9485 Wireless Network Adapter MTU = 1500 Server 'resfiosspeed1.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] Packet size is preserved End-to-End 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 [100.7.37.242] but Client says [192.168.1.173]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using a hardwired device go to speedtest.verizon.net with no other devices active.
See what your test results are.
If you meet your subscribed speeds, then any delays are within or past the Verizon network.
If you don't take that info back to Verizon and tell them that your access is not working up to spec.