site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
4285
Share Topic
Posting?
Post a:
Post a:
Links: ·FiOS Map ·Vz FiOS FAQ ·General Fiber Optics ·Vz FiOS Monitors ·Submit a FAQ
page: 1 · 2 · 3 · 4 · 5
AuthorAll Replies

Mar9tin

join:2012-07-08

speednet grade of F

I am currently able to download at only 1/10th of the b/w I pay for. Speednet grades this F. I know we had storms through here this afternoon, but this seems to be a regular Sunday nite occurrence and I'm frigging tired of it.

gadgetboyj

join:2009-08-25
Staten Island, NY
kudos:2

What router are you using? Is it the Verizon supplied Actiontec MI424WR? If so, what revision is it?



More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:28

reply to Mar9tin
•What tier are you on?
•Are you testing wired or wireless?
•Do you get full speed the rest of the time?
•When this happens, what speeds do you get on VZ's test site?
--
There are 10 kinds of people in the world; those who understand binary and those who don't.



danclan

join:2005-11-01
Midlothian, VA

Further:

What site?

Without more information folks can neither confirm or deny your complaint.


Mar9tin

join:2012-07-08

reply to Mar9tin
The problem persists. The router has nothing to do with it altho it is an old D-link 624. I was getting 10Mbps before Sunday's storms in the the DC area and now it's between 1 and 1.5Mbps. I foolishly contacted a Verizon no-nothing, in India apparently, who asked me to reset my router, which of course lost all my settings, my connection and him. But good riddance. What galls me is that this is obviously a network problem, and Verizon doesn't have the balls to just admit and ask for patience. They are on a par with Pepco.


Mar9tin

join:2012-07-08

reply to danclan
Speednet.net, but I got the same result here.


Mar9tin

join:2012-07-08

I wouldn't touch one of Verizon's tests with a ten-foot pole. I've used Verizon since about 2002 abd FIOS since 3005. Posted here years ago, I think before they required log-ins, at least I couldn't find the user:pass and had to sign up again just to look at the forum. I saw something about slow speeds somewhere on this site yesterday, but couldn't find it again and still can't.



danclan

join:2005-11-01
Midlothian, VA

so you are still not providing us with any information regarding details to assist. Without such details and without using tools that have been recommended we really cant help you.

There is nothing wrong with verizons speed test.

We still dont know where you are trying to get to

We dont know what service you are supposed to be getting

You do appear to be running on very old equipment, nothing wrong with it but its just old.



birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
kudos:8

reply to Mar9tin
FiOS support does not go to India, at least at this time.

Perform a traceroute to dslreports.com and post the results.

Also, use »my.verizon.com/micro/speedtest/broadband/ and click the red button for the classic speed test. It includes a link for connection details that will be helpful in diagnosing.

If you're ordinarily getting 10Mbps with a D-link 624, you're either on an old legacy plan, or you're limited by hardware/software on premises. Then a storm rolls through and you get worse.

Understandable, but details are needed, including what you're supposed to get. We had a legacy 10/2 plan at one location until we upgraded to business account 25/25 in January.


prisaz

join:2008-08-11
Germantown, MD
Reviews:
·Verizon FiOS

4 edits

reply to Mar9tin
If you do have FiOS, I would say Verizon owes you a new router. The DI-624 is old, and even on my 20/5 connection it would choke. I would say they owe you an updated Actiontec router. If that does not solve your issues, then perhaps a tech needs to come and check your ONT or run more test.

Oh yes let me mention I am not 20/5 anymore. I am running Quantum 75/35, and get about 84/39. I have had about every bundled speed since 2005, and always A+. Oh I skipped the 5Mbps speed at launch, and went straight 15/2, 20/5, 25/25, 35/35, and now 75/35. Fios rules.

Make them send you a new router. My DI-624 was upgraded when TV was added. Now if you were a convert from DSL, they may have given you an older router if you don't have FiOS TV. Some of the very first TV installs may have used the 624 with and adapter for the TV connection. Bottom line you should get a new router, regardless.

Montgomery County Maryland

Edit for spelling.



aaronwt
Premium
join:2004-11-07
Woodbridge, VA
Reviews:
·Verizon FiOS

reply to Mar9tin
You missed the 30/5 and 50/20
Those are the two I had over the last five years before getting the 35/35 tier when it came out. I'm still flip flopping about pulling the trigger on 75/35. If the upload speed was higher I would switch in a heartbeat.


