Wireless Notes -- Verizon Wireless Data Drops: 1XRTT/EvDO (3G) and 4G/LTE Coverage Problems, Drops, and Service Issues List Verizon 
Wireless Data Drops List Banner; the page details Verizon Wireless Data 
drops and coverage issues on Verizon's 1XRTT, EvDO, 3G and 4G data 
networks

An Updated List of Verizon Wireless Data Drops on its 3G Express Network (1XRTT/EvDO) and 4G/LTE Data Networks and other Verizon Wireless Data Service Difficulties and Issues


Last Update: 08/05/2017

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 areas in the US.

[ Wirelessnotes Main | Interpage | Cellular Carrier Comparison | 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 Dropped Call List | Sprint Dropped Call List | Nextel Dropped Call List | T-Mobile Dropped Call List | Disclaimer | Contact Wirelessnotes.org ]


      Interpage OutVoice Text-to-Speech and
WAV voice broadcast and messaging service promitional link. Click here for
additional details on the Interpage OutVoice service. Interpage DirectPage service to
replace or augment numeric pages by sending numeric pages to
cellphones/SMS, multiple pagers, email, voice and fax. Click here for
additional details. Interpage Voicemail service which
offers notification of hangup calls and all other messages received with
CallerID to cellphones, SMS, email and pagers, and will even send a
voice/WAV file to your phone or email and call you with your new
messages!. Click here for details.


General/Background:

