An Updated List of Areas where Verizon's 3G Express Network (1XRTT/EvDO) and 4G/LTE Data Services Regularly Experience Service Difficulties

Last Update: 04/28/2014

This list is intended to provide a consolidated state-by-state reference to a series of posts, messages, and other observations as to dropped data calls and/or forcefully reset 3G/1XRTT/EvDO/Express Network and 4G/LTE Connections Verizon's data service ar eas in the US.

[ Wirelessnotes Main | Interpage | Verizon Problems/Drops Overview/General | Systemic/Initial 3G/1X/EvDO issues | Criteria for Inclusion | Verizon 3G/4G Data Network Drops | Corrected/Remedied Issues | Verizon Cellular Drops | Verizon DC Metro Drop Map | AT&T Wireless List | Sprint CDMA List | Nextel List | Disclaimer | Contact Wirelessnotes.org ]

Tell your elected officials what you think! Use LobbyByFax(sm) to instantly send a free fax from the web to your elected Congressional and State-wide representatives supporting telecommunications, Internet net-neutrality, transportation and other issues! Some of the current LobbyByFax alerts include: Stop Tolls on East River Bridges in NYC!: Keep New York's East and Harlem River Bridges Free! Help stop Gov. Paterson's / Richard Ravitch's Plan to Toll NYC's Bridges! Use the link to get to the LobbyByFax.Com system, and select New York State from the drop down menu box. All of New York's Albany delegation, the Governor, and the New York City Council are listed ; send a free fax to them and let them know you oppose any tolls on the Brooklyn , Williamsburg, Manhattan, Queensboro, Third and Willis Ave, and Harlem River bridges. A sample letter (which is used on the LobbyByFax East River toll action alert) is located here. Be heard and help stop tolling of all the East River and Harlem River crossings! Stop Photo Radar in Maryland and the expanded use of photo enforcement in Montgomery and Prince George's Counties vis a vis Photo Radar/Red Light Cameras, and other Automated Tra ffic Enforcement! Send a free fax to Governor O'Malley as well to the Annapolis Legislature telling them to vote against the expansion of photo radar and other automated traffic enforcement and monitoring in Maryland. Tell them that these systems violate due process, place an unfair burden upon the registrant of the vehicle, are subject to "cloning", allowing malicious copies of license plates to be used to incur culpability upon innocent registrants, and effectively set up a "pay to speed" system where those who can afford it can speed when desired. Go to the LobbyByFax Alerts Overview page and select the "Maryland Photo Radar" alert, or go directly to the Stop Maryland's Use of Speed Cameras alert for state lawmakers and Governor O'Malley. Note: Please be sure to select Maryland from the initial state-selection drop-down menu. Stop our Interstate Highways from being tolled!: Send a fax to Congress demanding that they do not allow tolls to be placed on free Interstates. We all pay a gas tax, we should n ot be taxed again with tolls! (As Pennsylvania is doing with I-80) Stop the Recording Industry: The heavy-handed approach of the recording industry to block copying via digital rights management is a cheap attempt to have Congress and thus the American public pay for the failed policies of the Recording Industry. We should no t tolerate, and Congress should not allow, the onerous restrictions which the Industry wishes to impose upon us, as the cost and loss of utility which such restrictions will create are incalculably greater than the minimal benefit in terms of higher profi ts which will be generated for the Industry. Rebuild the Twin Towers of the World Trade Center: Although current plans to rebuild the World Trade Center provide for a moderately tall 1,776 foot structure, the skyline of NYC will never be restored without the original towers of the WTC, and anything short of this goal will forever remain a tacit concession to those who destroyed them. For a complete list of all current LobbyByFax alerts, please visit the Interpage LobbyByFax.com site and click the start button on the main page, or click here for a summary page.

A number of other problems which are unique to Verizon's wireless data network are:

Generally, a Static IP is not offered, and customers are required to pay Verizon Wireless something like $500 to get one. Sprint/Nextel's 1XRTT/EvDO Service and ATTWS/Cingular's EDGE Service offer static IPs at no additional charge. Although some people prefer a dynamic IP for the anonymity it may offer, a static IP is very useful if a given user(s) will have p eople connect to a company's or their own wireless device and/or as a given remote user may need to access a corporate LAN or home network which blocks unknown IPs. By having a static IP, firewalls, routers, mailers and other TCP/IP devices/services can allow only the given wireless device to connect while barring all others. Verizon's insistence on dynamic IPs and charging $500 per static IP essentially precludes the widespread use of static IPs by most Verizon customers.

24 Hour Disconnects: Verizon's 1XRTT/EvDO and LTE services disconnect automatically after 24 hours, so a Verizon 1X/EvDO customer has a connection open and someone is FTPing files to/from the wireless device and the 24 hour period expires, the conn ection is terminated and all transferred data lost. They can prevent this in their switch (we've had them on occasion do this with us, only be overridden in a few months by some automated process on their side which checks for these things or som ething), but almost never will. From a cursory look around the Internet, it seems that a lot of people complain about this as part of Verizon's highly restrictive use policies, and they don't seem to care.

Rapid Timeouts: As a mobile users temporarily looses connectivity (drive though a tunnel or travel momentarily into a poor coverage area), the 1XRTT or EvDO software will only allow 3 to 4 minutes before it drops and the instant connection is lost, thus any open TCP/IP sessions (like Telnet, SSH, web streams, FTP, etc.) are lost as well. CDPD was not like this (see above), and I see no reason why Verizon has such a short timeout period. Obviously loss of coverage in a given area is not our "fault", and if Verizon can't support coverage in some well-traveled areas at the very least allow for the data timeouts on 1X/EvDO to be a good deal longer. They are aware of this and again just don't seem to care. (We need to see how Sprint's 1X/EvDO and AT&T/Cingular's EDGE systems handle this; EDGE does seem to want to wait longer before it times out, but it has other problems which prevent us from using it.)