prisaz

join:2008-08-11
Germantown, MD
Reviews:
·Verizon FiOS

said by aaronwt:

You missed the 30/5 and 50/20
Those are the two I had over the last five years before getting the 35/35 tier when it came out. I'm still flip flopping about pulling the trigger on 75/35. If the upload speed was higher I would switch in a heartbeat.

They were never offered in a "Bundle" in our market. 30/5 or 50/20. In Tripple Play. or any other.

xocsucram

join:2008-10-02

2 edits

reply to Mar9tin
its probably an issue with the verizon routers in your region(the actual routers for internet traffic, not your household routers), i was having issues earlier this year, an finally pinpointed specific regional IPs which belonged to Fios, that were causing it using tracerts, they fixed it about a week later.

you can also try running a test on Pingtest.net to all the servers in your area, not just the "recommended" ones and see if only certain ones give really bad results.

if you have a server close to you that has great results and another right next to it giving you the bad grade, they're probably going thru a bad router.

your Pingtest should be 1-2MS of ping delay and less than 5 jitter. dont worry about packetloss if you have manual security restrictions setup, the Jitter and Ping Delay are all you need.

also streaming data shouldn't effect your scores, i can run the test while streaming 3-4 games on MLB.tv, running Youtube ect... the scores are the same.


SL83

join:2005-05-28
Oceanside, NY
kudos:1

reply to Mar9tin
This is the wonderful connection quality I have been experiencing for the past week or so:

C:\Windows\system32>tracert speedtest.verizon.net

Tracing route to speedtest.verizon.net [206.46.241.4]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms L100.NYCMNY-VFTTP-135.verizon-gni.net [98.116.10
0.1]
3 7 ms 7 ms 6 ms G0-13-3-5.NYCMNY-LCR-22.verizon-gni.net [130.81.
182.182]
4 7 ms 6 ms * so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.151.234]
5 107 ms 93 ms 54 ms so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81
.17.41]
6 54 ms 54 ms 54 ms so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.
81.20.157]
7 144 ms 251 ms 217 ms po1.ctn-border1.vzlink.com [206.46.225.85]
8 57 ms 56 ms 56 ms 206.46.225.210
9 55 ms 56 ms 56 ms 206.46.241.4

Trace complete.

So far it has yielded me with a "Is this happening on all your computers?"



More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:28

Why are you using a Dallas speedtest server, when you are in New York? Use a closer server.
--
There are 10 kinds of people in the world; those who understand binary and those who don't.


rebus9

join:2002-03-26
Tampa Bay
Reviews:
·Verizon FiOS
·Bright House

reply to SL83

said by SL83:

This is the wonderful connection quality I have been experiencing for the past week or so:

C:\Windows\system32>tracert speedtest.verizon.net

Tracing route to speedtest.verizon.net [206.46.241.4]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     4 ms     4 ms     4 ms  L100.NYCMNY-VFTTP-135.verizon-gni.net [98.116.10
0.1]
  3     7 ms     7 ms     6 ms  G0-13-3-5.NYCMNY-LCR-22.verizon-gni.net [130.81.
182.182]
  4     7 ms     6 ms     *     so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.151.234]
  5   107 ms    93 ms    54 ms  so-4-0-0-0.DFW01-BB-RTR1.verizon-gni.net [130.81
.17.41]
  6    54 ms    54 ms    54 ms  so-1-0-0-0.DFW03-CORE-RTR1.verizon-gni.net [130.
81.20.157]
  7   144 ms   251 ms   217 ms  po1.ctn-border1.vzlink.com [206.46.225.85]
  8    57 ms    56 ms    56 ms  206.46.225.210
  9    55 ms    56 ms    56 ms  206.46.241.4
 
Trace complete.

So far it has yielded me with a "Is this happening on all your computers?"

What's wrong with the traceroute results? It looks pretty textbook clean to me. 56ms between NYC and TX.

If you're referring to the lack of response to the third echo on hop #4, then you clearly know nothing about traceroutes and how intermediate routers handle ICMP.

The only thing that matters is END TO END (hint: Last Hop) connection, and your traceroute results show consistent results within 1ms of each other with zero loss.

rebus9

join:2002-03-26
Tampa Bay
Reviews:
·Verizon FiOS
·Bright House

2 edits

reply to SL83

