FMA

Ar.PI, thanks for the update. FWIW, the problem in Brooklyn hasn't been corrected. The following are my DL and UL results taken at @ 10:00pm EST. :::.. Download Stats ..::: Connection is:: 310 Kbps about 0.3 Mbps (tested with 386 KB) Download Speed is:: 38 KB/s Tested From:: http://www.testmy.net/ Bottom Line:: 6 times faster than 56K you can download 1MB in 26.95 second(s) Validation Link:: https://testmy.net/cgi-bin/get.cgi?Test_ID=FBJQAKRC8 :::.. Upload Stats ..::: Connection is:: 667 Kbps about 0.7 Mbps (tested with 579 KB) Upload Speed is:: 81 KB/s Tested From:: http://www.testmy.net/ Bottom Line:: 12 times faster than 56K you can upload 1MB in 12.64 second(s) Validation Link:: https://testmy.net/cgi-bin/get.cgi?Test_ID=VBXD74LF5 Hopefully, this will be resolved soon.

I have the same exact problem. Only started to happen after I upgraded my circuit from 1.5/128 to 3/768. It's fine now, I think, but the speeds are so off the wall. Here's my tracert to speakesy.net taken at around 2am. Tracing route to nyc.speakeasy.net [216.254.95.2] over a maximum of 30 hops: 1 27 ms 25 ms 24 ms 10.32.105.1 2 25 ms 25 ms 33 ms at-2-3-1-1724.CORE-RTR1.NY325.verizon-gni.net [1 30.81.11.41] 3 26 ms 26 ms 26 ms so-4-0-0-0.BB-RTR1.NY325.verizon-gni.net [130.81 .8.25] 4 46 ms 32 ms 33 ms so-5-0-0-0.BB-RTR1.RES.verizon-gni.net [130.81.8 .253] 5 32 ms 32 ms 31 ms so-6-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81 .10.90] 6 32 ms 32 ms 33 ms 130.81.15.42 7 34 ms 34 ms 33 ms so-4-0-0.mpr2.iad2.us.above.net [64.125.30.122] 8 34 ms 33 ms 33 ms so-4-0-0.mpr1.iad1.us.above.net [64.125.28.213] 9 38 ms 38 ms 38 ms so-2-0-0.cr1.lga1.us.above.net [64.125.28.62] 10 63 ms 38 ms 38 ms so-0-0-0.mpr1.lga1.us.above.net [64.125.27.142] 11 37 ms 37 ms 36 ms so-1-0-0.cr1.lga3.us.above.net [64.125.30.18] 12 31 ms 31 ms 32 ms 208.184.48.181.speakeasy.net [208.184.48.181] 13 33 ms 32 ms 32 ms dns.nyc1.speakeasy.net [216.254.95.2] Trace complete. I tried to call Verizon a couple of days ago and after being on hold for almost an hour, I gave up. I going to try them again over the weekend and see what happens. It's interesting to note that the problem seems to be in the NYC area. I'm in Brooklyn and have never had a problem before this. Hopefully one of us will be able to shed some light on this matter.