EvDO-specific Issues:: Although Verizon as of late 2006 seems to have a better handle on the 1XRTT drop issues and many are being fixed as the CDMA-based data network expands, similar issues and difficulties seem to be appearing with the implementation of the higher-speed EvDO and EvDO Rev.A services throughout Verizon's data service areas.

This list tends to call these EvDO issues "Cycle" issues. "Cycle Areas", as per area not drops per se, that is, the connection is not torn down requiring a manual re-connect, but instead an area where the transition from 1XRTT to/from EvDO does not occur "smoothly", causing connections to "hang" either for more than a momentary period (at best) or to completely time out (at worst). In such cases, telnet/SSH/SSL and other ongoing connections will need to be re-established, as well as downloads, streaming audio and video, etc. Again, the EvDO/1XRTT software does not disconnect, but the extended delay in cycling "up" from 1XRTT to EvDO or cycling "down" from EvDO to 1XRTT, during which time data does not seem to pass, results in established TCP/IP connections being lost.

We are assuming that this is part of the debugging and initial implementation of the EvDO system, and that as soon as EvDO is universally implemented a lot of these "cycle" issues will go away. However, after two years (almost) of EvDO service, many of these issues remain, and the EvDO service seems too "delicate" and "fussy" compared to the 1XRTT service (and hence we do not yet use EvDO for any mobile application) or the much more robust (and now gone :( ) CDPD service. EvDO Cycle Area drops are detailed in the EvDO Cycle section of this list.

Overall, this list will hopefully serve as a central source where such drop information may be collected, posted, and utilized in furtherance of future service improvements by Verizon.

EvDO Step Up Failure: EvDO does not step back up to EvDO service speeds from 1XRTT speeds when moving from a 1XRTT area into an EvDO area. That is, if you initiate a connection in a (slower) 1XRTT only area, and then move to an EvDO area, the connection will remain at 1XRTT. This is also true at times if you initiate a connection in an EvDO area, transit to a 1XRTT area, and then transit back to an EvDO area. While not a drop (connectivity is generally not affected), these "step up failure" issues prevent EvDO customers who are mobile or in areas on the border between EvDO and slower 1XRTT service from enjoying the full benefit of EvDO speeds.

EvDO Drops: There are a seemingly large number of EvDO areas where the service inexplicably drops. These areas generally correspond with areas in which 1XRTT had the same service drop problems a number of years ago (which have been subsequently fixed) or which currently have outstanding 1XRTT drop issues. There are also some which show no apparent problems on the 1X side but for some reason drop in EvDO mode.

EvDO Hangs and Step Up/Down Hangs: Some EvDO coverage areas suffer from sections where connections simply "hang" for minutes on end (generally 2 to 4 minutes before resuming). In some cases this is apparently related to the EvDO device stepping up or down between EvDO mode and the slower 1XRTT mode. During these times, the connection remains active, but no data is passed. It is almost as if the wireless modem is having a hard time deciding what "mode" (1X or EvDO) to be in, and while it is considering the matter, does not pass any data. In other cases, the network hangs for no apparent reason, although this may be related to a "step up/down" issue occurring in the background and undetectable to users.

States and areas where these three EvDO-specific issues occur are listed in the EvDO Cycle Drops section.

Ordering Note: Lists are alphabetically organized, first by state and then by counties within states. In some cases, large Metropolitan areas which span a multiple set of counties, states or boundaries are listed as separate entities (such as New Y ork City).

Certain subway systems (such as DC Metro) are organized by line and are considered subcategories within the city they are contained.

Please feel free to submit your drop/reset experiences with Verizon which meet the above guidelines so that we can provide a more comprehensive list.

Additionally, if you feel that an item is incorrect, please let us know the specifics of your experiences in the given area so we can test it and modify the list accordingly.

Thanks!

Disclaimer/Note: The authors have nothing to do with Verizon other than using a few of their phones and/or data products as paying subscribers. While we will try to keep these lists current, you should test them out for yourself and not use this as a dispositive and authoritative source of information as to Verizon's cellular service (or lack thereof). In other words, these are just our and/or other's observations -- we try to be accurate, but we make no representations other than what we have observed (and if others notice we are wrong about a given drop, please mail us so we can test the drop and modify the list accordingly.)

Verizon Cellular Dropped/Reset 1XRTT/Express Network Session List by State

Connecticut

Fairfield County, Fairfield: Data drops occur while driving on I-95 heading north at Exit 24, approximately 2-4 miles south of Bridgeport. Most recent instance occurred on 10/01/2007.

Fairfield County, Greenwich, CT/NY border handoff: Approx. 50% of the time, upon initiating an Express Network Session in CT/00119 and driving down I-95 into NY State continuing to the NYC area (i.e., not heading west on I-287 or something), Verizon 1 XRTT Express Network Sessions will drop about 2 miles south of the CT border, near where similar cellular drops occur, at the Rye Playland Parkway overpass. The drops here usually cause the entire IP configuration of the laptop to "freeze", and merely re- starting the 1XRTT connection will not help -- all applications using IP traffic will not work and the laptop will need to be rebooted (verified with Win98, Win2000, and WinXP). Does not seem to happen as frequently on the Merritt, but is a very common an d very annoying problem southbound on I-95. 06/14/2003.

Fairfield County, Greenwich, CT and Purchase, NY state line along the Merritt/Hutch parkways, southbound only. 3G (1XRTT and EvDO) as well as 4G/LTE connections drop about 75% of the time when transitioning from the CT/00119 system to the NY-NJ/00022 system, generally as the Hutch passes over I-684. This problem only affects southbound traffic; northbound connections initiated in NY and progressing up the Hutch and then transiting to CT on the Meritt do not drop. This occurs generally in the same area where 800 MhZ only cellular phones drop, which also only occurs in the southbound direction (see the Verizon Cellular/Voice drops list for details). Last observed: 03/28/2014.

Fairfield County, Stamford/New Canaan: 1XRTT drops occur on the Merritt Parkway between Exit 15 and Exits 35 and 36 at Mile Markers 11. Most recent instance occurred on 01/24/2008.

Fairfield County, Stratford/Bridgeport Area on I-95: Approx. 50% of the time, more in the southbound direction than northbound, Verizon 1XRTT Express Network connections drop and reset to the "Ready" mode approx 4 miles south of "The Docks" shopping a rea, generally 1 mile or less before the Bridgeport Bridge where I-95 crosses into Bridgeport proper. These aren't the "worst" kind of drops where the connection hangs and requires a complete shutdown of the laptop (and fortunately there is a rest area ju st south of Bridgeport where one can pull over and re-start the connection and your file transfer!) but it is nevertheless a pain and one of the Express Network drops which can't be explained away as a coverage issue since it is in an area with generally very good coverage. 06/12/2003

Litchfield County, Kent: Drops occur just west of JCT of US-7 and CT-341 just before entering the state of New York. Most recent instance occurred on 07/19/2010.

Litchfield County, Litchfield: Drops occur on CT-341 approximately three or four miles west of US-202. Coverage does not resume until the JCT of CT-341 and CT-45. Most recent instance occurred on 10/15/2009.

Litchfield County, Bull's Bridge: On US-7 approximately one mile north of the JCT of US-7 and CT-55, there is a series of S-shaped turns. In that area, Verizon coverage for both cellular and data will drop. Other than the problem at Bull's Bridge at U S-7, there appears to be uninterrupted coverage on US-7 from Norwalk all the way up to Great Barrington, Massachusetts. The only place that it drops is Bull's Bridge. If Verizon Wireless were to fix this drop area in Bull's Bridge, coverage would be conti nuous. Most recently observed on 07/18/2012.

Litchfield County, Salisbury: Drops occur on US-44 between the CT A-side/00119 system and the NY 00486 system even though coverage is very good on both sides. Coverage is excellent up to and including the point where the drop occurs at the top of the hill between Salisbury, CT and Middletown, NY. The problem is that there is no handoff between the 00119 and the 00486 systems in spite of very good coverage. Most recently observed on 07/18/2012.

New London County, North Stonington, I-95 South, just west of CT/RI line near exit 99: Data sessions via 1XRTT / Verizon Express Network deteriorate (hang) and then drop upon reaching the CT Welcome Center / Rest Stop. Verizon CDMA (digital) calls fre quently (but not always) transit between the RI 00028/B and the CT 00119/A but the data calls don't seem to make it and drop regularly. 06/06/2003

Tolland County, Union: I-84 at CT/MA line: Data sessions via 1XRTT/Express Network will drop by the first Mass exit along I-84 NB. A complete shut down of the Watcher software (Sierra Aircard-equipped laptop) is required with restart before a new conn ection can be established. Session almost always drops at Roy Roger's/Sbarro "rest" stop on NB I-84 (atypical, excellent FRESH roast beef at the Roy's there!). Reported 01/12/2003, no resolution as of yet.