said by SL83:

This is the wonderful connection quality I have been experiencing for the past week or so:

C:\Windows\system32>tracert speedtest.verizon.net

You're tracing to the VZ speedtest front-end. It doesn't matter where that's hosted, because AFTER you enter the speedtest site, you choose the state you're in.

Your speed test DOES NOT RUN from the "speedtest.verizon.net" front-end.

IP address of the NY speedtest: 108.12.159.18

Traceroute to there, and you'll see much different results.

SL83

join:2005-05-28
Oceanside, NY
kudos:1

reply to More Fiber
Yeah my bad - I posted the wrong results. I've had spikes over 130ms to my gateway and packetloss to my gateway.

That's what happens when you're up too late several nights in a row:

Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 71 ms 74 ms 74 ms L100.NYCMNY-VFTTP-135.verizon-gni.net [98.116.10
0.1]
3 61 ms 54 ms 59 ms G0-10-5-0.NYCMNY-LCR-22.verizon-gni.net [130.81.
129.76]
4 106 ms 67 ms 66 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.151.234]
5 66 ms 74 ms 69 ms 0.ae5.BR3.NYC4.ALTER.NET [152.63.16.9]
6



More Fiber
Premium,MVM
join:2005-09-26
West Chester, PA
kudos:28

said by SL83:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 71 ms 74 ms 74 ms L100.NYCMNY-VFTTP-135.verizon-gni.net [98.116.100.1]

That's clearly indicative of a problem between you and VZ's edge router. Simply pinging the edge router doesn't indicate if you're seeing lost packets, which is why I prefer WINMTR.

However, even WINMTR isn't going to tell you if it's a bad ONT, a bad optical splitter, poor fiber connection, or a bad PON card.

--
There are 10 kinds of people in the world; those who understand binary and those who don't.

SL83

join:2005-05-28
Oceanside, NY
kudos:1