Classification of 3G/1XRTT/EvDO and 4G/LTE Drops: We've identified three types of drops with Verizon's 3G/4G Data Network Services, which are:

  • Type 1: Connection DROPS, all data sessions (Web, FTP, Telnet, etc.) are lost. Sierra Wireless Watcher or Airprime 5520 software says "Ready to Connect" about 30 seconds after connection drops. One can hit the "Connect" button and the service will re-connect. If a given FTP or Telnet session is restarted, the Watcher (or other connection software) will subsequently re-connect. These are the least annoying drops and occur most often (approx 65% of the time).
  • Type 2: Connection HANGS (not drops), all data sessions can not move any data through the Verizon 1XRTT network. There is NO WAY to tell exactly when or where these occur, since the Watcher does NOT reset - it just sits there, in a "hung" state, not indicating that anything is wrong other than that the "RX" and "TX" data throughput indicators do not increment (i.e., no data is going through). If a subscriber quits the Watcher, disconnects all TCP/IP sessions (or rather close them; they all have already been disconnected!) and then re-start the Watcher, users should be able to re-start their FTP and other TCP/IP sessions. These are somewhat more annoying and require a lot more work to restore the connection (I.E., you data customers to close and re-start everything).
  • Type 3: Connection HANGS as above (Type 2), all data sessions are lost and cannot move any data, and the Watcher does not indicate there is any problem other than the TX and RX indicators not incrementing. However, ONE CANNOT QUIT OUT OF THE WATCHER!! Clicking on "Disconnect" does nothing! Additionally, using the Task Manager (via control-alt-delete) to stop/kill the Watcher process eventually works, but when the Watcher is restarted, all it does is indicate "Searching for Aircard 555 modem" (or whatever the device is which is being used (which again in turn cannot be stopped/killed). Going again to the task manager and trying to kill it will again eventually work, and the "Watcher" process will die, but, as like in the first instance, when the Watcher is once again restarted it still cannot find the modem. Removing the Aircard 555 and then re-inserting it won't work either. The laptop MUST be rebooted and started de novo all over -- something not easy to do too well in a mobile environment, and a general pain regardless in ANY environment.
  • For a complete discussion of these 3 types of drops, see the full June 15, 2003 Update

    A number of other problems which do not pertain to drops/poor coverage, but are notably 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 people 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, and require a manual restart of the data connection software (such as Sierra wireless's old "Watcher", or Verizon's "Connection Manager"). As a result, if data is being transfered, uploaded, or downloaded (such as via FTP or a web-based graphical equivalent) at the time the automatic 24-hour disconnection takes place, all data sent during the file transfer will be lost. Not only does this waste time and cause duplicative efforts, but newer Verizon data plans generally don't offer unlimited data, and each subsequent effort to regain data after a 24-hour reset will subtract from a given customer's data allowance on metered accounts. (For example, and FTP session to transfer large files is started at 23 hours since the Verizon data session was started, and at 24 hours it is automatically disconnected. In order to properly send the files, the a new data session will need to be opened, and the hour's worth of data initially sent will have to be re-sent, using up more data than would have been needed if Verizon didn't force the disconnect after 24 hours.)

    Verizon can prevent this 24-hour disconnect 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 something), 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 Verizon doesn'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 1 to 2 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 there seems to be no reason why Verizon has such a short timeout period. Obviously loss of coverage in a given area is not the subscriber's "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.)

  • Voice-over-IP/SIP Blocking/Interference: A more recent problem, which surfaced in late 2010 or so, and has been reported in a number of online fora (including OnSIP and Howard Forums), is Verizon's use of an Application Layer Gateway for SIP telephony over its wireless data network. Generally, Application Layer Gateways (ALGs) are problematic for voice-over-IP/SIP, and Verizon's reported/suspected use of an ALG interferes with SIP "register" requests (used to set up a SIP connection to place and receive calls). It appears that different devices and software clients (virtual phones used to place calls from a laptop or smartphone) are affected, and more often than not the problem affects tethering of SIP equipment (such as using a phone as a hotspot and placing calls from a softphone on a laptop tethered to the phone). It's unclear why Verizon has implemented this -- some posts claim they don't want people competing for voice carriage with them, others posit that the use of an ALG was based on good intentions but sloppily implemented, resulting in the ongoing blocking problems. We've tested a number of SIP clients (devices, softphones, etc.) and we've had very limited success in terms of connecting and placing/receiving calls using Verizon Wireless Data; we tested 1XRTT, EvDO, and 4G/LTE, all of which had problems and only worked with a very limited number of softphones and other equipment. The same clients/equipment had (and continue to) have no problem whatsoever with AT&T, Sprint, and T-Mobile, yet the issue still persists with Verizon Wireless' data service as of December 2016. This is certainly something Verizon needs to remedy, both for the convenience and utility of all Verizon data customers, as well as to remove any suspicion that they are trying to block or adversely affect certain types of data and services.
  • Unlike the 1XRTT/EvDO/3G/4G/LTE drop issues in the list section, below, the (above) easily remedied 24-hour disconnects, short timeout window issues, overpriced Static IPs, and more recent SIP blocking/ALG problems are not covered on the drop list -- they are systemic throughout the Verizon data network, so there is no need to iterate them on a state-by-state basis; they happen everywhere all the time. They are noted here as they are significant issues which one would think Verizon would, as a company purportedly devoted to the highest standards of customer service and satisfaction, on their own volition wish to immediately remedy, but which Verizon has instead allowed to continue as of the most current update date of this list.



    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.

    And, similarly to the EvDO issues when it was introduced in 2006 or so, 4G/LTE suffers similar "cycle" issues even in 2015, where phones and data devices repeatedly re-cycle between 3G and 4G coverage; in many cases it is faster overall and better throughput it provided by setting a Verizon phone or mobile device to "3G only" in areas which straddle 4G/3G coverage demarcation lines rather than to have the phone or device continuously scan attempt to connect to 4G coverage, only to rapidly fall back to 3G instead.

    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.


    Criteria:

    The criteria for a drop being "worthy" :) of getting posted are:

  • Drop occurs at least 3 times traveling in the same direction (i.e., Eastbound on a given road)
  • Drops occur over a period of more than a month, e.g., if you notice a drop on 05/01/2002 it still needs to drop on 06/01/2002 for it to be posted.
  • Drops are moving drops or drops/resets (for Express Network/1XRTT) in areas of strong coverage, i.e., these aren't "I can't get coverage when I sit in my living room corner" situations, but areas where there is otherwise good coverage and the phone just for no apparent reason drops. (This isn't just for motorists; we've also had problems on Amtrak and commuter rail services, etc.)
  • Drops are in areas of otherwise good coverage, e.g., the drops listed are not in areas where Verizon (analog/digital voice or 1XRTT Data) has/have no coverage. Thus, there are no posts saying "My Verizon cell phone (or Express Network data connection) dropped on I-91 crossing the MA/VT line" since Verizon doesn't cover there, yet.
  • Cycle Drops: Not exactly a drop, but an area of transition between 1XRTT (slower speed) and EvDO/EvDO Rev.A (faster speeds). See section immediately below for details.
  • In terms of EvDO "Cycle Areas" or "Cycle Drops", we have noticed three general categories of EvDO drop and service interruptions, and thus the criteria for an EvDO issue to be included in the EvDO-specific list are listed below:
  • 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 York City).

    Certain subway systems (such as DC Metro) are organized by line and are considered subcategories within the primary city in which 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 Wireless 1XRTT/EvDO (3G) and LTE (4G) Data Drop List, by State

    Connecticut

  • Fairfield County, Danbury: Verizon's 1X, EVDO and 4G data services drop while driving along I-84 at the NY/CT State Line approximately 95% of the time. It appears handoffs between the NY/00022/B system and the CT/00119/A system are not being properly handled. This was a problem at the outset of 1XRTT, which was then fixed a few years later (2004 or so), and has as of 2014 become a problem again at most CT/A to other Verizon/B systems, such as along I-95 and the Merritt (00022 to 00119), and to the Boston/RI/00028 system from I-95, US-6, I-395 RI Connector (CT-695), CT/RI-138, etc. Problem seems to happen both ways (ie, NY -> CT and CT -> NY), but more often heading west from CT to NY, where calls drop around the JCT with I-684 (generally not speeding to avoid usual NYS revenue collection/speed traps in the median between the CT line and I-684, so after about 4 minutes into New York). Last observed: 03/22/2017.
  • Fairfield County, Danbury: Verizon data sessions drop approximately 75% of the time along US-7 south in the vicinity of the Federal Road exit on the US-7 freeway. This is generally where the old Litchfield (only) 01101/A system handed off to the Metro Mobile/BAMS 00119/A system before BAMS acquired it and changed the SID to 00119. Last observed: 08/10/2015
  • Fairfield County, Darien: Verizon Wireless data 1XRTT/EvDO calls drop approx. 50% of the time northbound along I-95 near Exit 10/Noroton Heights, and around 25% of the time southbound in the same area. Last observed: 03/01/2015.
  • Fairfield County, Fairfield: Verizon Wireless 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 Verizon Data/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 1XRTT 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 and very annoying problem southbound on I-95. 06/14/2003.
  • Fairfield County, Greenwich, CT and Purchase, NY state line along the Merritt/Hutch parkways, in both directions. 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 (or in the reverse northbound direction from 00022 to 00119), generally as the Hutch passes over I-684 southbound (00119 to 00022) or after the Greenwich service plaza northbound (00022 to 00119). This occurs generally in the same area where 800 MhZ (only, no 1900 or other newer frequency-capable) cellular phones drop (see the Verizon Cellular/Voice drops list for details). Last observed: 02/22/2016.
  • Fairfield County, Ridgefield: Verizon 1XRTT/EvDO and 4G data calls drop along CT-35 near the junction with Ridgefield Hill Road. The drop location is near the CT/NY border, and thus straddles the NY/00022 and the CT and Western Mass/00119 system, and old Verizon delineation which results in numerous data (and voice) drops where other carriers have little to no problems along the NY/CT state line. Indeed, the problems Verizon generally and continues to have in terms of inter-system handoffs appear unique to Verizon and vestiges of when market seggregation was in some part required by Federal law, requirements which today are no longer present. In this case, Verizon data calls appear to drop where the NY/00022 and CT/00119 systems should hand off, but don't, which results in the given drop. Most recent instance occurred on 09/26/2015.
  • Fairfield County, Stamford/New Canaan: Verizon 1XRTT/3G session 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 area, 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 just 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 generallyvery good coverage. 06/12/2003
  • 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 US-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 continuous. Most recently observed on 07/18/2012.
  • Litchfield County, Kent: Verizon Wireless data 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, Lakeville: Verizon Wireless data drops (calls/data sessions) occur along CT-41 (a generally north-south route from Sharon to Great Barrington, MA) at the JCT with CT-112 (a generally east-west road bypassing the towns along US-44 to the north), while CT-41 passes through the Hotchkiss School, which lies north of CT-41. Data (and voice) service is passable along most of CT-41, and seems to be serviced via the NY towers just to the west (SID 00486, more recently merged with the Albany/00078 system), and the drops may occur as handoffs are attempted to the CT/00119 system. In any case, heading north past the intersection with CT-112, Verizon data calls will drop near the student crosswalk over CT-41 for the Hotchkiss School, in an area of poor coverage, and resume approximately a mile further north. Most recent instance observed: 09/10/2016.
  • Litchfield County, Lime Rock: Verizon Wireless data calls drop along CT-112 in a number of locations and Verizon Wireless has generally poor service between the JCT of CT-112 to the east at US-7 (where coverage is generally good, especially northward towards Canaan/North Canaan, CT and Mass) and CT-41 (and then westwards to US-44). Calls along CT-112 drop regularly if there is even any coverage, and overall, Verizon's service along CT-112 in the area is very poor and unreliable. While this may be due to coverage along the US-7 corridor being "handled" by Verizon's CT/W. Mass/"A"/00119 system and coverage along the somewhat parallel CT-41 (to the west) being handled by the Verizon/Albany/"B"/00078 system and the usual handoff (or lack thereof!) problems between these two vestigal systems, the coverage in and of itself is so poor along CT-112 ("No Svc" shows up regularly, for both Verizon voice and data calls), that even if handoffs were properly working everywhere between Verizon's 00119 and 00078 systems, calls would likely still drop along CT-112 due to the generally poor coverage there. Most recent instance occurred on 07/20/2015.
  • Litchfield County, Litchfield: Verizon data 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, Salisbury: Verizon Wireless Data 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/Mid-Hudson system (or more recently the 00078 system since the ID seems to have been changed to 00078/Albany since 2013 or so) systems in spite of very good coverage. Initially observed on 07/18/2012, most recently observed: 07/20/2015.
  • New London County, Mystic: Verizon 1XRTT/3G/4G data calls drop along US-1 souythbound neae the JCT with CT-27. This data drop may be related to the "North Stonington" Verizon drop, below, as well as the "Westerly, RI" drop, further below. Calls initiated in Rhode Island (system 00028) along US-1 will seemingly transit to the CT(00119) system, but more likely they do NOT actually transit to the CT system, and data service is instead still being provided from the New England/00028 system. Heading southwards (more east along US-1 then south), calls become increasingly weaker until they drop just east of Mystic and JCT CF-27. Most recently observed: 11/25/2015
  • 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 frequently (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
  • New Haven County, Meriden: Verizon Wireless 1X/3G and 4G data calls/sessions drop along I-691 between JCT CT-322 (old CT-66) and JCT US-5, closer to CT-322 on the downhill heading eastound (uphill heading westbound). In other words, passing the mall along I-691 heading west, Verizon data sessions drop on the uphill stretch prior to JCT CT-322, which is where, until 1985 or so, I-691 ended, and all traffic exited to what is now CT-322 (it used to be CT-66). Heading east, Verizon data sessions tend to drop after the CT-322 overpass, and before the mall. Most recently observed: 03/03/2017.
  • New Haven County, Meriden: Verizon data calls drop along CT-15/Berlin Turpike near the beakaway/JCT with US-5. Active Verizon data sessions which are in use along CT-15/Berlin Turnpike at, for example, the JCT with the CT-9 freeway, will drop at or shortly after the breakaway from US-5 (which heads into downtown Meriden), and where CT-15 becomes a limited-access multi-lane divided highway. Generally, if a session will drop, it will do so no later than passing under the EB I-691 lanes, near the "Wesleyan University" sign directing traffic towards Middletown. Northbound, from the CT-15 freeway, Verizon data sessions drop generally by the point at which US-5 meets CT-15, and the combined roads head north towards Hardford as the Berlin Turnpike. Most recently observed: 04/22/2017.
  • Tolland County, Union: I-84 at CT/MA line: Verizon 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 connection 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: Verizon's data 1XRTT/3G 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: Verizon Wireless 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: Verizon's 1XRTT/3G data service 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

  • Baltimore County, Avalon/Relay/Ellicott City: Verizon Data drops connections and suffers from very poor coverge along River Rd. on the south side and Geln Artney Rd. on the north side of the Patapsco River in the Patapsco Valley State Park. Essentially, there is little to no coverage from Relay (where the Thomas Viaduct of the B&O Railroad heads south to DC and the old main line to Point of Rocks - one of the oldest rail lines still in service in America, splits off along the Patapsco River to Ellicott City, up to I-70, and then westward) to the western edge of the park heading towards Ellicott City along a spearate section of River Road which follows the Patapsco River westwards. Interestingly, the park lies directly under I-95, and within a mile of I-195 and I-895, all of which have acdeptable coverage with all major carriers. Why the park itself is not covered (the lower elevation perhaps?) is unclear, but no carrier has acceptable level of coverage in the park, and coverage only gets better heading west along River road at the JCT with Thistle Rd. (which connects River Rd with MD-144/Frederick Rd. at a higher elevation). Last observed: 05/18/2017.
  • Frederick County, Myersville: Verizon Wireless data 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 Celular system will drop while driving east on I-70 before entering the Frederick/00018 system. Most recent instance occurred on 09/24/2012.
  • Garrett County, Finzel: Verizon data calls drop on I-68 Eastbound in the vicinity of Finzel, MD. Technically this is not in the Verizon 00032/Pittsburg or 00096/Harrisburg systems, as the 01794 belongs to US Cellular, however, data sessions initiated in the Verizon 00032 (or 00096) markets which manage to hand off (most do these days for post-pay Verizon customers) to the US Cell/01794 market will drop in this general area of the US Cell/01794 market. Probably nothing that Verizon can do about this since it is likely the responsibility of US Cell, but one of the rarer examples of how Verizon customers may experience a service drop in a rural area which other carriers (ones which don't have ot admittedly depend upon roaming partners) do not. Last instance observed: 05/05/2015.
  • Harford County, Darlington: US-1, approximately 2 miles south of the Conowingo Dam, Verizon Wireless data calls/sessions 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: Verizon's 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
  • Massachusetts

  • Berkshire County, Egremont: Verizon Wireless data service drops occur along MA-23 near the Egremont/Great Barrington line near the northern JCT of MA-23/MA-41. While this may be the result of a poor handoff between the Verizon Albany/00078 system and the Verizon/CT/Western Mass/"A"/00119 system, it may also be due to generally poor coverage along MA-23 from the time in enters from NY (as NY-23) to the JCT with US-7 in Great Barrington. MA-23 is one of (if not _the_) major roads which are used to access Great Barrington/US-7 from the west, and the lack of proper Verizon Wireless Data coverage in the area (for over 20 years!) is disturbing and is indicative of yet another area where, based on coverage maps, motorists would expect reasonable coverage but find that in actuality there is none. Most recently observed: 07/20/2015
  • Berkshire County, New Marlboro/Monterey/Great Barrington: Verizon Wireless 1X/EvDO/4G data service drops as part of a large gap in coverage along MA-57 from the eastern New Marlboro town line all the way through southern Monterey (MA-23 goes through Monterey, while MA-57 runs roughly parallel to the south) onwards the western end of MA-57 at the junction with MA-23 a few miles east of the MA-23(END)/US-7 Junction in Great Barrington. Motorists familiar with the area will know that heading westwards, this is approximately the area from where MA-57 is a potholed, horrid road (even after repaving) with a 25 MPH zone, all the way past the JCT with MA-183, and onwards to the end of MA-57 at MA-23. Effectively, there is no coverage for about 15 miles on somewhat heavily traveled state route, which is unsual for Verizon's voice service. (To be fair, no other carrier - neither AT&T Wireless, Sprint, nor T-Mobile - covers the area either.) This extensive lack of coverage along a major route may be problematic for customers of OnStar and other similar built-in auto emergency services as if they were to break down along this strech of road or suffer an emergency they may be surprised to find they have no coverage at all! Moreover, it's been this bad for 20 years now, and although there has been some improvement generally in Western Mass, Verizon still has a lot of work do if the area. Initially observed and reported to Verizon in March of 1992 (yes, 1992!), last observed 10/14/2015.
  • Berkshire County, Savoy: At best scant Verizon data 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.
  • Hampden County, Brimfield: Verizon 3G and 4G data connections drop allong the MassPike/I-90 as the Masspike passes north of Brimfield, MA, near the "speed trap" (rarely used it seems, thankfully, a few miles west of the I-84 JCT). This is where the CT/Western Mass/A/00119 system ends and the Boston/RI/B/00028 system begins, and historically has been a handoff problem area. While the voice handoffs seem to have been fixed years ago (need to test), data calls/connections still drop, generally when passing the Eastbound "speed trap" area on the downhill side, approx 4 miles from the JCT of I-84. Most recent instance occurred on 07/04/2015.
  • Middlesex County, Natick: Verizon 3G/4G data connections/calls drop in Natick on MA-9 westbound, generally near the (hopefully still used) railroad tracks which cross MA-9 at grade before it runs over the Masspike near the ("Tara") Sheraton (which used to look like an old castle). Voice calls are generally fine in the area, but data calls seem to drop in the area for no reason. To a lesser extent, data calls also drop in the vicinity of the Natick exit on the Masspike (generally eastbound on the hill heading down to the exit, where they used to be voice call drops until maybe 2008 or so), but much less frequently. Most recent instance occurred: 07/04/2015.
  • Worcester County, Sturbridge: Verizon wireless data sessions on the MassPike/I-90 will drop in the vicinity of Mile Marker 77, near the JCT I-84 in Sturbridge. Most recent disconnection occurred: 07/26/2014.
  • New Hampshire
  • Cheshire County, Fitzwilliam: No Verizon data coverage (nor voice) 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.
  • New Jersey
  • Bergen County, Ft. Lee/Edgewater: Verizon data service drops along River Rd/CT-505 just north of the Whole Foods along the Hudson River. Verizon data sessions initiated (or in progress) along I-80 in Ft. Lee will drop heading south/downhill between the southern end of Fort Lee Historic Park/Henry Hudson Drive, and Undercliff Ave. At times Verizon data sessions will hold until a bit further south, but will generally drop by Old River Rd. where the 24-hour Acme Supermarket (ex-Path Mark) is located. This has been a problem since Verizon introduced CDPD (data service over analog cellular, now long gone) in the mid-1990's, and continued with 1XRTT, EvDO, and even currently with 4G. The problem may be related to multipath-like issues which are also in evidence along the Battery Park City esplanade, where signals from across the Hudson River make it difficult for phones to "lock on" a signal and/or for other similar technical/geographic reasons. Last observed: 05/02/2017
  • Cape May County, Cape May area: Verizon data service drops 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 which do NOT result in drops) near the JCT of US-9. Last observed: 06/14/2003
  • Mercer County, Pennington: Verizon Wireless data coverage drops along NJ-18, approx 2 miles north of the JCT with Tree Hill Rd, Verizon 1X/EvDO and 4G data calls drop 30% of the time right under the "quary spur" rail line off of the West Trenton branch. Data connections will drop while passing under the rail bridge and require a reset of whatever connection manager is being used, or in the case of a smart phone or other device which automatically reconnects, a reload of whatever page or application was transmitting/receiving data at the time. Last observed: 04/04/2015
  • Mercer County, Princeton: Verizon data 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 observed: 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: Verizon 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: Verizon data drops and up/down speed negotiation issues occir along the shore road which goes under Outerbridge Crossing (perhaps related to the problems on the NY side, above), where Verizon Express Network/1XRTT connections drop from 1 mile south of the bridge to about 2 miles north of it. The connection 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/2002, no resolution as of yet.
  • Somerset County, Raritan: Verizon Wireless data connections (1XRTT, EvDO and LTE) drop on US-206 in the general vicinity of Orlando Drive to Dukes Parkway West, heading south on US-206. Verizon data sessions disconnect enerally between Dukes Parkway East and Dukes Parkway West on the newly widened (2010?) section of US-206. Generally, data connections will drop anywhere from the bridge over the Raritan River (just south of Orlando Dr.) to slightly before Dukes Parkway West in the southbound direction, and northbound connections drop before the light for Dukes Parkway East. Drops can also occur just south of Orlando Rd traffic light; most often here data sessions just hang (can no longer pass data). Last occurred: 04/12/2016.
  • Sussex County, Sparta/NJ-15: Just north of I-80 on NJ-15 (1.5 miles), Verizon Wireless 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 very 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

    New York City 5-Borough/Counties:

  • Kings County (Brookyln) - Williamsburg: Verizon Wireless data calls experience connection difficulties in the Williamsburg, Brooklyn area, generally west of Bedford Street (the main north/south street), from North 10th to South 2nd. (Verizon voice services are affected as well, see the Verizon Voice Drops/Issues List for details.) All other carriers (ATT, Sprint, TMobile) suffer similar issues to a greater or lesser extent, and it's suspected that the problem stems from interference with signals from tall buildings immediately across the East River in Manhattan (similar to some issues in Battery Park City (Manhattan) along the Hudson River Promenade, where signals from Jersey City/Hoboken appear to compete with signals from the Manhattan-side, affecting voice and data performance). Essentially, when one is west of Bedford Street, data calls take a long time to set up and have slow throughput, text messages are slow to arrive, and voice calls are slow to set up outgoing and often miss incoming. It doesn't appear to be a signal stregnth issue (phones show ample signal stregnth), but more that a given phone or mobile device can't lock on a signal/channel reliably. Most recent instance occurred on 06/02/2016.
  • New York County - Manhattan: Verizon Wireless data 1XRTT/3G 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: Verizon Wirless data drops (and voice) 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 Verizon data 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: Verizon data 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 seem more robust and will drop less often while 4G/LTE drops more regularly, perhaps in trying to switch "down" to 3G speeds (which, as noted here, are also affected here by slow speeds and frequent drops). This is one of the weirdest and unusually poor segments of Verizon's (ex-NYNEX Mobile) Manhattan data service area and resembles areas near and along the Hudson River and the problems with signal propogation and multipath 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.
  • New York County - Manhattan: Verizon Wireless' 3G/1XRTT and 4G data connections "hang" traveling eastward along E79th St. After emerging from the Central Park 79th St. Transverse, data sessions (such as Telnet, FTP, SSH, streaming audo and video, etc.) all "hang" or "freeze" between Park and Lexington Aves. The data connection won't drop and remains active, but all data is "frozen", and no new data will be sent or received unless a given Telnet, FTP, SSH, or streaming audio/video session is restarted. Most recent instance occurred on 03/05/2015.
  • 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.
  • New York State Counties other than New York City:

  • Columbia County, Ancram: Verizon data connections (and voice) drop at the JCT of Boston Corners Rd and Under Mountain Rd/CTY-63. The drop occurs in general range from where the NY Cental RR (abandoned) right-of-way is along Under Mountain Rd down to where Boston Corners Rd meets Under Mountain Rd and proceeds south as Boston Corner's Road/County-67. Last occurred: 06/28/2014.
  • Columbia County, Austerlitz: Verizon Wireless data 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 Verizon data coverage (nor any voice 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, Boston Corners: Verizon Wireless data calls drop on NY-22 at the Dutchess/Columbia County Line, and (heading northward), remains wihout any appreciable coverage for 3 or 4 miles. NY-22 is the only major N/S road in the eastern section of these counties (since I-684 was never built that far north) and the lack of coverage in the area is not only an inconvenience but a potential safety issue for motorists driving on NY-22 in the area. Last occirred: 07/20/2015
  • Columbia County, Claverack: Verizon's wireless data service 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, Verizon data 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: Verizon Wireless's Data overage 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: Verizon Wireless data sessions drop 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/2009.
  • Columbia County, Gallatin: Verizon Wireless data drops along CTY-7 at the JCT with Tinker Hill Rd. at the Gallatin Town Hall. Heading westwards, Verizon data sessions begin to detriorate around Ancram/JCT NY-82 (which has poor Verizon coverage as well), and frequent drop-outs are prevalent between Ancram and Gallatin, before the complete drop near the Gallatin Town hall/Tinker Hill Rd. Verizon coverage is uncharacteristically poor in the general area, from CTY-3/NY-22 in Boston Corners, west to Ancram, Gallatin, and Silvernails, and only resumes (partially) near the Taconic State Parkway. Most recent instance occurred: 10/08/2016.
  • Columbia County, Spencertown: No Verizon Wireless Data 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 four miles east of Austerlitz. Most recent instance occurred on 08/08/2010.
  • Columbia County, Spencertown: Verizon data 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.
  • Columbia County, Silvernails: Verizon Wireless data calls drop along the Taconic State Parkway at JCT CTY-2(E)/CTY-50(W)/Jackson Corners Rd. In fact, along CTY-2 near the Taconic on/off ramps (at a slightly lower elevation than the Taconic), there is no Verizon data coverage at all. Most recent instance occurred on 10/02/2016.
  • Dutchess County, Amenia: Verizon Wireless's Data overage 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: Verizon data 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.
  • Dutchess County, Millbrook: Verizon data drops occur on NY-343, from just east of the Dutchess Day School (where the speed limit changes from 45 to 55), all the way to the JCT of CTY-23, and then poor coverage and drops continue along NY-343 to the JCT with CTY-24. Most recently observed on 12/2/2015.
  • Dutchess County, Millbrook: Verizon data calls drop on CT-23, just south of the JCT with NY-343. See above listing for general problems along NY-343 east of Millbrook; the drop on NY-23 is likely related to the generally poor Verizon coverage in the area. Most recently observed on 12/20/2015
  • Dutchess County, Pawling: Drops occur on NY-55/CT-55 at or near the NY/CT border, traveling in either direction. This may be due to an area of no coverage along NY-55 in the Verizon Wireless Mid-Hudson/00486 system, from the CT border westward along NY-55 to the JCT of CTY-22 (that's Dutchess COUNTY-22, not NY-22, which is about a mile or so further west). Due to the lack of coverage (as well as possibly the poor handoffs in general between the Litchfield, CT ex-01101 system and the Dutchess/00486 systems), all data connections drop at all times while driving either east or west over the CT/NY border on CT/NY-55. Most recent drop occurred on: 02/15/2017
  • Dutchess County, Stanfordville: Verizon data drops occur on the Taconic State Parkway at Mile Marker 63.3, which is just south of CTY-19/Bull's Head Rd. Heading southbound, calls begin to degrade at Nine Partners Road, and will drop completely just north of CTY-19. Heading northwards, calls begin to degrade crossing CTY-19 and will drop completely by Willow Brook Rd. Most recent instance occurred on 10/04/2016.
  • Dutchess County, Unionvale: Drops occur on CTY-21 at the Unionvale/Dover town line (pretty much at the apex of the hill which CTY-21 climbs over between JCT NY-22 to the east and CTY-9 to the west). Data connections are reset and must be re-established on 1X, EVDO, and 4G. Most recently observed: 04/02/2015.
  • Dutchess County, Unionvale/Billings: Verizon drops data calls/sessions along Tompkins Road near the JCT with N. Smith Road. (Just slightly north of Sky Acres Airport and slightly east of the JCT of Tompkins Road and NY-82.) Most recent instance occurred on 07/12/2016. Coverage along the NY-82 corridor between NY-55 and US-44 is often weak, and drops can occur from time to time while driving along NY-82 away from the NY-55 and US-44 junctions (where Verizon's data coverage is decent and usually 4G), but between the two points, coverage degrades quickly (for audio as well, see the Verizon Voice Drops list for details), and data sessins will often drop, time-out, and/or require re-connecting. NY-82 parallels the Taconic Parkway in this segment (between NY-55 and US-44), so one would expect better coverage in the area, but after many, many years, Verizon's coverage is still weak and "droppy" in the area. Most recent instance occurred: 12/28/2016.
  • Nassau County, East Norwich: Verizon data drops occur on NY-106 between NY-25A and NY-25. Data connections simply shut down, even though there'’sgenerally good coverage along the north shore of Long Island. 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., Verizon data Express Network/1XRTT/3G 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.
  • Orange County, Cornwall: Verizon Wireless data drops occur approximately one mile south of Continental Rd. Last instance occured on 07/17/2011.
  • Rensselaer County, Berlin: Verizon's data 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 continues 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 Verizon Wireless data 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.
  • Suffolk County, Huntingon: Verizon Wireless drops data calls (1X/3G/4G) along Old Post Road East (old NY-25A) at the intersection of Crystal Brook Hollow Road. (At the point where, heading east, Old Post Rd. E. turns encounters a stop sign and requires a right turn to proceed along Old Post Rd. E., while a left turn takes you south along Crystal Brook Hollow Rd towards (new) NY-25A near where NY-347 (extension of the Northern State Parkway) mergers with and ends at NY-25A.) While not the most traveled road in Suffolk County, it used to be NY-25A and is used by many locals as a means to avoid traffic and lights on the often more crowded NY-25A. Most recent instance: 11/25/2016
  • Suffolk County, Miller Place/Mt. Sinai: Verizon Wireless data calls drop along North Country Road (old NY-25A) near the intersection with Birch Hill Road. Coverage is surprisingly poor in both Mt. Sinai and Miller Place areas. Most recent instance: 11/25/2016
  • Suffolk County, Sunken Meadow State Park/Coack/Fort Salonga: Verizon data calls/sessions drop on the Sunkean Meadow Parkway just north of JCT NY-25A/Ft. Salonga Rd., passing the parking permit booths, before the SMP overpass over Sunken Meadow Rd. The drop occurs in the general area of where there used to be a northbound exit to Kohr Rd, but now appears to be only for park employees and vehicles. A possibly related drop also appears to take place on Sunken Meadow Rd, just west of the Sunken Meadow Parkway overpass. In general, north of where NY-25A makes a sharp eastward right and heads down to NY-25 in Smithtown near the LIRR overpass, St. Johnland Road (which becomes Sunken Meadow Rd. a bit north and west of the NY-25A JCT/turn) has relatively poor Verizon voice and data coverage, and is typical of many of the far North Shore coverage issues in Nassau and Suffolk Counties on Long Island. Most recent instance: 08/04/2017
  • 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 until 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 if 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, Eastchester: Verizon Wireless Data drops, or more accurately, data "hangs" (where the session is not disconnected as would be the case in a more typical Verizon 1X/3G data drop) occur on the Hutchinson River Parkway at the JCT with the Cross County Parkway, and all data sessions are frozen, but the physical data connection does not get torn down. This "hang" occurs perhaps 30% of the time, more often in the southound direction, and most often when a data session is initiated in Connecticut on Verizon's A/00119 system and it successfully transits to Verizon's NY Metro B/00022 system. In many cases, this handoff does not occur (see the Greenwich CT/NY border entry in the Connecticut section, above), but when the tennuous handoff occurs (coverage dips to nothing along the Hutch in Purchase, NY), but given a successful CT to NY handoff, the Eastchester hang is more likely to occur. Last observed: 10/25/2015
  • Westchester County, North Salem / (Fairield County, CT, Ridgefield): Verizon data calls drop along NY-116 between North Salem (NY) and Ridgefield (CT), just east of the JCT with NY-121, at or near the NY/CT line. The area (for about a mile east of the NY/CT line) lacks nearly any Verizon Wireless coverage, which results in a Verizon voice drop as well. Interestingly, along the more southerly NY/CT-35, although voice calls drop at the state line, data calls will hold, so this appears to be just a coverage issue and no something pertaining to the usual CT/NY inter-system handoff problems. Last observed: 09/09/2016
  • Westchester County, Rye: Verizon's dara service drops along I-95 at Mile Marker 12 in the vicinity the Rye Playland connector. Most recent instance occurred on 09/20/2009.
  • Westchester County, Vista: Verizon Wireless data 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: Verizon 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: Verizon Wireless data 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 is where the connection will drop. Most recent instance occurred on 11/27/2006.
  • Pennsylvania

  • Bedford County, Breezewood: No Verizon data 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: Verizon Wireless data 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: Verizon 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 general 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" and 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: Verizon 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: Verizon Wireless data drops/disconnects 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 and data. Most recent instance occurred on 08/19/2012.
  • Fulton County, McConnellsburg: Verizon data 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: Verizon Wireless data service 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/13/2014, reported to Verizon on 09/01/2004, no resolution as of yet (that's nearly 10 years it's been going on!)
  • Westmorland County, Ligonier: Verizon System ID 00032/Pittsburg Area - Poor to no coverage on PA-31, between JCT PA-381 heading eastward to Laurel Summit (on PA-31). At Laurel Summit heading east (down the hill) coverage is generally better, but both voice and data calls will generally drop heading westward from the summit going to and past the JCT with PA-381. Last observed: 05/05/2015
  • 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 pass data again (a simple re-connect will not work here). 06/07/2003
  • Washington County, Westerly: Verizon Wireless voice (and data) calls drop at the RI/CT line, between the RI/MA/NH/00028 system and the CT and Western MA/00119 system, calls drop on US-1 and generally in the area of donwtown Westerly and anywhere south of I-95 where the CT and Rhode Island systems need to hand off to each other. The drops are most pronounced near the Westerly Rotary (eastbound/northbound on US-1) or under the Amtrak/NE Corridor rail tracks (heading westbound/southbound on US-1) on approaching the CT side of the line. This has been a problem since digital service started over 15 years ago and has never been resolved, and again appears to be a vestige of how Verizon had relatively segregated systems when they grew their service area and acquired new service areas and (apparently) have been unable to integrate them to the same extent as other carriers, which do not have "border" hand-off and drop issues to the same extent which Verizon seems to. Last observed 09/24/2015.
  • Vermont

  • Bennington County, Searsburg: Verizon Wireless data drops along VT-9 (the southernmost major East-West route in Vermont, extending from Bennington at the Western end eastwards to Brattleboro (and on to Keene, NH)) near the JCT with VT-8. The drop appears to be due to the handoff between the Verizon/00300 and the US Cellular/01484 systems, and may be similar to the handoff problems between Verizon and US Cell/01794 at some of the Pennsylvania/Maryland handoff areas as well. Additionally, since (older) Verizon phones show "Extended" service (ie, roaming) in the 01484 southern VT/southwestern NH US Cell system, many will not allow data service while roaming in the 01484 system (again, similar to the US Cell 01794 system in W. VA and MD along I-81 and I-70/68). And of course, MVNOs, like Straight Talk's Verizon resale product, are prohibited from roaming on 01484 (voice or data), so no data can be used with many Verizon MVNO's in this area in the 01484 market (which includes Wilmington, VT, and one can only imagine all the Verizon customers in the winter coming to Wilmington using endless amounts of data and all the revenue going to US Cell from all the skiers staying over!). Incidentally, Verizon/00300 service doesn't commence again heading east until Newfane, just west of Brattleboro, on VT-9. Last observed: 09/29/2016.
  • Windham County, Guilford: Verizon data drops occur southbound on I-91, within the Verizon Wireless 00300 system, just north of the Vermont/Mass border, before entering Greenfield, MA. Verizon data sessions in the northbound direction do not drop; only dara sessions which are active north of the MA/VT line will drop as the line is crossed heading southwards. Before Verizon took over Cell One/VT (which was SID 00313, apparently this was changed so Verizon's entire VT system is 00300 now), drops occurred both ways, but this was corrected in 2010, and so noted in he "Corrected Issues" section at the bottom of this list. More recently (2015), the drop seems to have resurfaced as one in the southbound direction only. (Other previously corrected drops, such as CT/NY along I-95 or the Merritt Parkway), also seem to have resurfaced for some reason as well. Most recently observed: 08/22/2015.
  • Windham County, Marlboro: Not really a "Verizon" drop, as it involves service from the US Cell/01484 system, but Verizon customers roaming on the 01484 system (in Wilmington, for example) will experience a drop heading eastwards on VT-9 near the "runaway truck ramps". As there is coverage on both sides of the ramps along VT-9 via US Cell/01484, it's not Verizon's "fault", as they have no control as to what their roaming provider does in the area, but it is a drop on one of the main roads to/from Wilmington. Most recently observed: 09/29/2016.
  • Virginia
  • Clarke County, Berryville: Verizon Wireless data service 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 affects 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 Virginiawill 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, Verizon's data service 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-64, 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

  • Washington DC Metro: Verizon Wireless' Data Service drops on the DC Metro Red Line between Twin Brook and White Flint. Most recent instance occurred on 03/31/2009.
  • Washington DC Metro: Verizon data drops occur on the DC Metro Red Line between White Flint and Grosvenor. Most recent instance occurred on 02/26/2009.
  • Washington DC Metro: Verizon data 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: Verizon Wireless data 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: Verizon's data (and to a lesser extent voice) overage 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: Verizon data sessions drop on the Red Line between just north of Woodley Park. Most recent instance occurred on 08/23/2010.
  • Washington DC Metro: Although there is Verizon Wireless data 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: Verizon's data (and voice) coverage at the Farragut North station on the Red Line is very poor, as compared to other carriers (like T-Mobile), which have very good voice and data service in that station. We thought the poor Verizon data (and voice) coverage in Farragut North was a result of the station reconstruction work, but now that it's over there is still very poor Verizon Wireless data and voice coverage. Most recently observed on 10/20/2015.
  • Washington DC Metro: No Verizon data 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: Poor to no Verizon data coverage on the Red Line between Farragut North and just north of Metro Center. Most recent instance occurred on 12/22/2009.
  • Washington DC Metro: Metro Center - As of 2016, Verizon's data service at Metro Center seems to have taken a turn for the worse - while voice coverage works well enough on both the upper (Red Line) and lower (Blue, Orange, and Silver Lines) platforms, data seems nearly unusable, and connections often can not be initiated or maintained. (But Verizon's data service works fine at all the surrounding stations, such as Gallery Place, Farragut North, McPherson Sq., and Federal Triangle, so it appears to be something confined to the Metro Center station.) Unless they have changed frequencies so that only the newest phones will be able to utilize data at Metro Center (we tried with a Galaxy Nexus 5, as well as many older models as well as those of Verizon MVNOs/resellers), it seems highly unlikely that this is intentional on the part of Verizon, and instead appears to be poor quality control with respect to data service at the Metro Center station. As of January 2017, this has just gotten worse, with data sessions being blocked or impossible to complete in most cases (even off peak when there are few people there), and even voice calls generally blocked; multiple attempts were made on 01/03/2017 with various phones and an old data-only card and each had the same problem. Most recent instance occurred on 01/04/2017.
  • 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 the Corrected Items section.)
  • Washington DC Metro: Verizon Wireless data 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: Verizon Wireless data sessions 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: Verizon's 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: Verizon Wireless Data (and voice) 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 on 07/13/2008.
  • Washington DC Metro: There is no Verizon Wireless data 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.
  • West Virginia
  • Jefferson County, Charlestown: No Verizon Wireless data 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, Verizon 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 continue 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.

  • 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. Verizon's data 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.
  • New Jersey
  • Middlesex County, New Brunswick: Traveling on US-1, Verizon 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.


  • 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.
  • Florida
  • Brevard County, Cocoa Beach near Cape Canaveral between A1A North of FL-520. The connection will reset while entering the FL-528/Beeline HWY extension. Problem occurred on 01/31/2004 and was resolved in April 2004 and continues to work as of April 2005.
  • Palm Beach County, Delray Beach, Atlantic Ave (while exiting the causeway from Florida A1A and heading west towards US-1), the 1XRTT connection drops. Problem occurred on 01/31/2004 and was reported to Verizon in February 2004; Verizon said they were aware of the problem and said they would have the problem resolved shortly: problem was resolved in April 2004 and continues to work properly as of April 2005.
  • Maryland

  • 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

  • Franklin County, Bernardston: Drops occur on I-91 at the Vermont/Massachusetts border. Most recent instance occurred on 10/13/2009. Appears to have been corrected as of 05/23/2010. Then drops southbound started re-appearing around mid-2014, and after a few such southbound Verizom data drops at the Vermont/Mass border, this drop was re-added for the southbound (only) direction, in the active Verizon Data drops section, above.
  • New Jersey
  • 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
  • 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 drops 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 drops. 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 service 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 00025/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 generally 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.
  • Pennsylvania
  • 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 occurred on 07/20/2006.
  • Vermont
  • 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 and 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
  • 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 where 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 occurred 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. Appears 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. 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 02/11/2013. This seems to have been corrected as of 02/27/2013.

  • Contacting WirelessNotes.org

    We may be reached via:

  • E-Mail: Please mail to abcwireless-notes@interpage.net , removing the first three letters of the alphabet from the name/address.
  • Web-based Interface.
  • Phone: +1 (802) 316-5000 M-F, during regular business hours.

  • Back to Main Wireless Notes Page
    Comparison of Cellular Carriers
    Interpage NSI Main Page

    Last modified and ©: 08/05/2017