Florida

Brevard County, Cocoa Beach area: Connection is lost while traveling on US-192 at the JCT of I-95 (Mile Marker 176), which is just south of Coco Beach. Problem occurred on 01/31/2004.

Nassau County, Jacksonville, I-95: The 1XRTT signal drops heading northbound at the Florida and Georgia state line (and occasionally in the southbound direction as well, see below). Most recent instance occurred on 03/25/2005, it was reported to Verizon on 03/31/2005. It was noted on 04/09/2005 that the signal drops occur going southbound as well. Verizon has been updated about this but the initial call revealed that this is "a dead area and nothing can be done" despite the fact that coverage is very good right on either side of the state line. Last occurred on 03/12/2006

Palm Beach County, Boca Raton: EvDO drops occur near the Royal Palm Plaza despite having five bars worth of coverage. Drops occurred while using Windows 2000 as well as Windows XP environments. Most recent instance occurred 01/12/2006.

Georgia

Glyn County, Brunswick, I-95: 1XRTT abruptly disconnects heading northbound on I-95 between Mile Marker 38 and Mile Marker 45. Last occurred on 12/23/2004, reported to Verizon on 03/31/2005, no disposition as of yet.

Maryland

Frederick County, Myersville: Drops occur while driving on I-70 at about Mile Marker 43 (approximately a mile and a half west of the overpass over Hollow Rd), while entering the Verizon system that covers Hagerstown. Data calls initiated in the US Cel lular system will drop while driving east on I-70 before entering the Frederick/00018 system. Most recent instance occurred on 09/24/2012.

Harford County, Darlington: US-1, approximately 2 miles south of the Conowingo Dam, calls quickly lose any degree of throughput and over 75% of the time the connection to Verizon's data network drops. This is more problematic with EvDO service (drops nearly 100% of the time) as compared to 1XRTT (which drops around 50% of the time), but both regularly experience service difficulties and drops in that area (the general area surrounding the Conowingo Dam has very poor Verizon digital coverage, and thus 1X/EvDO also suffers from the adverse effects of the deficient coverage). However, as of 11/08/2009, drops occur when driving on US-1 in the general area of the dam on both EvDO service as well as 1XRTT. Last occurred: 03/08/2007.

Howard County, Columbia: EvDO service drops between Mile Marker 37 and 36 on I-95, which is not far from the intersection of MD 32. 1XRTT service is unaffected and maintains a connection from Washington, DC to Havre de Grace without any problems. Last occurred 10/12/2006

Prince George's County, Beltsville: I-95 at Mile Marker 35, which is about halfway between I-695 (Baltimore Beltway) and I-495 (Washington Beltway), there is an EvDO drop. 1XRTT service is unaffected. Last occurred on 11/21/2006.

Massachusetts