reply to Mar9tin
One kinda long ping test to my gateway (sorry for the length)

Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=16ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=12ms TTL=126
Reply from 98.116.100.1: bytes=32 time=3ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=33ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=169ms TTL=126
Reply from 98.116.100.1: bytes=32 time=161ms TTL=126
Reply from 98.116.100.1: bytes=32 time=164ms TTL=126
Reply from 98.116.100.1: bytes=32 time=167ms TTL=126
Reply from 98.116.100.1: bytes=32 time=169ms TTL=126
Reply from 98.116.100.1: bytes=32 time=171ms TTL=126
Reply from 98.116.100.1: bytes=32 time=174ms TTL=126
Reply from 98.116.100.1: bytes=32 time=176ms TTL=126
Reply from 98.116.100.1: bytes=32 time=176ms TTL=126
Reply from 98.116.100.1: bytes=32 time=178ms TTL=126
Reply from 98.116.100.1: bytes=32 time=179ms TTL=126
Reply from 98.116.100.1: bytes=32 time=182ms TTL=126
Reply from 98.116.100.1: bytes=32 time=188ms TTL=126
Reply from 98.116.100.1: bytes=32 time=117ms TTL=126
Reply from 98.116.100.1: bytes=32 time=129ms TTL=126
Reply from 98.116.100.1: bytes=32 time=129ms TTL=126
Reply from 98.116.100.1: bytes=32 time=102ms TTL=126
Reply from 98.116.100.1: bytes=32 time=108ms TTL=126
Reply from 98.116.100.1: bytes=32 time=107ms TTL=126
Reply from 98.116.100.1: bytes=32 time=113ms TTL=126
Reply from 98.116.100.1: bytes=32 time=116ms TTL=126
Reply from 98.116.100.1: bytes=32 time=118ms TTL=126
Reply from 98.116.100.1: bytes=32 time=122ms TTL=126
Reply from 98.116.100.1: bytes=32 time=127ms TTL=126
Reply from 98.116.100.1: bytes=32 time=131ms TTL=126
Reply from 98.116.100.1: bytes=32 time=132ms TTL=126
Reply from 98.116.100.1: bytes=32 time=134ms TTL=126
Reply from 98.116.100.1: bytes=32 time=113ms TTL=126
Reply from 98.116.100.1: bytes=32 time=116ms TTL=126
Reply from 98.116.100.1: bytes=32 time=121ms TTL=126
Reply from 98.116.100.1: bytes=32 time=34ms TTL=126
Reply from 98.116.100.1: bytes=32 time=17ms TTL=126
Reply from 98.116.100.1: bytes=32 time=14ms TTL=126
Reply from 98.116.100.1: bytes=32 time=16ms TTL=126
Reply from 98.116.100.1: bytes=32 time=77ms TTL=126
Reply from 98.116.100.1: bytes=32 time=76ms TTL=126
Reply from 98.116.100.1: bytes=32 time=23ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=18ms TTL=126
Reply from 98.116.100.1: bytes=32 time=11ms TTL=126
Reply from 98.116.100.1: bytes=32 time=10ms TTL=126
Reply from 98.116.100.1: bytes=32 time=10ms TTL=126
Reply from 98.116.100.1: bytes=32 time=10ms TTL=126
Reply from 98.116.100.1: bytes=32 time=10ms TTL=126
Reply from 98.116.100.1: bytes=32 time=8ms TTL=126
Reply from 98.116.100.1: bytes=32 time=8ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=6ms TTL=126
Reply from 98.116.100.1: bytes=32 time=8ms TTL=126
Reply from 98.116.100.1: bytes=32 time=7ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=13ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=8ms TTL=126
Reply from 98.116.100.1: bytes=32 time=135ms TTL=126
Reply from 98.116.100.1: bytes=32 time=35ms TTL=126
Reply from 98.116.100.1: bytes=32 time=30ms TTL=126
Reply from 98.116.100.1: bytes=32 time=43ms TTL=126
Reply from 98.116.100.1: bytes=32 time=50ms TTL=126
Reply from 98.116.100.1: bytes=32 time=53ms TTL=126
Reply from 98.116.100.1: bytes=32 time=55ms TTL=126
Reply from 98.116.100.1: bytes=32 time=63ms TTL=126
Reply from 98.116.100.1: bytes=32 time=63ms TTL=126
Reply from 98.116.100.1: bytes=32 time=70ms TTL=126
Reply from 98.116.100.1: bytes=32 time=88ms TTL=126
Reply from 98.116.100.1: bytes=32 time=43ms TTL=126
Reply from 98.116.100.1: bytes=32 time=58ms TTL=126
Reply from 98.116.100.1: bytes=32 time=63ms TTL=126
Reply from 98.116.100.1: bytes=32 time=60ms TTL=126
Reply from 98.116.100.1: bytes=32 time=88ms TTL=126
Reply from 98.116.100.1: bytes=32 time=60ms TTL=126
Reply from 98.116.100.1: bytes=32 time=63ms TTL=126
Reply from 98.116.100.1: bytes=32 time=63ms TTL=126
Reply from 98.116.100.1: bytes=32 time=70ms TTL=126
Reply from 98.116.100.1: bytes=32 time=65ms TTL=126
Reply from 98.116.100.1: bytes=32 time=70ms TTL=126
Reply from 98.116.100.1: bytes=32 time=100ms TTL=126
Reply from 98.116.100.1: bytes=32 time=50ms TTL=126
Reply from 98.116.100.1: bytes=32 time=55ms TTL=126
Reply from 98.116.100.1: bytes=32 time=55ms TTL=126
Reply from 98.116.100.1: bytes=32 time=68ms TTL=126
Reply from 98.116.100.1: bytes=32 time=55ms TTL=126
Reply from 98.116.100.1: bytes=32 time=55ms TTL=126
Reply from 98.116.100.1: bytes=32 time=65ms TTL=126
Reply from 98.116.100.1: bytes=32 time=73ms TTL=126
Reply from 98.116.100.1: bytes=32 time=58ms TTL=126
Reply from 98.116.100.1: bytes=32 time=65ms TTL=126
Reply from 98.116.100.1: bytes=32 time=62ms TTL=126
Reply from 98.116.100.1: bytes=32 time=70ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
Reply from 98.116.100.1: bytes=32 time=5ms TTL=126
 
Ping statistics for 98.116.100.1:
Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 188ms, Average = 18ms

No packetloss this time - but the latency seems to spike out of nowhere. Running actual speed tests I get some odd results. On myspeed.visualware.com I am getting erratic results:

Just did 2 tests back to back, one I was getting 42Mbps down and 35 up, 5 seconds later I am getting 1.68Mbps down 36.4 up.

The actual verizon speed test I am getting semi stable downspeeds but consistent up speeds of 12Mbps.

Thursday, 20-Jun 01:37:42 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics