- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You are on a different Central Office if your on the Elmhurst, Queens Hub
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You don't have results during the slowdown fromt he Verizon speedtest server.
That would be the definiticve test if Verizon was throttling.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am receiving this issue for a WHILE now. My videos start buffering, my internet speed is slowed. I don't have any viruses on my computer nor do I have a slow computer. This has never been an issue with my previous internet provider, Optimum Online.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
do a trace route
Go to start type in cmd
Enter
Run command tracert verizon.net
post your results for comparison
C:\>tracert verizon.net
Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.11.1
2 3 ms 1 ms 2 ms L100.NYCMNY-VFTTP-72.verizon-gni.net [71.183.243.1]
3 * 13 ms * G2-3-1-6.NYCMNY-LCR-21.verizon-gni.net [100.41.194.214]
4 * * * Request timed out.
5 51 ms 47 ms 68 ms 0.ae2.DFW9-BB-RTR1.verizon-gni.NET [140.222.229.111]
6 60 ms 64 ms 64 ms so-2-1-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.81.20.219]
7 * * * Request timed out.
8 * * * Request timed out.
9 52 ms 53 ms 53 ms 206.46.228.129
10 50 ms 42 ms 53 ms 206.46.232.39
Trace complete.
C:\>
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tracing route to verizon.net [206.46.232.39]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 5 ms 3 ms L100.NYCMNY-VFTTP-192.verizon-gni.net [71.190.21
6.1]
3 9 ms 6 ms 8 ms G1-5-3-4.NYCMNY-LCR-21.verizon-gni.net [130.81.1
90.254]
4 * * * Request timed out.
5 43 ms 42 ms 41 ms 0.ae2.DFW9-BB-RTR1.verizon-gni.NET [140.222.229.
111]
6 43 ms 43 ms 44 ms so-2-1-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.
81.20.219]
7 * * * Request timed out.
8 * * * Request timed out.
9 44 ms 44 ms 46 ms 206.46.228.129
10 51 ms 52 ms 50 ms 206.46.232.39
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After numerous call's to tech support they always say everything is ok, and just acknowledge slow speed and no solution. Except needing to send out a technician to check on the ONT.
Will update more on the tech's visit.
Verizon Network team logs speed test at : http://speedtest.verizon.net
It's a shame on a 150/150 I only get 10Mbps
- 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
Tons of people are having this issue. Mostly on the east coast but I am having download problems 7-11pm and live in the LA area. It seems to be improving lately for me but started at the beginning of the year.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well Finally Verizon is finally upgrading there Overloaded Network I was switched over.
you can check yours here: http://my.verizon.com/services/speedtest/DefaultNdt.aspx
Old Connection:
------ Web100 Detailed Analysis ------
2.4 Gbps OC-48 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
New Connection: Fially
------ Web100 Detailed Analysis ------
10 Gbps 10 GigEthernet/OC-192 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
Tracert is still some issue with one of the servers and how the traffic is routed
As you see 2 trace roots ran with a minute of etchother 1st one ok 2nd one Not so good
Tracing route to google.com [173.194.123.73]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 2 ms 2 ms lo0-100.NYCMNY-VFTTP-352.verizon-gni.net [100.12.212.1]
3 5 ms 7 ms 4 ms T1-12-0-7.NYCMNY-LCR-21.verizon-gni.net [100.41.221.242]
4 2 ms 2 ms 2 ms 130.81.199.10
5 4 ms 2 ms 2 ms 0.xe-2-0-4.XT1.NYC4.ALTER.NET [152.63.10.17]
6 7 ms 11 ms 11 ms TenGigE0-6-0-7.GW8.NYC4.ALTER.NET [152.63.21.69]
7 65 ms 64 ms 74 ms google-gw.customer.alter.net [152.179.72.62]
Trace complete.
Tracing route to google.com [74.125.226.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 19 ms 1 ms 2 ms lo0-100.NYCMNY-VFTTP-352.verizon-gni.net [100.12.212.1]
3 3 ms 7 ms 3 ms T1-12-0-6.NYCMNY-LCR-22.verizon-gni.net [130.81.98.138]
4 * * * Request timed out.
5 82 ms 75 ms 67 ms 0.so-6-0-0.XT2.NYC4.ALTER.NET [152.63.17.97]
6 90 ms 87 ms 93 ms TenGigE0-7-0-7.GW8.NYC4.ALTER.NET [152.63.21.73]
7 147 ms * 163 ms google-gw.customer.alter.net [152.179.72.62]
Trace complete.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seeing as how the traceroute went to two totally different ips, that means nothing.
FOr an accuracte comparison, run traceroute to the same ip each time.
- « Previous
-
- 1
- 2
- Next »