How about showing some integrity and honesty concerning this ongoing nightmare of networking incompetence ? Verizon is still screwing all of us in the 14 state, rural acquisition area. It started as far back as mid day, Dec. 24th, 2009. At that time, we were being hardware re-routed. Set off on the side rail while the "bullet train" of real broadband went screaming past. That was Verizon's " Merry Christmas" to rural area customers. The "Happy New Year" was the hard coding and flashing of our modems with the IP Gateway, re-route switch. It's been a running battle ever since.
$10 billion up front, over $3 billion in the hole, 7 months to try and figure out how to migrate a working network solution on equipment that was poorly, if at all, maintained ? Frontiers solution has been to stay reliant on Verizon's "Hosting" infrastructure and leaving them in complete control over what continues to be happening. You can set your clock's by what happens, almost without fail, at approximately 4:00pm EST. Forget about any chance at productivity during peak traffic hours and speeds barely capable of even sending a fax. (14.4Kb). From 4'ish, until after 12:00 am, the bandwidth get's throttled back to a crawl.
EG: 2 recent trace routes as well as transceiver stats.
C:\Users\>tracert frontier.com
Tracing route to frontier.com [66.133.172.92]
over a maximum of 30 hops:
1
---------------------------------------------------------------------------------- -------------
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\>tracert frontier.com
Tracing route to frontier.com [66.133.172.92]
over a maximum of 30 hops:
1
----------------------
Transceiver stats from a recently replaced, Frontier branded, Westell 7500.
Software Version: VER:5.01.01.07
Transceiver Revision: A2pB020b3.d20h
Model Name: A90-750045-07
Serial Number: *************
Broadband Connection Status: Connected
Broadband IP Address: 71.186.51.62
Broadband MAC Address: -------------
Broadband Connection Type: PPPoE
Active Status: 0:00:31:51
Configuration: 096-900222-00 A
--------------------------------------------------
Transceiver Revision A2pB020b3.d20h
Vendor ID Code 4D54
Line Mode ADSL_2plus
Data Path FAST
Transceiver Information Down Stream Path Up Stream Path
DSL Speed (Kbits/Sec) 1790 447
Margin (dB) 10.9 23.2
Line Attenuation (dB) 58.5 30.3
Transmit Power (dBm) 5.5 12.4
------------------------------------------------------------------
We've all read about call's to support, 1st level - Supervisors desk, etc... and all have the same mantra, the big fix is coming, Dec., no, January, whoops, maybe February, nope, how about March, sometime the 1st Quarter, maybe June ... ? And, oddly enough, each State is first in line for this miracle fix.
Phft-t-t-t-t. Yeah, Right.
More than 5 different routing schema's in the past 2 months, each worse than the previous. I especially liked the one that hopped from Chi.Level3.net to ... wait for it, 2 hops through Montreal, Canada before coming right back to (il,chi.frontier.clusterphuc.net ). Then on to the next huge bottleneck as far as latency, dropped signals due to lost packets, retransmitted packets, blocks received out of sequence... Make's me wonder how it's possible for the "networking guru's" at Frontier, in Rochester, NY. to still be drawing paychecks. These idiots couldn't find their collective butt's with both hands, an anatomical map with a flashing bulls-eye encircling the buttocks, a troop of Boy Scouts as well as having GPS chip implanted in their butt cheek. They'd still be touching their noses and asking, am i getting warm yet ?
I envy the posters that have alternative broadband options in their area's and have told Frontier to take a hike.
Bottom line here is, Until Verizon is out of the picture, entirely, We're screwed.
)
·
·
·