Berkshire County, Savoy: At best scant coverage exists on MA-8A between the JCT of MA-116 and continuing all the way to VT-9 in the state of Vermont. Coverage remains scarce until slightly north of Coltrane and just south of VT-9. Most recent instance occurred on 05/23/2010.

Cheshire County, Fitzwilliam: No coverage exists on NH-12 starting from approximately two miles south of the JCT of NH-119 and heading approximately two miles north of there. This is likely an extended coverage area, the carrier for which is probably US Cellular. While crossing into the state, the phone will still be on Verizon Wireless for a while, after which comes the extended area system at the JCT of NH-119 and NH-12, at which time drops occur. If a call is then placed inside the extended system, drops will occur upon returning to a Verizon market. Calls do not hand off from one coverage area to another, and that�s a problem. Most recently observed on 07/08/2012.

Cape May County, Cape May area: On NJ-47 while heading north from Cape May at Mile Marker 9.7 the Verizon 1XRTT Express Network connection drops pretty suddenly and resets (to "Ready to Connect"). Also, along NJ-109, a number of dead areas (most of wh ich do NOT result in drops) near the JCT of US-9. 06/14/2003

Mercer County, Princeton: 1X and EvDO drops occur on NJ-31 at Mile Marker 12, which is approximately ten miles north of I-95, roughly four miles south of US-202 and about two miles south of the JCT of CTY-579 and NJ-31. All Verizon coverage is weak there and the area generally suffers from vestigial conflicts between the BAMS/00008 (S.Jersey/Philly) system ands the NY/NJ Metro/00022 system. Last observe d: 12/12/2006

Mercer County, Princeton: US-1 at Mile Marker 19, EvDO coverage drops in both directions while 1XRTT service remains connected for the entirety of US-1 in that area. Last observed: 05/12/2006

Mercer County, Trenton: EvDO coverage drops on the northbound transition of I-295 to eastbound transition of I-195. This is not an equipment problem as multiple EvDO cards have been tested, and it's not a coverage problem as the (slower) 1XRTT service works fine and doesn't drop. 05/12/2006

Middlesex County, Perth Amboy: Along road which goes under Outerbridge Crossing (perhaps related to the problems on the NY side, above), Verizon Express Network/1XRTT connections drop from 1 mile south of the bridge to about 2 miles north of it. The c onnection is reset, and it generally will not allow re-establishment until the JCT with US-1. The Express Network Service is generally unusable in that area since connections have a hard time establishing and will rarely maintain for more than 10 minutes. Cellular coverage is good there, but Verizon used to have digital sudden drops there as well a few years ago until it was remedied in the summer of 2001. Informally reported on 12/03/2 002, no resolution as of yet.

Sussex County, Sparta/NJ-15: Just north of I-80 on NJ-15 (1.5 miles), 1XRTT connections drop and the connection must be re-established. Further up, along NJ-15, near the PathMark supermarket and shopping area, Express Network/1XRTT connections are ver y tenuous, and will regularly just drop/reset and require that a re-connection (This is being typed in from outside the PathMark and the connection has dropped 3 times just editing this file! :( ). Pretty unusable around here. Never reported since the cellular coverage here is surprisingly poor for BAMS!.

New York

Columbia County, Austerlitz: Drops occur on the Taconic State Parkway, just south of the JCT with NY-203. Coverage is generally weak in the area. Most recent instance occurred on 03/15/2009.

Columbia County, Austerlitz: There is no coverage starting approximately four miles north of the JCT of NY-22 and NY-203. Most recent instance occurred on 05/23/2010.

Columbia County, Claverack: Drops occur right at the JCT of NY-23 on the Taconic State Parkway. Display never says no coverage exists but effectively none does. Most recent instance occurred on 08/08/2010.

Columbia County, Copake: At the JCT of NY-22 and CTY-7A, coverage drops while traveling northbound. There is no coverage for approximately eight miles north beyond the initial drop in Copake. Most recent instance occurred on 07/06/2008.

Columbia County, Copake: Coverage is very poor on NY-23 starting from a quarter of a mile east of the New York/Massachusetts border until approximately half a mile west of the JCT of MA-23 and US-7 in Massachusetts. This occurs when driving in either direction. Most recently observed on 07/19/2012.

Columbia County, Gallatin: The connection drops on the Taconic State Parkway at Mile Marker 70.8. It resumes upon reaching the rest area located at Mile Marker 75.6 in the vicinity of Lake Taghkanic State Park. Most recent instance occurred on 03/15/2 009.

Columbia County, Spencertown: No coverage exists between the Taconic State Parkway all the way to NY-22 and up about four or five miles past Austerlitz. However, coverage resumes in the vicinity of the JCT of NY-203 and NY-22, which is approximately f our miles east of Austerlitz. Most recent instance occurred on 08/08/2010.

Columbia County, Spencertown: Calls drop approximately one mile north of Rigor Hill Rd while driving on NY-203. There is no service at all and calls drop. Most recent instance occurred on 08/08/2010.

Dutchess County, Amenia: Coverage attentuates on NY-22 in Amenia and drops completely for most of the distance between Amenia to Millerton (JCT NY-22 and CTY-62). Most recent instance occurred on 07/06/2008.

Dutchess County, Amenia: Drops occur for no apparent reason while driving on NY-343 approximately half a mile east of the JCT of NY-343 and CTY-2. Most recently observed on 07/19/2012.

Nassau County, East Norwich: Drops occur on NY-106 between NY-25A and NY-25. Data connections simply shut down, even though there�s good coverage. Most recent instance occurred on 06/24/2009.

Nassau County, Laurel Hollow: "Data hangs" occur just east of Cove on NY-25A and slightly west of Cold Spring Rd. Most recent instance occurred on 01/29/2013.

Nassau County, Long Island, Glen Cove Rd: While traveling south (and occasionally north) along Glen Cove Rd., Express Network/1XRTT connections drop at the LIRR station (Greenvale?) to the west of Glen Cove Rd. This is a "Type 2" drop, e.g., the Watcher will show the connection is active but no data will pass through and new TCP/IP connections can't be initiated. Unlike "Type 3" drops, users *can* disconnect all open connections, then click on "Disconnect" on the Watcher, then close the Watcher, then re-start the Watcher and connect with it, and should be able to initiate new connections. (A Type 3 would probably require a reboot of the computer, so fortunately this is not one of those .) Reported to Verizon on 07/03/2003, no resolution as of yet. Most recent instance occurred on 06/23/2009.

New York County - Manhattan: 1XRTT connections drop at seemingly random intervals in the waiting room at Penn Station. Watcher will not disconnect, it will simply stop passing data. Most recent instance occurred on 10/18/2007, reported to Verizon on 08/03/2007, no resolution as of yet.

New York County - Manhattan: Drops occur while passing through the East River tubes which are utilized by Amtrak and the LIRR to access Penn Station. The connection works fine before entering the tube and will also work fine after exiting the tube, but the connection will while drop while passing through the tunnel. Most recent instance occurred on 03/18/2008, reported to Verizon on 09/21/2007, no resolution as of yet.

New York County - Manhattan: There is no coverage in the Park Ave tunnel of Metro North between 72nd St. and the opening of the tunnel near 104th. Most recent instance occurred on 02/18/2009.

New York County - Manhattan: 3G and 4G connections are very slow and often drop (>30% of the time in a given hour-long interval) on the Upper West Side along 74th. St between Broadway and Amsterdam Ave. In parciular, along 74th St. neat the "Big Apple Bank" building (most of which has been converted into luxury apartments), just north of the 72nd. St West Side IRT station. 3G 1XRTT and EvDO connections seems more robust and will drop less oftenm while 4G/LTE drops more regularly, perhaps in trying to switch "down" to 3G speeds (which, as noted here, are also affected here by sloew speeds and frequent drops). This is one of the weirded and generally bad sections in Verizon's (ex-NYNEX Mobile) Manhattan data service area and resembles the areas near the Hudson River and the problems with signal propogation from Jersey, although this area is not relatively close to the River nor are Jersey towers easily received here. Most recent instance occurred on 04/27/2014.

Orange County, Cornwall: Drops occur approximately one mile south of Continental Rd. Last instance occured on 07/17/2011.

Queens County - Queens: 1XRTT drops occur at Woodside Station. On occasion, the error message which is displayed subsequent to the drop is "cannot detect carrier". Most recent instance occurred on 10/17/2007.

Rensselaer County, Berlin: Coverage drops approximately five miles south of Berlin while traveling north on NY-22. There continues to be no coverage on NY-22 from that point, nor does coverage return in Berlin itself. The area of no coverage then cont inues for at least five miles further north along NY-22 until the JCT of NY-2 in the town of Petersburg (there may be no coverage further north of this point, however we did not have an opportunity to test it). Most recent instance occurred on 07/06/2008.

Rockland County: There is poor coverage on the Palisades Interstate Parkway between Exit 16 and Exit 19 (near the Bear Mountain Bridge). Most recent instance occurred on 07/11/2011.

Westchester County, Briarcliff Manor, NY-9A: Express Network drops on NY-9A heading south up the hill towards Briarcliff Manor, and by JCT NY-133 is unusable (drops by that point and can not be re-established). Connection cannot be re-established unti l the JCT of NY-9A and NY-100 (where they merge into one road southbound), sometimes it cannot be re-established until JCT NY-117. Pretty poor coverage for a significant patch of area in Westco., probably make a good way to get out of a service contract i f a customer had an expectation of use in that area. Not reported; we gave up telling them about these problems (mainly in the NY system) since they (a) don't seem to care and (b) don't do anything to fix them. 02/22/2003, no resolution as of yet.

Westchester County, Rye: Data drops occur on I-95 at Mile Marker 12 in the vicinity the Rye Playland connector. Most recent instance occurred on 09/20/2009.

Westchester County, Vista: Drops occur while driving from New Canaan, CT into Vista, NY on CT-123/NY-123. While crossing into the state of New York, the service drops. Most recent instance occurred on 08/24/2009.

Westchester County, White Plains: Data drops and generally poor coverage occur on the Hutchinson River Parkway within a mile either way of Exit 22 (which is Old White Plains Rd.), slightly north of Larchmont. Within about a mile either way of Exit 22, Watcher shows no coverage at all. However, if one drives fast enough (at normal highway speeds) one can traverse the "dear air" area rapidly enough to avoid the idle time out, but at slower speeds (ie, such as being stuck in traffic) 1XRTT sessions will drop. Most recent instance occurred on 10/16/2007.

Westchester County, White Plains: Drops occur just south of the North White Plains train station. The connection is stable at the Valhalla station which precedes the North White Plains station when traveling south. Just south of the Valhalla station i s where the connection will drop. Most recent instance occurred on 11/27/2006.

Pennsylvania

Bedford County, Breezewood: No coverage exists on US-522 near the JCT of PA-655. The lack of coverage continues on US-522 until south of US-30. Most recent instance 04/26/2010.

Bucks County, Eddington: Drops occur about a 1.5 miles north of JCT of I-95 and PA-132 near Exit 37, EvDO service drops, while 1XRTT service works perfectly all the way from south of Trenton to Philadelphia (on I-95). Last occurred on 11/21/2006.

Chester County: Drops occur just north of the Pennsylvania/Maryland state line when driving on US-1. Most recent instance occurred on 11/05/2009.

Delaware County, Chester: Data "hangs" occur when driving on US-322 at the border of New Jersey and Pennsylvania. The transfer of data will stop even though the connection itself remains open. Most recent instance occurred on 04/02/2009.

Delaware County, Marcus Hook: At the border New Jersey of Pennsylvania while heading south on I-95 right where the beltway of I-495 breaks off of I-95, EvDO service will on occasion drop. Last occurred on 11/21/2006.

Delaware County, Marcus Hook: EvDO drops occur while heading north on I-95 at the Delaware/Pennsylvania border. Connections won't just drop from EvDO to 1XRTT, they completely drop out altogether. This is similar to the drops which occur in the same g eneral area but a few miles to the south while traveling southbound. No similar drops occur with 1XRTT. Last observed: 05/15/2006.

Delaware County, St. Davids/Wayne PA: Verizon Express Network/1XRTT drops occur on PA-252 while heading south of St. David's road towards JCT PA-3. Driving south on PA-252, south of the St. David's road overpass, the Watcher shows "Connection lost" an d resets approx. halfway between the St. Davids overpass and PA-3. Reported 05/30/2003, no resolution as of yet.

Franklin County, I-81 Rest Area, Chambersburg Area: 1X/EvDO/LTE calls drop just north of the MD/PA state line heading north. Data sessions initiated in the US Cellular/01794 system (south of the MD/PA line) or which transited into the 01794 system are dropped upon crossing from MD to PA and entering into the Verizon/ex-Alltel 00096 (SID) service area. However, data sessions which are initiated in the 00096 (or elsewhere) market do NOT drop heading southwards on I-81 from PA into MD. Last observed 04/24/2014.

Fulton County, Belfast: Drops occur on US-522 while driving north and away from the JCT of PA-655 and after the point where US-522 splits off from PA-655 at a very steep U-turn/horse shoe turn. That area has very poor Verizon coverage on both voice an d data. Most recent instance occurred on 08/19/2012.

Fulton County, McConnellsburg: Drops occur while driving on US-30 just east of the JCT with US-522 over while proceeding up the hill toward the Tuscarora Summit. Most recently observed on 07/23/2012.

Philadelphia County, Philadelphia: Drops occur on I-95 near the JCT of I-76/Walt Whitman bridge. Data connections will become erratic connections and disconnections will follow. Most recent instance occurred on 08/31/2004, reported to Verizon on 09/01 /2004, no resolution as of yet.

Rhode Island

Kent County, Warwick Area: I-95 heading south, approx. 1 mile South of JCT I-295 and approx 1 mile north of JCT RI-4 (left exit/split). Verizon Express Network data connection suddenly drops, and requires a reset of the Watcher software in order to pa ss data again (a simple re-connect will not work here). 06/07/2003

Virginia

Clarke County, Berryville: Drops occur while driving north on I-81 at or slightly after the Virginia/West Virginia line. All data connections seem to drop while transitioning from the Verizon Wireless system to the US Cellular system. This incident af fects both cellular and data connections; all will drop. Most recent instance occurred on 02/10/2013.

Clarke County, Berryville: Drops occur while driving on US-340 just north of the JCT with VA-7, slightly east of I-81 and just south of the border with West Virginia. Sessions initiated in West Virginia and carried across the state line into Virginia will drop approximately half a mile north of the JCT of US-340 and VA-7. The user can immediately reconnect when the drops occur (in other words, there appears to be good coverage through out the area). Most recent instance occurred on 08/20/2007.

Richmond: While driving west on I-64 away from Richmond, data stops at approximately Mile Marker 138. The data connection does not drop but SSH, Telnet and other connections stop passing data. This is possibly a handoff issue. When driving west on I-6 4, motorists will exit the Richmond system somewhere near Mile Marker 138. At that time, although Watcher says the connection is still active, data is no longer passed. Most recent instance occurred on 02/28/2010.

Washington DC Metro: Although there is coverage on the Orange Line at Virginia Square/George Mason University, connections cannot be made. Most recent instance occurred on 02/24/2011.

Washington DC Metro: Coverage does not exist at Farragut West station on the Orange/Blue lines. Most recently observed on 03/05/2013.

Washington DC Metro

Washington DC Metro: Drops occur on the DC Metro Red Line between Twin Brook and White Flint. Most recent instance occurred on 03/31/2009.

Washington DC Metro: Drops occur on the DC Metro Red Line between White Flint and Grosvenor. Most recent instance occurred on 02/26/2009.

Washington DC Metro: Drops occur on the DC Metro Red Line between Grosvenor and Medical Center. However, the drops are not as severe or prolonged as they have been in the past. Most recent instance occurred on 06/01/2009.

Washington DC Metro: Drops occur on the DC Metro Red Line between Medical Center and Bethesda and it coincides with certain 1XRTT drops. However, the drops are not as severe or prolonged as they have been in the past. Most recent instance occurred on 06/01/2009.

Washington DC Metro: Coverage at Bethesda station is generally poor. Most recently observed on 06/01/2009.

Washington DC Metro: Drops occur on the DC Metro Red Line between Bethesda and Friendship Heights. Most recent instance occurred on 06/01/2009.

Washington DC Metro: Calls drop while riding down the northern escalators at Friendship Heights station riding from the ground floor downstairs. Most recent instance occurred on 08/03/2010.

Washington DC Metro: Calls drop on the Red Line between just north of Woodley Park. Most recent instance occurred on 08/23/2010.

Washington DC Metro: Coverage does not exist at Farragut North station on the Red Line. Although it was generally known that drops occur between Farragut North and DuPont Circle stations, the lack of coverage at this station is a new phenomenon. Tyler , a representative from Verizon Wireless, reported on 02/11/2013 that Verizon technicians will investigate this issue and attempt to determine the cause of it. Most recent instance occurred on 03/05/2013.

Washington DC Metro: No coverage exists between DuPont Circle and Farragut North on the Red Line. The drop occurs just north of Farragut North station, and the lack of coverage extends beyond DuPont Circle station. Most recent instance occurred on 03/ 31/2009.

Washington DC Metro: Coverage does not exist on the Red Line between Farragut North and just north of Metro Center. Most recent instance occurred on 12/22/2009.

Washington DC Metro: No coverage exists at Gallery Place station on the western section of the upper level platform. (As of 03/19/2009, coverage seems to have improved and may indeed be working. Pending further tests, this incident may be moved to th e Corrected Items section.)

Washington DC Metro: Drops occur on the DC Metro Red Line between Friendship Heights and Tenleytown and Van Ness. Most recent instance occurred on 03/31/2009.

Washington DC Metro: Drops occur on the DC Metro Red Line between Tenleytown and Van Ness. Most recent instance occurred on 05/30/2008.

Washington DC Metro: Drops occur on the DC Metro Red Line between Van Ness and Cleveland Park in both directions just north of the Cleveland Park station. Most recent instance occurred on 05/30/2008.

Washington DC Metro: Calls initiated before Archives Navy Memorial on the Yellow Line (running concurrently with the Green) will drop while going south towards L'Enfant Plaza midway between the two stations. Most recent instance occurred on 06/16/2008 .

Washington DC Metro: Data coverage is slow and lossy at Gallery Place station where the Yellow and Green lines on the lower level meet the Red line on the upper level. Most recent instance occurred on 02/26/2009.

Washington DC Metro: On the Yellow and Green Lines Georgia Ave and Columbia Heights station, no coverage exists in the tunnels. Most recent instance occurred on 10/06/2011.

Washington DC Metro: No coverage exists on the Blue Line between Capitol South through Federal Center and continuing to L�Enfant Plaza. Coverage resumes at L�Enfant Plaza. Most recent instance occurred on 07/14/2009.

Washington DC Metro: Calls drop on the Blue Line while entering the tunnel which leads to the Rosslyn station while heading northbound from the Arlington Cemetery station. It is not known if the drop occurs while traveling on the southbound side. Most recent instance occurred on 07/13/2008.

Washington DC Metro: Drops occur between the Pentagon Station and Arlington on the Blue Line. Somewhere in the tunnel north of the Pentagon station, calls drop before exiting the tunnel headed towards Arlington station. Most recent instance occurred o n 07/13/2008.

Washington DC Metro: There is no service on the Yellow line both south of Pentagon and north of Pentagon. Most recent instance occurred on 11/05/2009.

Washington DC Metro: Drops occur on the Yellow and Blue Lines between Pentagon and Pentagon City (which could be due to construction work). Most recent instance occurred on 11/16/2009.

Washington DC: I-495 about 2.5 to 3 miles north of Georgia Ave (MD-97), EvDO service will drop, while 1XRTT remains fine. Last occurred 11/20/2006.

EvDO Cycle areas

"Cycle Areas", as per the discussion in the General/Background Section, area not drops per se, that is, the connection is not torn down requiring a manual re-connect, but instead an area where the transition from 1XRTT to/from EvDO does not occur "smoothly", causing connections to "hang" either for more than a momentary period (at best) or to completely time out (at worst). In such cases, telnet/SSH/SSL and other ongoing connections will need to be re-established, as well as downloads, streaming audio and video, etc. Again, the EvDO/1XRTT software does not disconnect, but the extended delay in cycling "up" from 1XRTT to EvDO or cycling "down" from EvDO to 1XRTT, during which time data does not seem to pass, results in established TCP/IP connections being lost.

Maryland

NW Baltimore area: While driving south on the western side of the Baltimore Beltway, EvDO drops to the slower 1XRTT service in the vicinity of the JCT with I-83. The EvDO speed will not be reacquired during the entire trip to Washington (one of the two initial EvDO markets so there is certainly EvDO coverage there). After arriving in Washington, D.C., EvDO will not come back up. Disconnecting the session and restarting immediately results in a connection at EvDO speeds, which indicates it is very difficult to "step up" from 1X to EvDO in this area despite extremely good coverage. Last occurred 12/10/2006.

Anne Arundel County, Annapolis: Sandy Point Beach just north of the Annapolis, right at the Bay Bridge where the bridge comes to the western shore of Chesapeake Bay. The coverage almost constantly switches between back and forth between EvDO and 1XRTT. The 1XRTT service was fine, but the EvDO service was inconsistent at best and completely out of commission at worst. The constant "flip-flops" were making the system completely unusable. Most recent instance occurred on 09/14/2005, reported to Verizon on 09/15/2005.

Middlesex County, New Brunswick: Traveling on US-1, EvDO connections will properly drop to 1XRTT generally south of the Metropark area, but will not come back up to EvDO until considerably south of Trenton, even though there is adequate EvDO coverage in areas in between. Additionally, there are significant delays in connectivity (periods where even though the Watcher application indicates an active connection no data can be passed) as the Watcher searches for EvDO service. Last observed: 12/23/2005.

Jefferson County, Charlestown: No service exists starting at the JCT with WV-9 and US-340 all the way to WV-9 and I-81 and from I-81 all the way to Pennsylvania. The service provider in this area is US Cellular. Most recently observed on 06/24/2012.

While driving on I-81 right at the VA/West VA line, data connections established while on the VA side will drop while passing over the state line into West Virginia. Interestingly, once the connection has been reestablished after the drop, it will con tinue on I-81 all the way north from the West Virginia border and on into Maryland and back into Frederick on I-81 and then I-70. The connection will even go into Washington DC from I-70 to the beltway. Most recent instance occurred on 02/28/2010.

Corrected Problems

The following were problem drop areas but have apparently been corrected and/or no longer suffer from regular/repeated drops.

Connecticut

Fairfield County, Danbury: I-84 WB at the CT/NY line: Express network Eastbound drop reported 12/18/2002 and was finally resolved by 01/02/2007.

Mercer County, Robbinsville: New Jersey Turnpike between Exits 8 and 7A: A "Type 3" (complete system reboot required) generally occurs here. Since this is a "hung connection drop", it is impossible to tell exactly where the drop occurs, but it is approximately 4 miles north of Exit 7A (JCT I-195). Noted 06/15/2003. (For a complete discussion of this drop, see the June 16, 2003 update).

New York County (Manhattan): 1XRTT drops and resets driving north on 3rd Ave at 110th St. 06/06/2003

New York County (Manhattan): After the 1XRTT drop at 3rd Ave and 110th St (on the way to the Harlem River Drive), the user cannot reconnect. A few blocks north on the Harlem River Driver is where the user can finally re-establish the session which dro ps for no reason upon passing 3rd Ave and 110th. St. 06/06/2003

Richmond County, Staten Island, Outerbridge Crossing/NY-440: Express Network Connection drops 90% of the time on trips from Perth Amboy, NJ heading east (north) along NJ/NY-440. Upon arrival at the PANY/NJ (rip-off!) toll-plaza is passed, connection d rops. On the approx 10% of the time the connection does not drop, half of those times it will drop further north along NY-440 near just before the Fresh Kills Land Fill and the first exit on NY-440 north of the bridge. Reported to Verizon in Bedminster on 11/29/2002, no resolution as of yet.

I-95S at Rye Playland Parkway Exit: Verizon 1XRTT Express Network data service drops regularly after transitioning from the CT 00119/A system to the NY 00022/B system. Calls can be "pulled" into the NY system for a mile or two, but the Verizon data se rvice will drop by the time upon arrival at the Playland Parkway overpass. (Note that non-data cellular voice calls also don't seem to hold from CT to NY, although they make it a bit further, all the way to Larchmont. This is true for CT 00119/A to NY 000 25/A (analog) handoffs as well as CT 00119/A to NY 00022/B digital intra-Verizon/BAMS handoffs, although sometimes the latter will work all the way to NYC (rarely, though). 06/06/2003

Westchester County, Greenburgh/Mount Pleasant, Taconic State Parkway near I-287: Verizon Express Network/1XRTT drops just south of JCT I-287 near JCT NY-100C. Data connection needs to be completely reset and will generally not establish for at least 2 miles (or 2 minutes of driving?) south of where it drops. Reported to Verizon on 11/29/2002, no resolution as of yet.

Westchester County, Elmsford, Saw Mill River Parkway near I-287: Verizon Express Network/1XRTT drops just south of JCT I-287 near golf course of NB side, approx 3/4 of a mile south of the I-87S to SB SMP ramp with a "STOP" sign. Connection will genera lly not re-establish until Farragut Rd., a few miles down the SMP from where it drops. Reported to Verizon on 11/29/2002, no resolution as of yet.

Westchester County, Yonkers: Drops occur while driving on the Sawmill River Parkway just north of the JCT with the Sawmill River Parkway. After proceeding up and then back down a hill, drops will occur immediately before the first traffic light. Most recently observed on 01/01/2013.

Dauphin County, Harrisburg: A drop used to occur regularly while traveling on I-83 north and crossing from the DC 00018 market into the Harrisburg 00096 market. The connection would function properly but while approaching the JCT of I-83 and PA-182, the 1XRTT service would "hang". It was possible to ping some sites, but data could not pass through. After disconnecting and reconnecting, the same IP was assigned and everything worked fine. This seems to have been fixed. Most recent successful test occu rred on 07/20/2006.

Windham County, Brattleboro: Calls drop on I-91 at Mile Marker 5 which is just south of the rest area. Most recent instance occurred on 10/13/2009. As of January 2012, and likely even before, the 00313 system now displays a Verizon/Boston 00028 SID an d seems to have been fully incorporated into the Boston system. No handoff problems were experienced at the Vermont/Mass state line, and all issues in that area pertaining to Verizon have been fixed.

Washington DC Metro: Clarendon station on the DC Metro Orange Line -- which previously had both voice and data coverage as of 05/20/2008 -- seems to have suffered a diminishment thereof as there are only a limited number of points within the station w here a signal can be acquired. has no Verizon cellular or data coverage. A paucity of coverage continues heading eastward until approximately halfway between Clarendon and Court House Stations, at which point coverage resumes. Most recent instance occurre d on 05/21/2008. As of 07/13/2008, this appears to have been corrected.

Washington DC Metro: Drops occur while riding on the Orange Line between Rosslyn station and Courthouse station. Most recent instance occurred on 12/18/2008. Appears to have been corrected as of 07/27/2010.

Washington DC Metro: Drops occur on the Orange Line (running concurrently with the Blue) between Foggy Bottom and McPherson West. Calls initiated at Foggy Bottom drop while entering McPherson West station. Most recent instance occurred 06/16/2008. App ears to have been corrected as of 07/27/2010.

Washington DC Metro: Drops occur while riding on the Orange Line (running concurrently with the Blue). While traveling either eastbound or westbound in the tube which goes under the Potomac River between Foggy Bottom and Rosslyn, drops occur closer to the Rosslyn station than to the Foggy Bottom/GWU station. Most recent instance occurred on 10/08/2009. Appears to have been corrected as of 07/27/2010.

Washington DC Metro: Drops occur on the Orange and Blue lines at the Potomac tubes just east of Rosslyn when travelling both eastbound and westbound. Most recent instance occurred on 11/05/2009. Appears to have been corrected as of 07/27/2010.

Washington DC Metro: No coverage exists at the DuPont Circle station on the Red Line. Even though it is well known that drops occur between DuPont Circle and Farragut North stations, the utter lack of coverage at this station is a new phenomenon. Tyle r, a representative from Verizon Wireless, reported on 02/11/2013 that Verizon technicians will investigate this issue and attempt to determine the cause of it. Most recent instance occurred on 02/11/2013. This seems to have been corrected as of 02/27/201 3.

Contacting WirelessNotes.org

We may be reached via:

E-Mail: Please mail to [email protected] , removing the first three letters of the alphabet from the name/address.

Web-based Interface.

Phone: +1 (510) 315-2750 during Pacific Business Hours.