Wirelessnotes.org Verizon Wireless Dropped Calls

Verizon Dropped Call List:
An Updated List of Locations, Places, Areas and Roads where Calls on Verizon Wireless Drop, are Disconnected, have Poor Coverage, or Experience Service Difficulties

Last Update: 08/12/2024

This list is intended to provide a consolidated reference to a series of posts, messages, and other observations as to Verizon Wireless dropped calls, disconnects/poor handoffs, feature issues, and overall cellular service problems.

(This page previously contained a list of Verizon Data (previously branded as “Express Network”) 1XRTT/EvDO(3G)/LTE(4G) drops, handoffs, and service issues, but as the combined list was getting too long due to the unfortunately increased incidence of Verizon voice call drops, we have decided to move the list to a separate page, which covers only Verizon Wireless 3G/4G Data Connection Drops and service problems. )

See also the Annoying Verizon page for an ongoing and updated list of annoying, silly, aggravating, and penurious Verizon Wireless (and landline) practices.

If you are experiencing problems viewing this page, please try the older, flat Verizon Dropped Calls List page.

General:

In our experience with regular use of the 4 (and as of mid-2022, 3) nationwide US cellular carriers for the past 25 years, we’ve generally found that Verizon Wireless’ coverage and service suffers from the fewest call drops, disconnections, audio distortions and other voice call difficulties (hereinafter collectively refered to as “drops” unless otherwise specified), and has the most extensive and penetrating network for wireless voice and data services.

Even with the recent (post-LTE/2019) increase in Verizon drops, where for some reason which we don’t fully understand (LTE conversion?), we’ve noticed a dramatic increase in drops while driving on roads which were previously problem-free, the overall incidence of these drops is still somewhat less than ATT, and appreciably less than T-Mobile (TMO/Sprint). While there seems to a be trend of a greater-than-before incidence of Verzion drops on some roads and corridors where Verizon has curiously ceded its lead to AT&T, or in fewer instances to T-Mobile (which in a few cases seems to have reduced its many drops after the acquisition of Sprint), overall and on average, despite service improvements on the parts of AT&T and T-Mobile, Verizon still suffers from the fewest dropped calls, even when taking into account Verizon's apparent increase in drops along previously drop-free roads.

Verizon's superior coverage is of particular note outside of urban areas (which tend to be more densely covered by all major carriers and even some regional ones). In many rural areas, there are really only two carriers to choose from: Verizon and AT&T, as T-Mobile/(& ex-Sprint) appear to have little interest in covering exurban and rural markets outside of high-traffic road corridors or places which are flat and topographically unchallenging. Thus, Verizon and AT&T (and their resellers and MVNOs) are effectively the only two choices for reliable and generally uninterrupted (ie, “drop free”) calling, with Verizon currently (Jan 2023) having a slight edge on AT&T.

This is not to say that Verizon's coverage and overall service is without its faults — quite to the contrary: Besides the apparent and inexplicable degredation of services (read: more drops) starting in 2018 and continuing into 2023 at an increasing rate, the implemtation of 4G/LTE and the removal of 2G/3G in Dec 2022 does not seem to have, as of yet, yielded dividends in terms of more long-range, penetrating frequencies being re-farmed to 4G/LTE bands, and service in many areas where 2G/3G service was acceptable has now become poor to non-existent.

In fact, in January 2023, after the 3G shut down, when ostensibly more frequencies and/or spectrum would be made available for 4G/LTE devices, in tests performed with phones provided by Verizon, coverage appears worse, and drops more frequent, than with 2G/3G equipment which worked fine for 15 years! We hope this situation is temporary and a result of some transitional lag while frequencies/spectrum are re-purposed for 4G/LTE, but so far there is no evidence in any improvement of coverage in terms of 4G to replace the lost coverage which 2G/3G devices enjoyed.

The Verizon Cellular (Voice) dropped call list below notes such cases, eg, where 4G/LTE service post-2G/3G/CDMA shut down was tested Verizon-provided phones, and which dropped and/or had other service difficulties using 4G/LTE, as are so noted at the end of each given drop's/problem's description with a specific reference to 4G/LTE drops using Verizon-provided equipent.

Additionally, some fundamental aspects (other than the continuity of coverage) of Verizon's voice cellular service are less than stellar, even with the supposed “improvements” of 4G/LTE.

Prior to the 3G shut down in early Jan 2023, the sound quality of the CDMA protocol which Verizon used was, in our experience, worse than GSM (which was/is (in part) utilized by AT&T/T-Mobile) and suffers from greater distortion and delays in conveying normal-sounding coversation (see the Digital Cellular Latency Page for a discussion of voice delays and latency in cellular telephony).

Verizon's 4G/LTE, as of yet (2022/3 and going forwards) doesn't seem to have helped much – Verizon calls, even in areas of good coverage, still have a “tin-can”, distorted, “twang” to them which immediately screamed out “CDMA cellular call!” (and as of 2023 “Verizon cellular call!”) to the called party (if the call is received on a traditional, non-Voip landline), as compared to AT&T's GSM and newer LTE protocol(s) which have somewhat better tonality and less latency. In fact, when comparing Verizon's 4G/LTEvoice audio quality and latency with that of ATT, ATT Wireless sounds cleaner and more immediate than Verizon's. ATT Wireless is getting closer to sounding like a traditional landline call, while Verizon, even with 4G and LTE, still more or less sounds like a “cell phone call”.

(Note: With some limited calls on Verizon's fastest 5G frequencies, call audio quality does sound better, but 4G/LTE still sounds almost bad as CDMA, while AT&T's 4G audio sounds significantly better. T-Mobile also uses GSM (in 2017), and is in 2022 mainly on LTE (but 2G/GSM is still available), but in either case, their audio has for the past few years (2017-2023) sounded very “processed” and “Voip-ish” – are they using Voip or some sort of extreme compression for the backhaul? (e.g.,the connection from the cell tower to the telephone network)).

In addition to the above voice sound/tone issues with Verizon, there is also the issue of latency, which is the delay imposed by digitization (and to a lesser extent by how long it takes the electrical signal pass through the air, and then via trunk wires, and then via a local phone “loop” or cellular connection to the destination phone) from the time that a person speaks a word to the time the person on the other end of the line hears it. We've found that in the past that customers with CDMA service (Verizon and Sprint) had a somewhat lengthier delay from the time a caller said something into a phone to when the recipient heard it as compared to the (somewhat) faster/lower-latency GSM counterpart. This effect is even more noticeable on mobile-to-mobile calls and mobile-to-VoIP calls (for more details, see this discussion of cellular and Voice-over-IP latency/voice delays. Unfortunately, 4G/LTE/VoLTE has not made much of an improvement, as currently, as noted above, there seems to be somewhat more latency with voice conversation via Verizon's more modern protocols (4G, LTE, etc.) than with similar protocols on AT&T.

Thus, if you like/need your cellular service to closely approximate landline (or good analog cellular) service, with no noticeable delay and/or no/less distortion, AT&T Wireless may be a better choice of carrier, as Verizon and T-Mobile will likely prove more of a disappointment due to their inabilities to make any improvement (except with certain 5G bands) towards landline-like audio and conversational call quality.

(As an aside, a number of people familiar with digital cellular protocols have written to us to suggest that while CDMA is more “managed” and “metallic” sounding than GSM, the codecs (or modems) in newer CDMA phones are not well-made, and that CDMA sounded a lot better with early Verizon digital CDMA phones (like the Sony/Qualcom Digital QCP-800). As users of the QCP-800 (even in 2022!), we agree there may be some validity to the point (Verizon CDMA calls do sound somewhat better and less “metallic” on the QCP-800), overall, AT&T's cotemporaneous GSM and their generally high-quality backhaul from the cell tower to the telephone network offers a superior audio profile than anything Verizon currently offers.)

Other than call drops and audio quality, another issue which seems to date back to the inception of cellular service, is Verizon's segregation of markets. In the 1990's, when cellular networks were being built out, there was lack of integration between the various markets (calls wouldn't be delivered from one market to another – unheard of now in 2019), voicemail didn't work outside of a person's “home” market, and other features and services didn't function or worked differently while roaming. Most of these problems have long since been corrected, but for some reason, Verizon has in many cases never fixed many drops between markets.

We have raised these issues on the drop list and complained long and often as to these drops between Verizon markets (ex: I-84 between the CT/00119 “A-side” market and the NY/00022 “B-side” market at the CT/NY line weren't corrected fully until 2018 or so), and yet, still in 2023, some of these drops still occur! Many of these are detailed in the Verizon dropped calls section, listed state by state, below.

Additionally, Verizon's customer service and upper management can be at times ossified and stodgy, and suffers from parochialism and in-fighting between the various (seemingly Balkanized) companies which were absorbed into Verizon during the Verizon/GTE/PrimeCo merger, as well as with subsequent mergers with carriers such as Alltel (which seems to have been a much smoother transition than with GTE).

This internecine feuding and bickering can manifest itself in the outward customer service experience which customers receive, which can make the resolution of otherwise relatively simple issues more protracted and complex as the case meanders through the rough waters of the various departments within Verizon fighting amongst themselves.

Verizon also appears to aggresively push customers away from calling Customer Service, with an IVR that makes it difficult to reach someone without useless self-help (read: stupid computer-based delaying tactics), to call hold times which can reach 30 minutes or more, and to non-US based call centers staffed by people who do not either have the tools and/or the inclination to provide the phone support which wireless issues often comport. At every step of the process it seems that Verizon is trying to save money and not properly support its customers by effectively telling customers “Even though YOU pay US, and technically YOU are customers, we don't want to see it that way, and we are going to make YOU do more work and take more of YOUR time by making it so difficult for you to deal with us via 611/(800) 922-0204 that you will just give us and use the (effectively cost-free, for Verizon, of course!) web site instead!”

Verizon either knows (or should know) of the readily apparent deficiencies of most of it's non-US based support, and instead of realizing that it just doesn't work well and obtaining better-trained, dedicated US-based support reps for ALL customer calls, they seem to maintain the offshore (Philippine?) center(s) as a way to make customers so disgusted that they just don't bother calling support anymore, and move over to the web.

More generally, Verizon seems to feel that there is no one better than they in terms of reliable service and coverage (which in our experience is true generally, but, as noted above, as of 2023, becoming increasingly less and less so), and thus they don't have to try 'as hard' to retain customers who are disatisfied with some aspect of their Verizon service, support, and/or charges.

Finally, Verizon, coming from a body of carriers which were primarily old “wireline” service (“B”) providers in most markets which they served, were assigned (now very valuable) 800 MHz frequencies in the 1980's at the inception of cellular service, which helps facilitate their somewhat better coverage — the 800 MHz frequencies can pentrate buildings, travel long distances, fit in the countours of mountan valleys, etc., and provide carriers which were assigned 800 MHz bands (mainly Verizon, ATT, and some regional/local carriers) a distinct advantage over those which weren't (TMO and Sprint). These early valuable frequency assignments in part may also serve as the basis for Verizon's (and to a lesser extent AT&T's) “We're the phone company and we know what you need!” biases and institutional impediments to better, more responsive and flexible customer service, since their alost exclusive use of 800 MHz allows them to provide service in a manner which non-800 MHz carriers can not.

Verizon's (and to a lesser extent AT&T's via SW Bell, Pacific Bell, and Ameritech) long-standing wireline/landline presence in most of their markets and initial mandate to build out their analog systems to cover their licensed areas, led to significantly broader and better (RF/dB-wise) coverage than many of their non-800 MHz/digital-only competitors. BAMS, GTE, Airtouch, etc., all had regional service areas to cover, and spent their assets and time covering these areas to become the (generally) superior carrier in their respective markets, using 800 MHz frequencies assigned to them by virtue of they're being he “landline” carriers in the respective markets which they served.

(When cellular licenses were handed out in the 1980's, the FCC opted to distribute them via the IMTS (Improved Mobile Telephone Service) pre-cellular model, with the “wireline” (Bell, GTE, or other independent local exchange carrier, or local “phone company”) getting half on the 800 MHz spectrum, and some “non-wireline” carrier getting the other half to “compete” with the wireline carrier (but which effectively formed an uncompetitve duopoly until Sprint, Nextel, and regional PCS carriers came online in the mid-1990's).

As noted above, the 800 MHz frequencies are particularly valuable as they penetrate buildings well, can travel for long distances, bounce reasonably well off mountains so covering valleys is easier, and have other Radio Frequency (RF) and propogation benefits. Verizon (comprised many of landline/wireline “B” carriers) and AT&T Wirless (also with a good number of landline/carriers, as well as many initial non-wireline carriers who received the “A”/”other half” of the 800 MHz licenses) have a majority, if not all, of the original 800 MHz licenses, which is why they tend to have superior/broader coverage, work better in buildings, and manage to have their signal penetrate into rural areas and those which are topographically challenging as compared to T-Mobile (+Sprint).

(This leads to another question which we've never had properly answered: As Verizon and AT&T were given these highly valued 800 MHz licenses, effectively for free (there were no auctions in the 1980's when the FCC assigned the 800MHz cellular band to a “wireline”/B and “non-wireline/A” carrier in each market) by virtue of Verizon and AT&T (or their predecessors) being the landline carrier in a given market, why do they get to keep said 800 MHz licenses (or any licenses?) if they opt to abandon wireline service in a given state?

For example, New England Telephone served as the local/wireline Bell Operating Company in Maine, Vermont, and New Hampshire, Mass, and Rhode Island, and as such was assigned some of the 800 MHz licenses in those states for the original A/B 1980's analog (“AMPS”) services, which Verizon currently uses for cellular service (along with more recently assigned bands). Yet when New England Telelphone decided to abandon the Maine, New Hampshire, and Vermont markets (which was a costly fiasco for ratepayers of those three states in having Fairpoint take over and quickly go bankrupt (which New England Telephone/Verizon was forced to pay for in 2011)), they were able to keep their 800 MHz cellular licenses, which they obtained by virtue of being the “B”/wireline carrier, even though Verizon was leaving Maine, NH, and VT, and thus was no longer the wireline/B carrier.

More specifically, take the 00428/B cellular market for Manchester, NH: After initiating analog cellular service there in the late 1980's, New England Telephone's mobile division (NYNEX Mobile) then became Bell Atlantic Mobile (after a merger of the mobile division with Bell Atlantic Mobile). Later on, NYNEX and Bell Atlantic also merged their landline services under the same name, and then after the GTE merger, became Verizon/Verizon Wireless. Thus, via a string of acquisitions and mergers, Verizon became the landline operating company for the Manchester market, and thus (rightly) the holder of the landline cellular licences which it first obtained 25 years earlier as New England Telephone.

But, after Verizon (landline) opted to leave the northern New England market via the aforementioned abandonment of local service in NH, VT and ME to Fairpoint in a disasterous transaction which local residents are still paying for many years later, why was Verizon wireless allowed to keep its 800 MHz licenses for Nashua, Manchester, etc? New England Telephone received them in the 1980s because they were the local/landline carrier, and if Verizon opted to stop being the local/landline carrier in Manchester as part of their abandonment of their northern New England markets, why should Verizon Wireless keep the free windfall of the original 800 MHz licenses if Verizon (landline) isn't the landline/wireline carrier there anymore?

At any rate, nonwithstanding the provenance and legitimacy of Verizon's wireless licencing in markets which they have abandoned, Verizon has and continues to maintain generally technically competent wireless network, and offers acceptable levels of service in a few areas where AT&T wireless, even in 2023, still does not, but the gap between the two is closing quickly, and in most cases, there is now parity between the two in terms of coverage, and ATT has superior voice quality for most calls. (We're not even bothering to consider TMO's much less robust service – or lack thereof – in more challenging areas.)

While customer service is stodgy, and billing practices are laughable (in 2023, it's still amazing that a $50 Verizon plan ends up with an “out the door price”, eg, what you are billed for, of $79, which includes all sorts of fees and surcharges, including Verizon's “administrative charge” (the fee they charge for charging all the fees!)), and audio quality less than stellar, Verizon offers, by a slight margin, a fewest drops and call interruptions over AT&T Wireless.

(Note: If the billing nonsense, fees, and annoying customer service makes dealing with Verizon seem to much trouble, consider dealing with an MVNO (essentially a reseller) of Verizon, where the underlying network is Verizon's, but the billing and customer service is performed by a company more interested in your business and willing to effectively act as a “buffer” between the customer (you) and Verizon – for better or worse! 🙂 )

As a final note, the length and extent of the list (as compared to other lists which we maintain) should not be construed as evidence of more drops/inferior coverage by Verizon Wireless – quite to the contrary – it is due to their generally superior coverage that we utilize Verizon as our primary carrier, and thus have more experience with them than with other carriers as to where their service experiences drops and other difficulties.

Overall, the Verizon Digital Cellular Dropped Call 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 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 a drop is experienced on 05/01/2005 it still needs to drop on 06/01/2005 for it to be posted.
Drops are moving drops 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 doesn't just pertain to motorists and roads; we also list Verizon Wireless call drops on Amtrak and commuter rail services, parks, and other areas without vehicular traffic, etc.)
Drops are in areas of otherwise good coverage, e.g., the drops listed are not in areas where Verizon doesn't yet have coverage. Thus, there won't be an entry such as "Verizon drops calls between Montauk, NY (00022 system) and Block Island, RI (00028 system)", as there is no coverage over the open waters between the two systems. The Verizon call drops list thus generally lists call drops in areas where there is good coverage (or in some cases where there should be good coverage), which shouldn't experience any drops, yet do so for no apparent reason.

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 dropped call experiences with Verizon Wireless which meet the above guidelines so that we can provide a more comprehensive list. Contact information for this list is provided at the end of this page.

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 Call List by State

California

Los Angeles County, Hollywood: Verizon Wireless calls drop along the Hollywood Freeway/US-101, just north of the Hollywood Bowl, about half-way between the Highland Ave/Cahuenga Blvd exit and the Barnham exit directly to the north. (The drops occur along Cahuenga Blvd as well, which parallels the 101 Freeway through the canyon in the area.) Likely one of the busiest sections of the 101 and Verizon apparently has problems covering it! Most recent instance occurred on 12/21/2018.
Los Angeles County, Hollywood Hills: Verizon calls drop along Outpost Drive just south of the JCT/intersection with Castillian Drive. This is a relatively new drop (seems to have started in Jan, 2019). We initially speculated it was weather related (other areas along Mulholland stopped dropping at the same time, if only for a few days), but this drop has now persisted for over a month. Another new drop for Verizon (amongst many) in an area (south of Mulholland) which had relatively drop-free coverage for many years. Most recent instance occurred on 02/15/2019.
Los Angeles County, Hollywood Hills/Beverly Glen: Verizon drops calls along Mulholland Drive, between the Stone Canyon overlook and Beverly Glen Blvd. Heading east, calls initiated while on the San Diego Freeway/I-405 begin to attenuate and get distorted passing the Stone Canyon overlook, and will fully drop in most cases just west of the JCT with Beverly Glen Blvd. Generally, coverage is lacking east of Beverly Glen Blvd. all the way to Laurel Canyon Blvd, although calls between Beverly Glen and Laurel Canyon don't drop. In general, Verizon needs to do a much better job covering the Hollywood Hills and Mulholland Drive between the 405 and US-101 to the east. Most recent instance occurred on 11/30/2018.
Los Angeles County, Hollywood Hills: Verizon Wireless calls drop along Mulholland Drive at the JCT with Las Altures. Problem has gotten worse as of late 2019 and 2020 (due to Verizon LTE transition? - but LTE coverage is very spotty in the Hollywood hills, as is coverage in general, so why handicap it further?). Most recent instance occurred on 12/05/2019.
Los Angeles County, Sherman Oaks: Verizon Wireless drops calls at the JCT of I-405/San Diego Freeway and US-101/Ventura Freeway, from the Northbound I-405 transition to the US-101 Southbound. An odd place for a drop, seeing as how the 405 is likely one of the busiest (if not -the- busiest) freeway in LA County. Most recent instance occurred on 11/28/2017.

Connecticut

...or click here for additional details.

Fairfield County, Brookfield: Verizon Wireless call drops occur on US-202 (old US-7) almost directly outside of the WRKI/I-95 radio station building. This is in the general area of an occassional call drop on the parallel and newer US-7 freeway, which is detailed immediately below. Most recent instance occurred on 09/15/2013.
Fairfield County, Fairfield: Verizon calls drop between Mile Marker 21 and 22 on the Merritt Parkway while crossing the Redding/Fairfield county line near the overpass for North Ave. Generally, drops occur more often in the northbound direction than southbound, and tend to occur very quickly and without much distortion upon reaching North Ave. Most recent instance occurred on 10/11/2015.
Fairfield County, Greenwich at the Merritt Parkway/Hutchinson River Parkway (CT/NY) line: Verizon Wireless calls drop when traveling from the Hutchinson River Parkway in New York onto the Merritt Parkway in Connecticut. Most recent instance occurred on 02/08/2007. As of late 2012 to mid-2013, this problem seems to have been largely correct, at least on the voice side (Verizon Wireless' data service is a different issue and still experiences drops at the NY/CT state line; more so heading south to NY than back to CT; see the Verizon Wireless Data Drops and Service Problems list for more details). In some cases, generally during rush-hour heading back to CT, perhaps 5% of voice calls will drop, but the incidence of the Merritt/Hutch (00119/00022) calls drops has been steadily decreasing. Most other carriers have finally managed to correct this as well, but they to have occassional drops there. The last Verizon Wireless voice drop in the area, in this case on the CT side between the Greenwich service area and the old Greenwich toll plaze occurred on 07/19/2014.
Fairfield County, New Canaan/CT-106 a bit west of Valley Rd.: Verizon Wireless has a large dead spot where both digital and analog services drop for a stretch of about 3/4 of a mile heading either east or west on Valley Rd. CT-106 goes between US-7 and downtown New Canaan (and continues south to I-95 from there). Coverage from US-7 to Valley Rd. is "OK" to "poor", then totally dead for 3/4 of a mile west of Valley Rd., and then picks up a bit while driving into downtown New Canaan. Drops are just as bad heading west on CT-106 from downtown New Canaan to Westport. Reported initially on 03/12/1997, tested again on 06/29/2003, no resolution as of yet. As of Jan 5th, 2016, this is still a problem area, although less prone to drops. Still drops on July 6th, 2018.
Fairfield County, New Canaan: Verizon Wireless drops calls on Old Kings Highway, which breaks off of CT-106/New Canaan Rd. heading east towards the New Canaan/Wilton Line, about 1/2 a mile west of the New Canaan/Wilton town line. Likely part of the generally poor Verizon Coverage in eastern New Canaan (north of the Merritt and east of CT-123) as well as the poor coverage specifically along CT-106, there is also a Verizon data drop along Old Kings Highway in the same location as well. Most recently occurred: 07/07/2018.
Fairfield County, New Canaan/Norwalk: Calls drop when traveling on CT-15 (Merritt Parkway) at exit 38 at the JCT with CT-123, between New Canaan and Norwalk, e.g., west of the US-7 interchange and east of the New Canaan Rest Area. 4G/LTE and 5G calls (if/when there -is- any 5G available there) drop 1/4 of a mile west of CT-123. This has been a perennial problem spot for Verizon, and since the inception of cellular service in the 1980s, they have always had a drop and/or poor coverage along the Merritt in the New Canaan area. It's amazing that callers are still being dropped there in 2024! In fact, pre-4G/LTE, drops were less frequent as compared to today. Most recently occurred on 07/17/2024.
Fairfield County, Norwalk: Verizon Wireless calls drop along the Merritt Parkway/CT-15, approximately 2 miles east of the US-7 JCT, more often in the southbound (compass west) direction. Calls drop very quickly and with little "warning", and coverage is weak in the area. Drop was tested on a Verizon-provided, 4G/LTE phone, as well as other relatively new phones which work well elsewhere. Most recently occurred: 08/11/2024.
Fairfield County, Trumbull: Verizon Wireless calls drop along CT-15/Merritt Parkway near the JCT with the (typically for CT) unfinished CT-25 freeway. The drop usually happens at night, and calls generally started to the north (east really) will drop passing under the CT-25 overpasses (also under the railroad bridge which seems to have never been used for service). The drop does not happen consistently, but still does on a sufficient basis to ummm..."merit" posting here! Most recently occurred: 08/26/2017.
Hartford County, Granby: Verizon Wireless calls drop along CT-20 just east of Eastwood Road, despite good coverage along CT-20 on both sides of the drop. No idea why it drops there with generally good coverage. Most recently occurred: 07/07/2019.
Hartford County, Hartford: Verizon calls drop (still!) just west of the I-84/I-91 JCT/interchange. Calls initiated to the west along I-84 (such as in Southington) will still sometimes drop prior to the covered roadway in Hartford. Calls begin to deteriorate passing the Hartford Courant/CTNow building, and drop just before entering the covered roadway. This has been going on since analog service started (before the roadway was even as covered and before the I-84E/I-91N flyover ramp was built!), and while it doesn't happen too often anymore, it still from time to time does, even late at night. Most recent instance occurred on 05/16/2021.
Hartford County, Plainville: Just west of the I-84 and CT-72 concurrency (where both highways merge for about a mile into one 5-lane highway), CT-72 splits off heading west, while I-84 heads southwest towards Southington. About a mile after the westward split, as the CT-72 freeway crosses CT-10/Queen St., Verizon calls drop. Heading east on I-84, calls drop about 1 miles west of the JCT with CT-10. Most recent instance occurred on 11/03/2019.
Litchfield County (at large): Generally there are no handoffs between Verizon's 00119/CT-A system and the ATT&T Wireless (ex-Cingular) 01001/CT-A system. (BAMS/Verizon's A system in CT, SID-00119, unlike SNET's (pre-AT&T Cingular) B system 00088, up until 2003 or so, did not provide service in the entire state of CT, and shared the A-side service in Connecticut with AT&T Wireless/Cingular/01001 which bought out the small A-carrier in Litchfield around 1996 or so...). Driving north of Torrington on CT-8, calls initiated on Verizon/BAMS/00119 drop at the apex of the hill heading up away from Torrington, and do not hand off to the what was the 01001 system. The same is true heading south, and calls on formerly-AT&T's network start to degrade along CT-8 at JCT CT-229 and drop at the apex of the hill; they will generally not hand off to BAMS. Reported to both AT&T and Verizon on 04/10/1999, no resolution as of yet.
Note: In the early 2000's Verizon acquired this 01001 system, and branded it as the rest of the CT-A system with "00119". However, as of late 2014, drops between the two systems still occur in some areas (CT/MA/NY border area along and west of US-7 for example). Data Service (3G/4G) drops also occur along the ex-01001/00119 demarcation which may (or may not) still be related to the vestigal separation of the markets; please see the Verizon 3G/4G Data Drops List for details.
Litchfield County, Bull's Bridge: Verizon Wireless service experiences call drops and generally poor coverage on US-7 approximately one mile north of the JCT of US-7 and CT-55, along 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 (with somewhat weak coverage at the JCT with CT-4 in Cornwall Bridge, but voice calls usually don't drop there). 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, Cornwall: Verizon Wireless calls drop along CT-43, just north of JCT CT-4, on the way up to CT-63 and Canaan, CT. While service isn't great along CT-43 north of CT-4, most of the rest of CT-43 is drop-free (although with the poor coverage it's hard to actually converse). AT&T Wireless drops in the same spot as well, while Sprint and T-Mobile have no coverage at all in the area (typically, of course). Most recently observed: 07/07/2019.
Litchfield County, Lakeville: Verizon Wireless drops (voice calls) 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. Voice (and data) 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, or at least identified as, 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 voice 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: 07/07/2019.
Litchfield County, Lakeville: As per above, if a call does by some chance manage to hold past CT-112, northwards past the Hotchkiss School, it will drop heading downhill before reaching US-44 in downtown Lakeville. (And of course Sprint and T-Mobile have no coverage in the area, while AT&T Wireless has a similar drop in nearly the same location just south of CT-41 hitting US-44.) Most recent instance observed: 07/07/2019.
Litchfield County, Gaylordsville (to NY/00486/00404 System): Verizon call drops occur on CT/NY-55 at the border between NY and CT. Calls placed on either side of the NY/CT border will drop just west of the CT border (westbound) or just slightly east of the NY-55/CTY-22 junction (eastbound). This may be due to the lack of any coverage for approximately 2 miles on the Verizon/00486 (now 00078/Albany; the SID seems like it was changed in 2014 or around there) system along NY-55 in the vicinity of the JCT NY-55/CTY-55 (as noted in the New York State section of this list). Interestingly, calls -do- hand off and transit to/from CT/00119 and NY/00486 along Bull's Bridge Rd/CTY-22, from US-7 south of Kent, through the covered bridge, to CTY-22 in New York, and then NY-55. Drops occur on both the 3G and 4G networks (there is no 5G coverage there), using 4G/LTE phones provided by Verizon. Most recent drop occurred on 04/10/2024.
Litchfield County, Kent: Drops occur just west of JCT of US-7 and CT-341, after the Kent School (where coverage is acceptable), just before entering the state of New York. The reverse is also true when driving from the Verizon NY/00486 (now 00078) system to CT. Most recent instance occurred on 08/22/2023.
Litchfield County, Lime Rock: Verizon Wireless voice 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. (Generally, the worst/weakest coverage is in the town of Lime Rock (in the 35 MPH zone), and if you speed fast enough through the 35 zone, you often can hold a call between US-7 and CT-41, but you have to drive pretty fast!) First observed on 07/20/2015, most recent instance occurred on 08/30/2022.
Litchfield County, Northfield: Verizon Wireless calls drop along CT-254/Northfield Road (which runs from CT-8 in Thomaston northwestwards up to CT-118 just east of Litchfield) at the JCT with Knife Shop Road. Most recent instance occurred on 07/05/2019.
Litchfield County, Litchfield/Warren: Verizon calls drop on CT-341 approximately 1/2 of a mile west of US-202 (which is where CT-341 starts its westward path towards Warren and Kent), passing. Coverage does not resume until the "stinking farm" near the JCT of CT-341 and CT-45. Even in 2023, after the 4G/LTE migration, there is still no coverage for 4 or 5 milesalong CT-341! It's been over 35 years since cellular service started - why can't this road be properly covered??? Verizon's coverage west of Warren/CT-45, all the way "down the hill" to Kent, is also very poor and "droppy", and pretty much useless until one gets just east of US-7 in Keny. Most recent instance occurred on 07/11/2023.
Litchfield County, Norfolk/East Canaan: Verizon Wireless voice drops occur along US-44, between the JCT with CT-272 in Norfolk, heading west uphill over to East Canaan. Coverage degrades approaching the apex of US-44 between Norfolk and East Canaan, and doesn't maintain (eg, drops) heading down/westward to East Canaan. Typical poor wireless coverage in Litchfield County, but Verizon is certainly better than Sprint/T-Mobile, both of which have virtually no coverage in the area at all. VZW still needs to make dramatic improvements in the area, which even as of 2019 it seems very slow to do. Most recently observerd: 09/22/2019
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 Amenia, NY. The problem seems to be again that there is no apparent handoff anywhere 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: 06/28/2019.
Litchfield County, Sharon: Verizon Wireless calls drop and experience poor coverage along CT-4/Cornwall Bridge Road, between US-7 (Cornwall) and CT-41 (Sharon) in a number of locations, one being at the intersection with Dunbar Road. There is little Verizon coverage between the CT-41 and US-7 segment endpoints, and calls initiated at each end drop repeatedly traveling from one "side" of the CT-4 segment to the other. It may also be a result of the apparent failure of Verizon to implement handoffs between its vestigal systems, as the western section of CT-4 in Sharon (at the JCT of CT-4 and CT-41) appears to be covered by the Verizon/Dutchess County 00486 system (now part of the Albany 00078 system), while the eastern section at JCT US-7 is covered by the Verizon CT/A/00119 market. Last observed: 07/02/2019
Litchfield County (at large): Generally there are no handoffs between Verizon's 00119/CT-A system and the Cingular (formerly AT&T Wireless) 01001/CT-A system (BAMS/Verizon, unlike SNET/pre-AT&T Cingular, does not provide service in the entire state of CT, and shares the state with AT&T Wireless/Cingular which bought out the small A-carrier in Litchfield around 1996 or so...). Driving north of Torrington on CT-8, calls initiated on Verizon/BAMS drops at the apex of the hill, and will not hand off to the ex-ex-ATTWS, ex-Cingular, currently US Cell system. The same is true heading south, and calls on formerly-AT&T's network start to degrade along CT-8 at JCT CT-229 and drop at the apex of the hill; they will generally not hand off to BAMS. Reported to both AT&T and Verizon on 04/10/1999, no resolution as of yet. Note: In the early 2000's Verizon acquired this 01001 system, and branded it as the rest of the CT-A system with "00119". However, as of late 2014, drops between the two systems still occur in some areas (CT/MA/NY border area along and west of US-7 for example). Data Service (3G/4G) drops also occur along the ex-01001/00119 demarcation which may (or may not) still be related to the vestigal separation of the markets; please see the Verizon 3G/4G Data Drops List for details.
New Haven County, Wallingford: Calls drop while traveling on I-91 between exits 14 and 15 and exits 25 and 36. Last occurred: 02/02/2005
Windham County, Brooklyn: Drops occur while travelling on US-6 and driving over a hill approximately two miles east of the JCT of US-6 and CT-97. Most recent instance occurred on 10/14/2009.
Windham County, Thompson: Verizon Wireless call drops occur while heading south on I-395 at the state line with Massachusetts. Most recent instance occurred on 01/30/2011.

Delaware

New Castle County, Claymont/(Wilmington): Verizon Wireless Calls drop on I-495/Wilmington Bypass just south of the JCT with US-13/Philadelphia Pike, more often in the southbound direction than northbound. Last observed: 08/14/2017. Appears it may have been corrected as of 05/05/2019; willneed further testing.
New Castle County, Newark: Verizon calls drop along W. Chestnut Hill Road, just north of the intersection with Otts Chappel Road. Even though W. Chestnut Hill Rd. is a relatively small road, it sees an inordinate amount of traffic as local drivers (and smart drivers from I-95) divert around the DE/MD line toll and use the route, along with DE-896 and MD-279 as a quick toll bypass and generally cheap area to purchase gas (they Delaware side is generally a few cents cheaper along DE-896, although the WAWA along MD-279 right at the Maryland and Delaware state line can sometimes be comparable). In any case, why pay a toll on a road that was paid off years ago when it can easily be avoided, and as a bonus buy some cheap gas? (For additional information about why tolls are counterproductive and are symptomatic of government dysfunction, see the following pages: Anti-Road Tolling Outline and Discussion, Problems Created by Tolls, and EZ-Pass rates and how out-of-state EZ Pass holders are overcharged). Last observed: 04/28/2019
New Castle County, Delmarva Peninsula, both DE and MD side: Verizon's voice cellular service experiences poor coverage and drops on many of the local roads between the N/S line which divides DE and MD. E.G., while traveling from US-301 on the MD side eastward to DE, there is generally poor coverage until the JCT of US-13 or DE-1, and many of the other E/W roads also suffer from drops transiting from the Atlantic side to the Bay side. Last observed: 01/16/2006.

Maryland

Anne Arundel County, Rose Haven, Eastern Shore: Almost the entire stretch of MD-261 near the Chesapeake Bay from MD-2 is completely devoid of coverage on all carriers, although AT&T Wireless does have a somewhat higher lever of service there. Last occurred on 06/16/2006; Verizon has improved coverage as of the summer of 2013 but there are still problematic drops on MD-261 with all carriers and the road is still not problem-free.
Baltimore County, Avalon/Relay/Ellicott City: Verizon drops calls and suffers from very poor coverge along the Patapsco River, traveling on River Rd. on the south side, and Geln Artney Rd. on the north side of the 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: 04/10/2021.
Baltimore County, Baltimore, Baltimore (train) Tunnel: North of Baltimore Amtrak/MARC trains go through a tunnel; calls often drop there or at the very least switch from digital to analog. (90% of the time calls drop, 10% there is a sloppy drop to analog.) Last tested: 05/21/2004.
Baltimore County, Towson: Verizon Wireless calls drop on the Baltimore Beltway/I-695 at Exit 29/MD-139/Charles Street. Seems to be a new drop for 2019, and generally it occurs only on the inner loop (heading northeast in the Towson area). Last observed: 05/22/2019.
Cecil County, Port Deposit / (See also the Havre de Grace/Harford County Drops in the same general area on the southern side of the Susquehanna River): Verizon Wireless calls drop at the JCT of US-1 and US-222 (where US-222 heads north to Pennsylvania away from US-1; there is a Royal Farms gas station at the NW corner). Calls which do not drop while traveling over the Conowingo Dam on US-1 will generally drop at or just south of the Royal Farms gas station. This appears to be a relatively new problem as of mid-2018. Most recent instance occurred on 11/28/2019.
Cecil County, Port Deposit/Susquehanna River Crossing (See also the Havre de Grace/Harford County drops in the same general area on the southern side of the Susquehanna River): Verizon calls drop at times (~80%) along I-95 at Mile Marker 93.3, just north of the JCT with MD-222 (not to be confused with US-222, which heads instead over to Port Deposit just north of the Conowingo Dam). The area along I-95 north of Port Deposit/Havre de Grace between up to the Chesapeake Rest Area had historically been an area of poor coverage for all carriers, but Verizon had more or less fixed the problem in the mid-2000's; as of late (Jan2018) drops along this 4 or so mile stretch of I-95 have resurfaced for some reason. Most recent instance occurred on 12/17/2018.
Frederick County, Myersville: Verizon wireless drops occur westbound on I-70 just past the Maryland Rest Area, at the handoff between the Verizon/00018 system and the US Cellular/1794 system, approximately 25% of the time for Verizon postpay customers (often less as of 5/2017). In the cases of Verizon resellers, MVNOs, and possibly pre-pay customers, drops seems closer to 100% of the time, such as in th case of Straight Talk, which will not allow a hand-off along the westward transition between Verizon/DC/00018 and US Cell/Hagerstown/01794 on I-70. This is another example of how resellers/MVNOs, in this case Straight Talk, appear to carelessly use Verizon's coverage map when in fact they do NOT offer coverage in the US Cell/01794 market; they used to allow calls initiated in the Verizon/DC/00018 market to roam onto the US Cell/01794 market but have now apparently blocked such calls and all calls fail westbound when reaching the top of the hill on I-70 which serves as a demarcation point between the 00018 and 01794 systems.

NOTE: Somewhat atypically, AT&T Wireless, Sprint and T-Mobile do NOT drop on I-70 at the Myersville Rest Area/hill apex, and offer continuous coverage from Frederick westward to (at least) JCT I-81 in Hagerstown, and then northwards along I-81 into Pennsylvania (where the Verizon/Scranton/00096 system kicks in). This may be due to there being a roaming market which Verizon has to deal with (US Cell/01794) while AT&T, Sprint, and T-Mobile do not, and thus Verizon may have drop/disconnect issues during the roaming handoffs between the Verizon and US Cellular markets, but roaming handoffs are an old issue which should have been corrected a decade ago.

Last observed with a Verizon postpay account/phone: 05/18/2017
Last observed with a Verizon MVNO account/phone: 05/18/2017

Frederick County, Smithburg: Verizon Wireless calls drop along MD-77 at the JCT with Labrador Road, approximately 2 miles east of Smithburg and the JCT with MD-64. Interestingly, unlike AT&T Wireless and perenially poorly-covered T-Mobile, Verizon manages to hold coverage along MD-77 through Catoctin Mountain Park, and only seems to drop around where the handoff to the US Cellular system would take place. Most recent instance occurred on 05/29/2024.
Harford County, Havre de Grace/Perryville (on Amtrak/MARC trains): Verizon Wireless drops calls and has very poor coverage from approx 6 miles north of Havre de Grace / Port Deposit (is there a Port Return on the other side? :) ) to approx 10 miles south of the river crossing; calls drop, there are areas of no coverage, etc. Note that along I-95, a few miles "inland", there is very good coverage, so this may be a local issue affecting US-40 or roads (and rail lines) closer to the water. This is a glaring hole in Verizon's coverage. Last tested: 04/20/2009. (Note that this has likely been fixed as of 2018, but we have no results from Amtrak since no one wants to put up with their nonsense anymore; see Amtrak Rewards Typical Nonsense and Amtrak Quiet Car Typical Nonsense).
Harford County, Havre De Grace: Verizon Wireless calls drop heading south on I-95 near or just south of the JCT with MD-155. Calls initiated on the north side of the Susquehanna River will generally drop after crossing over the river from Cecil to Haford Counties, and after cresting over the hill, calls begin to atennuate and then drop at or within a mile south of JCT with MD-155. Most recent instance occurred on 11/27/2019.
Harford County, Level/Darlington: Verizon calls drop when driving on MD-155 at the JCT of MD-161, and then turning east onto MD-161/Darlington Rd. Calls drop approx. 1/2 mile east of the MD-155/161 JCT. Most recent instance occurred on 10/02/2018
Harford County, Level/Aldino: Verizon call drops occur on MD-155 near the JCT of Paradise Rd when traveling in either direction on MD-155. Most recent instance occurred on 10/02/2018.
St. Mary's County, Chaptico: Drops occur at the rotary of MD-234 and MD-238. Most recent instance occurred on 09/23/2010.
Montgomery County, Bethesda: The opposite of a drop - Verizon is the only carrier with coverage in the Bethesda Harris Teeter throughout the whole store and in the garage, while AT&T Wireless and T-Mobile do not. 01/21/2024
Montgomery County, Darnestown: Verizon Wireless voice calls drops on MD-112 between MD-128 and River Rd/MD-190, drops occur at the JCT with Cervantes Rd. Most recent instance occurred on 03/18/2012.
Montgomery County, Chevy Chase/DC Line: Verizon Wireless has poor coverage and calls drop along Connecticut Ave/MD-185, from the District Line at Chevy Chase Circle/Western Ave, northwards along Conn Ave past the Chevy Chase Country Club (to the west), up until the JCT with Bradley Lane/MD-191. Verizon has weak/poor coverage along Connecticut Ave between Bradley and Western/Chevy Chase Cricle, and calls drop (or at least become inaudbile) along that span of Conn. Ave. Most recent instance occurred on 07/14/2019.
Montgomery County, Potomac: Verizon Wireless voice calls drop on MD-190/River Road and Marwood Hill Rd. Most recent instance occurred on 06/12/2011.
Montgomery County, Seneca: Drops occur approximately half a mile east of the JCT of MD-190/River Road and MD-112. Most recent instance occurred on 06/12/2011.
Washington County, Billmeyer Wildlife Management Area/Park: While not a Verizon Wireless drop per se (as Verizon doesn't cover the area), US Cellular, which Verizon customers roam on along this stretch of I-68, drops west of Exit 64/M. V. Smith Road NE, between the Smith exit (Mile Marker 64) and Mile Marker 65. Both US Cellular and AT&T Wireless drop here (Sprint and T-Mobile have NO coverage here) thus Verizon customers roaming in the area (perhaps having been handed off from one of the surrounding Verizon systems to roam on US Cell) will drop as well, but it's not within Verizon's control other than to pressure US Cell to fix the issue. As both carriers (US Cell and ATTWS) drop here, we really can't single out US Cellular for poor/weak/lacking coverage as we normally do, but it seems like a problematic drop on a major Intersate which for 20 years has not been remedied, and will likely affect Verizon customers who have come to expect "through coverage" (with roaming handoffs), with this being one of the few (if not the only) drops a Verizon customer (roaming on US Cellular) will experience on the entirety of I-70/I-68 (Frederick to Cumberland) in Maryland. Most recent instance occurred on 06/10/2016.
Washington County, Hagerstown: Drops occur while driving east on Alt US-40 and transitioning to the Verizon-owned Washington DC/Baltimore system (SID 00018) from the US Cellular (SID 1794) system in Washington County. Although it remains uncertain if the drops occur when travelling west, calls certainly do not hand off when driving east on Alt US-40. Most recent instance occurred on 09/11/2011.
Washington County, Sandy Hook: Handoffs from the US Cellular/1794 system to the Verizon Wireless system will not occur even though there is almost perfect coverage on both systems on each side of the "drop", respectively. Most recent instance occurred on 06/24/2012.
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

Massachusetts

Barnstable County (Cape Cod), Orleans: Verizon Wireless calls drop or exeperience audio drop-outs near and passing throgh the Orleans Rotary where MA-6A and US-6 merge (heading east) / diverge (heading west). Calls east/north of Orleans can be choppy at times, perhaps from signal interference/multipathing from the mainland over the bay, or perhaps just due to poor coverage. (Cape Cod took a long time to have cellular coverage on the eastern end, due to land problems with an Indian group who prevented tower sitings for a while, but it is our understanding these problems were resolve by the 2000's and thus there should be no reason for such poor coverage between Orleans and Truro.) Most recently observed: 07/28/2017
Berkshire County, Egremont: Verizon Wireless call 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 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. ATT Wireless does not suffer the drop, and AT&T Wireless holds calls all the way into New York State to NY-22; this is detailed on the ATT Wireless Dropped Call List. (T-Mobile and Sprint have no coverage in the area so there are no drops on their respective lists.) If AT&T Wireless can provide a drop-free ride along MA/NY-23, why can't Verizon? Most recently observed: 08/15/2018
Berkshire County, Egremont: Heading east from NY along MA-23, after the above drop, Verizon Wireless has poor coverage along MA-23 eastward to MA-71/Egremont Plain Road, where Verizon calls drop again. Most recently observed: 08/12/2020.
Berkshire County, Great Barrington: Verizon Wireless calls drop along MA-41 at the JCT/intersection with Long Pond Road, just north of the JCT with US-7 where US-7 heads a bit to the northeast, while MA-41 heads slightly to the north and west (under the RR tracks). Sprint and T-Mobile also drop in the same spot, but AT&T Wireless does not drop, and provides through-coverage along MA-41 all the way to US-20 (near the Hancock Shaker Village) and then along US-20 into Pittsfield. If AT&T Wireless can cover MA-41 so well, why can't Verizon? Most recently observed: 07/07/2019.
Berkshire County, Great Barrington: Verizon Wireless calls drop along Christian Hill Rd. at the intersection with Division Street, and continuing west on Division Street, to Seeknk Rd, and onwards to the NY State line and re-joining MA/NY-71 just west of the line, Verizon has very poor coverage and calls drop regularly. (Compare to AT&T Wireless which suffers no drops along the entire route; why can't Verizon offer a similar level of coverage in the area?). Most recently observed: 07/18/2019.
Berkshire County, Great Barrington/North Egremont: Verizon drops calls along Boice Rd., just south of it's eastern/northern end at JCT with Seekonk Rd. Coverage on Verizon is generally not very good in the area (as compared to AT&T Wireless which offers drop-free coverage on the same route), and there are multiple audio drop-outs and other coverage problems along Boice Rd., from Seekonk Rd. all the way southwestward to North Egremont and the JCT with MA-71. Most Recently observed: 07/18/2019.
Berkshire County, Hancock: Verizon Wireless calls drop along Brodie Mountain Road (which runs east-west from US-7 to MA-43, with Jay Speak Ski Area towards its western end near MA-43) just west of JCT US-7, and suffers poor coverage for a few miles west of there. With all the ski traffic in the winter heading to Jay Peak, one would think that for reasons of safety (if nothing else) that Verizon would do a better job at covering the area. Most recently observed: 07/07/2019.
Berkshire County, New Marlboro/Monterey/Great Barrington: Verizon Wireless voice cellular 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 areas of improvement 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, New Marlborough / Sheffield: Verizon Wireless drops calls and coverage is very poor along Norfolk Road (a continuation in Mass of CT-272) between the CT/MA state line and MA-57 (which is part of an even greater area of poor/no coverage in southwestern Mass, see the drops along MA-57/MA-23, above). Basically, there is poor to no coverage east of US-7 in Sheffield for a large swath between the CT/MA border north to MA-23 in Montery, all the way east to MA-8. The entire area of SW Mass has such poor coverage on ALL carriers (AT&T, Verizon, and T-Mobile) that it's shocking (if not potentially fraudulent) that they show coverage there on their maps! Anyone traveling north of US-44 on CT-272 up to MA-57 and MA-23 should expect to have no useful coverage on ANY carrier for most of the trip after entering into Mass. Last observed: 08/23/2023.
Berkshire County, Otis: Verizon Wireless calls drop (due to apparently poor/no coverage) just west of Otis along MA-23. MA-23 and MA-8 meet in Otis - MA-23 from the east joins and runs concurrently with MA-8 for 1/4 of a mile heading north, after which MA-23 splits off MA-8 and heads west. From thae westward MA-23 junction in Otis, up along the westward incline on MA-23, Verizon's coverage is good, but as MA-23 levels off just west of the town of Monterey, Verizon's coverage fades, and drops near the (white) church on the north side of MA-23. Coverage is spotty at best (and generally lacking altogether) until MA-23 heads back downhill further west approaching Great Barrington. See also the MA-57 drop, above. Basically very poor to no coverage by Verizon for a significant radius around Monterey; T-Mobile and Sprint of course have no coverage there at all, but AT&T Wireless does, serving as another example of how AT&T in many areas is slowly surpassing what once was Verizon's superior coverage. See the ATT Wireless Drop List for details. Initially observed: 8/16/2018, last observed: 09/07/2020.
Berkshire County, West Stockbridge: Verizon Wireless calls drop along MA-41, just north of West Stockbridge, at or just south of the JCT with MA-102/State Line Road (which, by chance, heads west to the NY State line and ends at NY-22 just south of the Masspike/NYS Thruway Berkshire Extension). Last observed: 02/12/2022.
Berkshire County, Williamstown: Verizon Wireless calls drop along MA-2/NY-2 at the MA/NY line in the Taconic Ridge State Forest. As in so many cases where (legacy) Verizon systems were crossed, calls here, between the CT/Western Mass "A"/00119 system (which covers Williamstown) and the NY/Albany "B"/00078 system (which covers the NY side of MA/NY-2 as it comes down the hill from the State Forest and heads west to NY-22 and Troy, NY), drop right at the handoff between the two system. And it's not that there is no coverage - Verizon has relatively good coverage along the route from the JCT with US-7 in Williamstown south and then westwards to the JCT (old interchange, really) with NY-22 in NY - it's just that when an active call crosses from the 00119 system to the 00078 system at the apex of MA/NY-2, they don't hand off, and just drop. This is typical of Verizon in many areas where they simply do not hand off between markets, such as between CT/NY (except on I-95, the Merritt Parkway, and I-84), CT/NY (the Masspike/I-90) and NY/VT (nearly all roads; maybe not the new Bennington bypass). Most recent instance occurred on 08/30/2018.
Franklin County, Greenfield: Drops occur while driving on I-91 at the northern JCT of MA-2. This given Verizon call was initiated was in Vermont and then transitioned down from Vermont on I-91. This may have something to do with a call being initiated in Vermont and successfully transitioning in to the Massachusetts system and then dropping. No tests have been made to determine if calls drop when driving the other way. Most recent instance occurred on 05/23/2010.
Hampshire County, Amherst: US-202, no through service along US-202, from MA-9 north to just south of MA-2, where coverage picks up again. (Cingular/CO Boston 00007 does a somewhat better job along this route.) Last tested 08/01/2006.
Hampshire County, Huntington/Knightville/Knightville Dam: Verizon Wireless coverage drops along MA-66, heading west from Northampton (and further west Westhampton), along the hill heading down MA-66, a few miles east of the JCT with MA-112, near and south of Knigthtville Dam. While (needless to say) T-Mobile has barely any coverage there, AT&T manages to maintain a connection quite well, so why can't Verizon do the same? Most recent instance occurred on 08/22/2023.
Middlesex County, Wakefield: An (isolated?) drop occurred on RT-128 in the Wakefield area while crossing under the Hopkins St. overpass. Most recent instance occurred on 05/15/2006.
Worcester County, Athol: MA-2, just west of US-202S JCT: Calls won't transition/maintain to the to US Cell 01484 system or whatever agreement Verizon has in place for its customers in Franklin County. Analog calls from the 00028 to the 01484 do seem to hand off, but drop westbound (from 00028 to 01484) a bit after Athol (admittedly this is an error on US Cell's side), and eastbound (from 01484 to 00028) at the northbound JCT of MA-2 and US-202 (MA-2 and US-202 are multiplexed for a bit). Digital (apparently 01484 supports CDMA as of late 2005) handoffs fail in approx. the same areas. Last tested: 05/21/2006
Worcester County, Charlton: Verizon Wireless calls drop along US-20, west of Aubrun and east of Charlton, in the vicinity of Glenmere Rd. US-20 generally parallels the Masspike (I-90) for most of its run in Massachusetts, and is only a mile or two south of the Masspike between Auburn and Charlton, yet ever since the inception of Verizon's CDMA digital service in the late 1990's, calls have regularly dropped along US-20, particularly in the westbound direction (both voice and data connections), likely due to poor coverage, and the issue has never been remedied. Drop first started: Late 1990s; Most recent instance occurred: 07/26/2019

New Hampshire

Cheshire County, Fitzwilliam: No coverage on Verizon Wireless 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. Essentially, no cross-system hand-offs, which result in drops. Most recently observed on 07/08/2012.

New Jersey

Alpha/I-78: Calls drop on I-78 just 3-4 miles east of the PA-NJ state line. Last tested: 07/26/2004
Bergen County, Mahwah: Verizon drops calls along I-287, in the Mahwah, NJ/Sufferin, NY area, at between Mile Markers 64 and 65, just south of the I-287/I-87/NJ-17 interchange. Verizon calls begin to attenuate just south of the split with NJ-17, and by the time the speed limit on I-287 increases from 55 to 65 MPH near Mile Marker 65, Verizon voice calls will generally drop. This has been an "on and off" problem for many years - sometimes it happens, sometimes it does not - but there is really is no reason for this to continue for so long. And as of mid-2019, Verizon's calls more often drop there than don't, so it's getting worse. Most recent instance occurred: 05/17/2020.
Camden County, Pennsauken Township: Verizon call drops occur while driving on US-130 near the JCT of NJ-32 and US-130, in the vicinity of Mile Marker 70 and Airport Circle. Most recent instance occurred on 02/27/2011.
Gloucester County, West Deptford Township: Voice drops on Verizon occur along I-295 between Mile Marker 18-20, connections deteriorate and then drop. Last tested: 01/19/2006
Mercer County, Princeton area on Amtrak/NJ Transit: calls drop both northbound and southbound between the NY/00022 and Philly/South Jersey/00008 markets about 7 miles north of the Princeton Jct. station (e.g., wherever the handoff between the 00008 and 00022 markets occur). Drops occur on the order of 75% of the time. Last tested: 07/20/2004.
Mercer County, Trenton: At the JCT of US-1 freeway, approaching the JCT with US-13 heading north, digital coverage begins to deteriorate and drops upon reaching the left exit for PA-32(?) just south of the US-1 Trenton bridge. Drops occur approx. 70% of the time. Last tested: 06/10/2003.
Mercer County, Trenton/Washington's Crossing: Verizon Wireless calls drop just east of the Washington's Crossing bridge at the JCT of NJ-29 (which runs along the east side of the Delaware River) and CTY-546 (Washington Crossing - Pennington Rd.). This Verizon drop was recently detected due to all the traffic diverting from the previously free I-95 (and as of late 2018 renumbered as I-295) Scudders Falls Bridge to the Washington's Crossing bridge a few miles to the north (which is free). (See the YourTollsAtWork anti-tolling page for details; the Scudder's Falls Bridge was the only free Interstate Highway bridge crossing the Delaware, and the Delaware Bridge Commission was desparate to errr..."monetize" it, so they let the old bridge (free) fall into a state of disrepair, and then claimed that a second (southbound) span was needed, which would be paid for with electronic/spy tolling, so the previously free crossing is now tolled, causing diversion onto narrow, car-only bridges along the Delaware which are free.) Most recent instance occurred on 09/09/2019.
Morris County, Morristown: Verizon Wireless drops calls along I-287 at the JCT with NJ-10 just east of Morristown. This is a newer drop (post-2016) and may have to do with their poorly-managed migration to LTE. Most recent instance occurred on 08/01/2018.
Morris County, Parsippany: Verizon calls drop on I-80 at approximately Exit 33 or Exit 34. The drop occurs where the speed limit is increased from 55mph to 65mph. It is approximately five miles east of the junction of I-80 and I-287. Most recent instance occurred on 01/18/2009.
Passaic County, Clifton: Calls drop on NJ-3 approximately 1 mile east of the JCT with NJ-21, in the general area of the eastern section of the rebuilt portion of NJ-3 east of the Passaic River. Most recent instance occurred on 12/20/2014.
Somerset County, Osborn Mills/Basking Ridge: Verizon Wireless calls drop along I-287 just north of JCT CTY-613/North Maple Ave (exits 30A/B). Drops occur about 30% of the time in either direction. (This is very close to a number of Verizon complexes, including their old(?) corporate headquarters further down the road in Bedminster!). Most recent instance occurred on 06/06/2016.
Somerset County, Bedminster/Somerville: Verizon drops calls along I-287 at Mile Marker 23.4, just north of Exit 22 for US-202/206, with the little connector freeway between I-287 and US-22. Calls initiated along I-287 to the north (such as near Pompton Lakes) will drop passing MM23.4 when traveling from the north (heading southbound), while from the south, calls will generally drop at Exit 22. Most recent instance occurred on 03/18/2022.
Union County, Clark: Verizon drops occur on the Garden State Parkway the vicinity of Exit 137 for Clark Township/Kensington. Calls initiated north of Exit 137 (or on other nearby roads, such as US-22 where the Exxon is (and where the Shark Aquarium used to be from the east, or Maplewood from the west) will generally drop between Mile Marker/Exit 137 and MM 135. Northbound, calls initiated on the Parkway or nearby roads (I-287/NJ-440 for example) will distort around MM 135 and drop entirely by MM 137. This is not one of the "new" problems, that is, a drop which started around late 2017 to early 2019 but which was fine before this period; the drop in Clark/Kensignton with Verizon has been around as far as we can tell since cellular service started - analog service always dropped and it wasn't much better after conversion to digital in 2007. Most recent instance occurred on 05/05/2019.
Union County, Edgewater: Verizon drops calls along River Road/CTY-505 at the JCT/intersection with Palisades Med. Rd. Calls rapidly deteriorate in the general vicinity of the intersection, and generally drop within a few hundred feet of passing through in both the nortbound or sounthbound directions. Most recent instance occurred on 10/14/2019.
Union County, Edgewater: Verizon calls drop along River Road/CTY-505 at the intersection with Gorge Road, just south of the Homewood Suites/Hilton and Original Pancake House mini-shopping/residential plaza to the east of River Road. Most recent instance occurred on 10/14/2019.
Union County, Weehawken: Verizon Wireless calls drop along JFK Boulevard East just south of the overlook (with the view of NYC), at the intersection with Highwood Avenue, Duer Place, and Parkview Avenue. Most recent instance occrred on 10/14/2019.

New York

New York City 5-Borough/Counties:

Bronx - Verizon calls drop along I-87/Maj. Deegan Expressway near Exit 11, just south of the Mosholu Parkway interchange and the service area (gas station) near the Westchester County/Yonkers line. Verizon's calls drop more often in the northbound direction (30% of the time), and a good deal less southbound (perhaps 15%). Drops occur at all times of day, that is, not only in heavy rush-hour traffic, but on weekends, late at night, etc. Most recent instance occurred: 07/02/2017
Kings County (Brookyln) - Williamsburg: Verizon Wireless voice 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 data services are affected as well, see the Verizon Data 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, calls take a long time to set up, text messages are slow to arrive, and data is slow. 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 08/05/2017.
Kings County (Brookyln) - Williamsburg: Verizon Wireless calls drop along Kent St. and North 5th. Even while walking along N.5th street, calls drop when heading west (towards the East River) approaching Kent St. Most recent instance occurred on 08/14/2017.
New York County - Manhattan: Verizon Wireless voice drops occur while passing through the East River tubes which are utilized by Amtrak and the LIRR to access Penn Station. Reported to Verizon on 03/18/2008. Verizon indicated in 2010 that they were aware of this issue and that it affect the northern two tubes (generally used for inbound service) and that the southern two tubes (usually used for outbound service) did not experience similar drops. Our tests found the same, and as of late 2013, drops were still occurring from time to time in the north tubes (not sure if in both tubes or only the northenmost one), but we rarely if ever experience drops in the southern ones heading from Penn to Woodside. In 2017, we started noticing drops in the southernmost tube outbound, with the drop occurring closer to Penn than the Long Island City portal. As of May, 2018, drops were occurring on both outbound (eastbound) tubes. Most recent instance occurred 06/01/2018.
New York County - Manhattan: Penn Station, LIRR Concourse: Verizon drops occur at the mid-mezzanine staircase for track 17. Most recent instance occurred on 04/01/2012.
New York County - Manhattan: There is no Verizon Wireless 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 09/15/2015.
New York County - Manhattan: Verizon calls drop exiting from the George Washington Bridge heading eastward ON 178th. St. Additionally, drops sometimes occur on the I-95 section "under the apartments", but it's much more common for the drop to occur on 178th St. heading east (as would be the case in the event of work on the FDR ramps under the apartments late at night with traffic diverted onto the 178th. St. to continue to the FDR ramps at street level). This specific Verizon drop does not appear to be a result of network congestion, but is more likely that of poor engineering, as drops occur at all times of day in dramatically varied traffic conditions. Most recent instance occurred on 12/07/2014.
New York County - Manhattan: Verizon calls drop in the vicinity of the West Side Highway/NY-9A and W57th St, where the road ends (that is, where the old West Side Highway was torn down an never replaced with an adequate road due to near impossibility of getting anything road-wise built there anymore, contrasted with Boston which had a much more challenging project with the Central Artery which _was_ completed and has made significant improvements both transportation-wise as well as to the aesthetics of the old Artery footprint and Rose Kennedy Park; NYC just built a big roadway with traffic lights which serves as a barrier between the Riverfront and the rest of the City instead of Westway which would have burried the highway.) Anyhow...Calls frequently drop or are attenuated traveling southwards from the mid-60s towards 57th, perhaps due to multipath or other interference from NJ. Calls continue to drop and/or attenuate until approx 42nd st. Most recent instance occurred on 04/11/2015.
New York County - Manhattan: Verizon Wireless drops calls along the Henry Hudson Parkway/NY-9A at/near 138th Street heading southbound. This ia a new drop which has been reported a few times starting in April 2018, and verified in early 2018; it seems to be mainly on older 800 MHz/1900 Mhz CDMA (and analog, but there is no more analog in 2018) phones. There have been a few LTE drops as well on newer phones, but the location is much less specific - some drop at 125th St, some drop at the 178th St. near the ramps to the George Washington Bridge/I-95. Is this a result of some frequency migration? Or perhaps some changes across the Hudson in New Jersey which are affecting line-of-sight drivers along NY-9A in Manhattan? Most recent instance occurred on 07/07/2018.
New York County - Manhattan: Verizon Wireless voice calls drop along Central Park West from 73rd down to 72nd street. Verizon customers engaged in a telephone call traveling along Central Park West (either driving or walking) will experience reduced call quality and/or frequent drops in the area. Typically, a caller walking down Central Park West from, for example, the Museum of Natural History will experience distorted voice calls after crossing 73rd St, and upon reaching the IND subway entrance on the NW corner of 72nd St, the call will drop completely. Most recent instance occurred on 08/16/2015.
New York County - Manhattan: Verizon Wireless calls drop while walking along Lexington Avenue at 56th Street, near an open-air market (an atypically unushed lot with some pre-fabricated booths). For whatever reason, Verizon calls placed in the area will deteriorate while walking northwards along Lexington Avenue, with audio dropping in and out, ultimately leading to the call dropping entirely. The issue seems relatively localized, and calls placed/received a block in any direction away from Lex/56th (and not passing through the area) do not suffer the same audio/drop problems. Most recent instance occurred on 07/10/2018.
New York County - Manhattan: Verizon Wireless calls drop entering the 59th Street/Lexington Ave IRT/BMT Station (4/5/6, N/R). Calls in-progress which are initiated outdoors will drop upon entering the (finally, as of Nov 2016) covered IRT platforms. Like the drops in Washington, and the drop (immediately below) on the West Side IND at 72nd, it appears for some reason that Verizon calls do not transit well from outside to inside many subway stations, the 59th/Lex station being one of them. Most recent instance occurred on 12/12/2016.
New York County - Manhattan: Verizon drops calls entering the 81st St./8th Ave (Central Park West) IND Subway (C/B/(A) lines) from the northwest entrance. Verizon Wireless customers who initiate a call prior to entering the subway and who enter from the northwest stairway (at the northwest corner of 81st and Central Park West) will have their calls dropped entering the subway mezzanine, even though there has been Verizon coverage (as well as every other carrier) throughout the 81st. St IND station for over two years. In other words, despite relatively good coverage both outside and inside the station, calls from the outside will not hand off to the inside, at least when entering from the northern stairway. (This is similar to the DC Metro, which has long had Verizon coverage in its stations, yet more often than not calls will drop when transiting from between the surface and the subway or from the subway to the surface.) Conversely, however, calls initiated inside the station do appear to hand off to the outside. Most recent instance occurred on 10/24/2016.
New York County - Manhattan: Verizon drops calls entering the Second Avenue Subway at 86th. St. Even though there is coverage in the three new 2nd Ave Subway stations (72nd, 86th, and 96th; a 79th station was foolishly not built to, typically shortsightedly, save money; but then, it also should have been built as a 4-track express/local system and that wasn't done either, again, typical of the myoptic way everything is done in New York), calls which are initiated outside at street level will disconnect/drop shortly after entering the station and descending to the mezzanine via the escalators. Note that this seems commonplace for most NYC (underground) subway stations where Verizon is pushed in via repeaters (those white boxes with the three white plastic domes coming down from the ceiling, or sometimes just one suspended by a pole) - the Verizon Dropped Calls List notes a number of subway stations on the Lex Ave IRT and the 8Th Ave IND where the same thing happens - Verizon calls simply will not hand-off/transit from the "outside" Verizon-owned system to whatever the "repeater" system is which conveys the Verizon Wireless signal(s) underground. This is not the case with T-Mobile and Sprint, and semalessly transit from street level to subway, and thus their calls do't drop - only Verizon drops calls entering subway stations (and this is true on the Washington, DC Metro as well). Most recent instance occurred on: 01/15/2017.
New York County - Manhattan: Verizon calls drop along East 57th St between 2nd and 1st Ave, approaching the Queensboro Bridge Upper Level ramp opposite "Mr. Chow" (restaurant), coming from both 1st Ave (heading west) and 2nd Ave (heading east) where traffic tends to back up waiting to enter the ramp (which is usually the case, even late at night, since tolls are something close to $7 now on tolled facilities, and most sensible drivers would prefer not to have to fork over $14 just to drive in and out of the delight which is Manhattan and it's driving splendor. This of course explains why every few years some disingenuous politician (a redundancy) comes up with an idea "to improve traffic and pollution" by tolling the free bridges, when of course what they really want to do is raise revenue and likely some kickbacks for/from the MTA which runs the substandard tolled facilities). As an update, this has been repeatedly duplicated on calls initiated on 3rd Ave heading north, turning east on 57th, and by the time 2nd Ave is crossed heading east, calls already suffer a good deal of attenuation. By the time the Queensboro Bridge Upper Level outbound 57th st ramp is approached, the call drops completely. This happens at all times of day, including late at night, when there should be little to no network congestion. It also occurs one calls which traverse 1st Ave (northbound), turn left (west) onto 57th, and then right onto the QBB Upper Level ramp, as noted before, almost opposite of "Mr. Chow". Most recent instance occurred on 10/02/2016.
Queens County - Woodhaven: Drops occur while driving on the Long Island Expressway starting in the vicinity of the JCT with Queens Blvd to slightly west of the JCT with Grand Central Parkway. Drops tend to occur more often while driving in the eastbound direction rather than the westbound direction. Most recent instance occurred on 03/19/2008; this may be more of a congestion issue - as of mid-2014 calls properly transit through the area except during high traffic volumes when they can still often drop.
Queens County - Maspeth: Verizon voice drops occur approximately 30% of the time heading Westbound on the Long Island Expressway/I-495 just prior to exit 18 in Maspeth, Queens, prior to the "uppler level/lower level split" (the latter of which serves as a transition to the BQE/I-278). Calls initiated east of Woodhaven/Queens Blvds will drop on the westbound downhill just prior to Exit 18/LIE Lower Roadway. Eastbound drops are more frequent (approx. 85% of the time), with a drop at both "ends" of the upper/lower roadway confirguration - the first where the lower roadway is joined by eastbound traffic from the BQE/I-278, and the second about 1/2 a mile east of the merge between the upper and lower roadways. Most recent instance occurred on 10/01/2018.
Queens County - Whitestone: The audio quality of Verizon Wireless calls sounds distorted and attenuates midpoint on the (highly overpriced, poorly maintained, backed up, and out of date, but that's true of any TBTA bridge in NYC!) Whitestone Bridge/I-678. Bad enough residents of Long Island are held hostage and extorted by the MTA/TBTA just to get on/off of the Island, but also having to have Verizon calls sound distorted while sitting in traffic waiting to pay tolls (or soon to be spied on by automated plate readers) is just too much to bear! Time to leave NY! ;(. Generally, not a major issue, and calls rarely drop, but for Verizon this is a surprisingly poor quality of service for such a heavily travelled road. Most recent instance of audio distortion occurred: 03/25/2017; most recent actual dropped call: 05/11/2017.
Richmond County, Staten Island: On NJ/NY-440, heading east/north, calls initiated in Jersey (or DE or anywhere else and driven through NJ) will fail while approaching or passing through the toll plaza. Digital calls drop 80% of time, and analog gets too staticky to use after passing through the toll plaza near the Richmond Parkway / NY-440 JCT. Call drop/fail rates after driving up to and passing the Fresh Kills landfill approaches 95%, e.g., VERY rarely will a call transit through from Jersey to north of Fresh Kills on SI. Verizon was notified about this on 06/14/2000, and then again in terms of Express Network drops on 11/2002, and still drops regularly occur. Express Network (1X and EvDO) appear more or less fixed as of late 2005; cellular (digital and analog) still having problems as of late 2006. As of 10/31/2010, digital cellular calls still drop in this vicinity, specifically at the mid-point of the NY/NJ-440 Outerbridge Bridge crossing.

New York State Counties other than New York City:

Columbia County, Ancram: Drops occur while driving on NY-82 at the JCT of NY-82 and CTY-7. Most recent instance occurred on 08/08/2010.
Columbia County, Ancram: Verizon Wireless voice calls and data sessions 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, Ancramdale: Verizon Wireless calss drop on CTY-3, approximately 1 mile before the JCT with NY-22. Calls initiated in Ancramdale which head east along CTY-3 will drop on at the apex of CTY-3 as it transitions downhill to the Harlem Valley along NY-22. Last occurred: 09/04/2018.
Columbia County, Austerlitz: Verizon call drops occur in the town of Austerlitz, along NY-22, just north of JCT NY-22/NY-203/CT-5 and just south of East Hill Road. This appears to coincide with the demarcation point between the Verizon/00119/A/CT and Western Mass system and the Verizon/00078/Albany system, so it is unclear if the drop is related to poor coverage or the failure to perform a system to system handoff between the CT/MA/"A" system and the Albany/"B"-side system. NY-22 in the area carries a good deal of traffic to the NYS Thruway/Masspike/I-90 just a few miles north of Austerlitz, and despite acceptable coverage near the Masspike as well as south of Austerlitz/JCT NY-28, this small area of dropping coverage and/or lack of coverage impacts a significant number of motorists. Last occurred: 09/26/2016.
Columbia County, Boston Corners: Verizon Wireless voice calls drop on NY-22 at the Dutchess/Columbia County Line, near Mile Marker 102, 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 in the Harlem Valley (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 occurred: 07/07/2019
Columbia County, Claverack: Verizon drops occur at the overpass for NY-23 over the Taconic State Parkway between NY-23 and Palmer Rd. Display never says no coverage exists but effectively none does. Most recent instance occurred on 08/08/2010.
Columbia County, Copake: Verizon Wireless voice calls drop 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: Verizon's 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: Verizon Wireless calls drop along CTY-7 at the JCT with Tinker Hill Rd. at the Gallatin Town Hall. Heading westwards, Verizon calls begin to detriorate around Ancram/JCT NY-82 (which has poor Verizon coverage as well), and audio 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, Gallatin: Drops occur while driving on NY-82 at Half Circle Rd and the access road to Taghanak State Park, which is approximately two miles north of the JCT of NY-82 and CTY-11. Most recent instance occurred on 08/08/2010.
Columbia County, Queechy: Traveling northward from the New York Thruway/I-90 on NY-22, Verizon's voice coverage begins to attenuate approximately one mile south of the JCT of NY-22 and NY-295/Canaan Rd. At the actual junction, Verizon calls drop completely and no service is available along NY-22 heading northwards until just south of the JCT of NY-22 and US-20 in New Lebanon. Most recent instance occurred on 07/06/2008.
Columbia County: Salt Point: Verizon's voice service often 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/2009.
Columbia County, Silvernails: Verizon Wireless calls drop along the Taconic State Parkway at JCT CTY-2(E)/CTY-50(W)/Jackson Corners Rd. (see also the Gallatin area drops as well, above). In fact, along CTY-2 near the Taconic on/off ramps (at a slightly lower elevation than the Taconic), there is no Verizon coverage at all. Most recent instance occurred on 10/02/2016.
Columbia County, Spencertown: No coverage exists along NY-203 between the Taconic State Parkway, through Spencertown, all the way to the JCT with NY-22 in Austerlitz. Coverage barely resumes in the vicinity of the JCT of NY-203 and NY-22, in the town of Austerlitz. Most recent instance occurred on 09/10/2016.
Columbia County, Spencertown: Verizon Wireless 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, Spencertown: Verizon 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: Verizon's coverage (voice and data) attenuates and then drops entirely while heading northward on NY-22 starting from the JCT with US-44 (western component) in Amenia and continues for approximately five or six miles north until the JCT of NY-22 and CTY-62 (eastern component) in Millerton, at which point coverage returns. (However, both AT&T Wireless/Dobson Cellular and Nextel both have perfect coverage in this area.) Most recent instance occurred on 07/06/2008.
Dutchess County, Amenia: Verizon 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/Leedsville Road. Similar to other Verizon handoff drops between Verizon systems between CT and NY (CT/A/00119 and NY/B/00486) aling US-44, NY/CT-55, NY/CT-341, etc.), there is generally good coverage on both "sides" of the drop, but calls just suddenly drop on both sides Leedsville Rd. Most recently observed on 07/05/2019.
Dutchess County, Beekman: Drops occur on NY-55 both a mile west and approximately two miles east of the JCT of NY-55 and the JCT of NY-216. Most recent instance occurred on 06/07/2018.
Dutchess County, Billings/Unionvale/Verbank: Verizon call drops occur on 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, which itself has weak coverage a few miles north of Tomkins Rd.) Most recent instance occurred on 03/19/2019.
Dutchess County, Billings/Unionvale: Verizon Wireless calls drop at/near the JCT of NY-82 and Tompkins Road, likely as part of the same problem coverage issue as above. Generally, when heading north on NY-82 (from NY-55), calls will atennuate and drop shortly after turning (right/east) onto Tompkins Road. NY-82 between NY-55 and US-44 has always been problematic for Verizon, and Verizon's coverage still suffers problems in the general area, even though NY-82 is relatively close to and parallels the Taconic Parkway in this area. Verizon also drops calls at times near the JCT of NY-82 and CTY-90, before coverage improves approaching Millbrook and US-44 (west/north)/NY-343 (east). Most recent instance occurred on 7/16/2016.
Dutchess County, East Fishkill/Shenandoah: Verizon Wireless drops calls along the Taconic State Parkway at Mile Marker 34 between the JCT with Miller Hill Road (east) / Shenandoah Road (west) and Horton Hill Road, approximately 3 miles south of the JCT with I-84. T-Mobile, AT&T Wireless, and Sprint also drop in the same location, but we generally expect a higher standard from Verizon and are surprised that drops still occur here in 2016! The Verizon drop at/near Miller Hill/Shenandoah is by no means universal, and calls will transit the area a good percentage of the time (50%), albeit with some noticeable and typical digital/CDMA audio distortion/drop-out/loss. Most recent instance occurred on 07/10/2016.
Dutchess County, LaGrange: Verizon calls drop along CTY-21/Noxon Road just east of the JCT withy CTY-49/Titusville Rd. Calls initiated along CTY-49, for example at Dutchess County Airport, or on CTY-21/NY-55 before the two split east of the Dutchess Rail Trail, will drop shortly after heading east past the junction of CTY-21/CTY-49, as CTY-21 heads up a slight incline and makes a gradual left turn. On the downhill of the incline, calls will drop. Most recent instance occurred on 02/02/2019.
Dutchess County, LaGrangeville: Verizon's coverage is poor on NY-82 for approximately a mile and a half beginning at the JCT with Tompkins Rd. The attenuated coverage may or may not result in a dropped call. Most recently occurred on 08/26/2012.
Dutchess County, Milan: Significant coverage drops occur on the Taconic Parkway for eight or so miles, between JCT NY-199 (Mile Marker 68), heading northwards past North Rd, Wilbur Flats Rd, and Ferris Rd, up to the JCT with CTY-2/Jackson Corners Rd. Verizon voice calls will drop while data is weak but remains connected. Last occurred on 10/04/2016, last reported to Verizon Wireless on 06/07/2012.
Dutchess County, Millbrook: Drops occur while driving on CTY-23 between the JCT of CTY-24 and NY-343. The drop occurs closer to the JCT of CTY-24 and CTY-23 than the JCT of NY-343 and CTY-23. The stretch of NY-343 from the Dutchess Day School (where, heading east, the speed limit increases to 55), eastwards to the JCT with CTY-23, then east to JCT CTY-24 has very poor Verizon service, and both voice and data calls almost always drop along that stretch of NY-343. The CTY-23 drop, heading southeast of NY-343, is likely part of Verizon's poor and problematic coverage in that general area. Most recent instance occurred on 12/20/2015.
Dutchess County, Pawling: Calls drop while driving on NY-55 approximately half a mile east of the JCT of NY-55 and NY-292 after reaching the apex of the hill immediately after the JCT heading westwards and away from/out of the Harlem Valley (where NY-22 and the NY Central RR Harlem Line runs) along NY-55. Most recent instance occurred on 12/06/2019.
Dutchess County, Pawling: No overage for over two miles on NY-55's eastern segment east of NY-22, which heads to CT and becomes CT-55. Coverage drops out _completely_ on NY-55 approximately 1 mile east of the JCT NY-22/NY-55, in the general area of the JCT of NY-55/CTY-22 (that's Dutches County-22, it's not a typo, CTY-22 is just east of NY-22 there!) and there is no coverage for over two miles until entering the CT/00119 (ex-011010) system where NY-55 becomes CT-55 at the New York/Connecticut border. Both of Verizon's 3G and 4G networks drop; there is no 5G coverage; drops occur usiong 4G/LTE phones provided by Verizon. Most recent drop occurred: 01/08/2023.
Dutchess County, Pawling: Verizon Wireless calls drop along NY-22 north of the NY-22/NY-55 interchange at the JCT of NY-22 and E. Main St. Drop generally occurs at night (are they doing testing then?) and affects drivers heading north or south along NY-22; for example, calls initiated at the Hannaford Supermakret along NY-22 will tend to drop about 1/2 mile north of the JCT of NY-22/E. Main St. Most recent drop occurred: 08/17/2017.
Dutchess County, Pine Plains: Verizon calls drop along NY-199 heading east from downtown Pine Plains towards Pulver's Corner/JCT Bean Hill Rd, just after NY-82 branches off of NY-199 and heads north to Ancram. Verizon calls drop just east of the NY-199(east)/NY-82(north) split, and there is poor/droppy coverage until Pulver's Corner/Bean Hill Rd. At Pulver's Corner, along NY-199, at the JCT with CTY-59, any calls which can be established from NY-82 eastward will drop -at- CTY-59, and there is pretty much no coverage from CTY-59 all the way to CTY-63 (at the apex of a hill which NY-199 traverses, with the Hudson Valley to the west and the Harlem Valley to the east). Essentially, there is no Verizon Wireless coverage heading east from Pulver's Corner all the way to CTY-63 and a good deal into the Harlem Valley, as coverage resumes approaching the Harlem Valley corridor/NY-22. Most recent drop occurred: 07/07/2019
Dutchess County, Red Hook: Verizon Wireless calls drop along NY-199 on the east side of the Kingston-Rhinecliff Bridge, between JCT CTY-103 and JCT-9G. Verizon's coverage is somewhat poor in the area, which is heavily traveled for northern Dutchess County, and CTY-103 and NY-9G serve as arterials to the bridge. Most recent drop occurred: 07/07/2019.
Dutchess County, Washington's Hollow/Millbrook: Drops occur while driving east or westbound on US-44/NY-82 at the JCT with NY-44A (which is the western junction of NY-44A and US-44). Most recent instance occurred on 10/04/2007.
Nassau County, Greenvale: NY-25A between NY-106 and NY-107: Calls consistently drop while traveling either eastbound or westbound on NY-25A between NY-106 and NY-107. Verizon was contacted and reported back that the responsible tower in that area was at the time being worked on and that Verizon is having to "share" a cell tower which adds to the problem (Huh?!). A few weeks later, on 11/04/2004, Verizon then claimed that they did not expect to have resolved until the end of January 2005 at the earliest. (Fixing a transmitter on a tower takes over two months?!). As of late 2006 (2 years later!) drops still occur and there is generally very poor coverage on Verizon (and to a lesser extent on other carriers) on NY-25A from Greenvale west to Cold Spring Harbor -- certainly not the sort of coverage one would expect along a high-traffic corridor or Long Island, and especially not in 2007. Last tested: 04/09/2009.
Nassau County, Hicksville: Calls drop while traveling south on NY-106/107 generally while crossing over the LIE / I-495 and Northern State Parkway interchange. Last occurred: 12/09/2006
Nassau County (Long Island), Jericho/Hicksville area: A downward-pointing (inverted) "triangle" of bad coverage: The "points" of the triangle are: the JCT of NY-25/NY-106/NY-107 to the south, the JCT of NY-25A and NY-107 to the northwest, and the JCT of NY-25A and NY-106 to the northeast. Generally poor cellular coverage there with frequent drops and distortions, and practically no EVDO coverage and very little 1XRTT coverage. Even as of Summer 2017, drops stilloccur along NY-25A, east of NY-107 and just west of NY-106 (to Oyster Bay or Hickville). Calls initiated at CW Post (along NY-25A) will often atenuate and drop approaching NY-106, perhaps 1/4 of a mile west of the NY-25A/NY-106 traffic light. Most recent instance occurred on 08/30/2017.
Nassau County, Laurel Hollow: Drops occur just east of NY-25A/Northern Blvd and approximately three miles west of Cold Spring Rd. Most recent instance occurred on 06/24/2010.
Nassau County, Manhasset: Verizon calls drop along the Northern State Parkway, at Exit 28/Willis Avenue. A relatively new drop as of 2018 (perhaps as a result of frequency re-alignment for LTE?), it occurs mainly in the westbound direction; as an ex ample, calls initiated on the NSP near NY-25B/NY-25 will often drop a few miles to the west between Exit 28/Willis and Exit 27/Searingtown & Shelter Rock roads. Most recent instance occurred on 10/20/2019.
Orange County, Greenville: Verizon Wireless calls drop at the Greenville Scenic Summit overlooks (EB and WB) on I-84, as I-84 crests over the Shawangunk Ridge (the highest point on I-84 in NY State). This drop has been going on since (analog) cellular service started in the area on I-84 in the early 1990's, and for whatever reason seems to regularly occur where the Orange County/Lower Hudson 00404 (now identified as 00078 using the Albany SID) system handed off to the Scranton system (now grouped with the ex-Contel Harrisburg 00096 system). Even lower-tier carriers such as T-Mobile and Sprint don't drop at the summit/crest of the hill, but for some reason Verizon can't seem to fix this drop. By mid-2016, heading east over the summit, calls at times hold over the apex, but then drop 7 miles east along I-84; more testing needs to be done to see if this can regularly be repeated, but the fact that it still drops 7 miles to the east still indicates there is something problematic with Verizon Wireless in the area. Heading west, calls still drop at the apex/rest area on Verizon as of January 2019. AT&T Wireless also suffers a drop both eastnound and westbound at the Greenville Summit, but, surprisingly, calls are maintained and do not drop with both Sprint and T-Mobile. Last westward drop observed: 01/02/2019.
Orange County, Cornwall/West Point: Drops occur on US-9W (freeway segement) approximately one mile south of the southern JCT with Continental Rd. Heading northwards, after coming down the hill along US-9W from Storm King Park, Verizon voice calls begin to attenuate near Deer Hill Rd, and by the time Continental Rd. in the Town of Cornwall is passed, calls drop completely. This may be a "vestigal" drop from a demarcation between the Poughkeepsie/Dutchess/00486 system and the Orange County-area/00404 system (the latter's SID does not seem to be used anymore but the line generally fell around that area when the 00404 SID was in use). Last instance occured on 07/17/2011.
Putnam County, Mahopac: On the Taconic State Parkway near the JCT NY-301, in both northbound and southbound directions, in the vicinity of the Taconic State Park Police barracks calls will drop. Traveling up the incline to the NY-301 overpass, some calls initiated in the Orange/Poughkeepsie 00404/00486 markets will drop as they transit into the NY Metro 00022 market in the vicinity of Mile Marker 34.6. Opened 10/11/1997, resolved in part by late 2001 as coverage improved, but both analog and more often digital drops still occur. 07/06/2003 -- tested again, and it still drops (i.e., calls will frequently NOT transit between 00486/00404 Mid-Hudson systems and the 00022 NY Metro system along the Taconic). 07/13/2006 -- tested again and analog and digital seem to transition, but drops occur further south at apex of Taconic at JCT NY-301. As of 05/27/2007, problems are still being experienced in the area; while some calls will transit properly, especially in the northbound direction, calls will drop with an equal degree of frequency more often than not in the southbound direction. Overall, an area which requires additional work to assure seamless transitions between the two Verizon service areas. UPDATE- As of 07/03/2007, calls in progress while driving both northbound and southbound do hand off, although voice quality deteriorates for about 20-30 seconds during the handoff. It is severe enough that neither party can hear the other. Update 04/22/2018 - seems to have become worse: for about two months now, calls initiated to the south (after the new Peekskill Hollow drop; see the Westchester County section of the Verizon Dropped Calls list, below) will drop going over the hill at NY-301, generally before or at the Taconic Park Police trap (they're often not there, but people still slow down, causing more accidents than if people were just allowed to drive without worry about speed traps at every turn in the road). While the issue was never fully remedied, since Feb 2018, the problem has become worse, and Verizon calls regularly and predictably drop going over the hill/interchange for NY-301 and heading down towards I-84. The majority of drops over the "NY-301 hill" occur in the northbound direction, which drops consistently; southbound calls hold through the area around 50% of the time. Last occurred: 12/06/2019.
Putnam County, Peekskill Hollow: Verizon Wireless drops calls along the Taconic State Parkway ("Secret" route NY-987) heading both northbound and southbound at the JCT with Pudding Street (southbound drops are much less frequent). This drop is a few miles south of the handoff between the Dutchess/Orange County 00486/00404 (now labled as the Albany/00078 system) system and the NYC/00022 system, but used to handoff well until perhaps mid-2018. Perhaps this is a result of Verizon's clumsy "transition" from CDMA to LTE? For whatever reason, this drop has become more frequent starting in mid-2018. Last observed: 07/26/2020.
Putnam County, Peekskill Hollow: Verizon call drops occur on the Taconic State Parkway ("Secret" route NY-987) nearly halfway between Bryant Pond Rd and the next exit northbound, Peekskill Hollow Rd. (Occurs in both the northbound and southbound directions at different locations; NB while descending into Peeksill Hollow, and SB after emerging from Peekskill Hollow prior to the Bryant Pond Road overpass). This is a relatively new drop for Verizon, which started around Feb 2018 and can vary as to location and the frequency of which it occurs, but generally over 50% of calls drop in both the northbound and southbound direction (much more northbound, closer to 95% of the time). We've noted as of Summer 2020 that northbound calls don't seem to drop as much, either due to more humidity in the air (more signal bounce) or Verizon actually doing some work to (re-)improve coverage. So uthbound calls still seem to drop coming out of the the Hollow. Last observed: 07/26/2020.
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 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: Bear Mountain State Park: There is poor coverage on the Palisades Interstate Parkway between Exit 16 and Exit 19, especially at the US-6/Palisades Parkway rotary. Coverage in Bear Mountain State park on US-6 and the Palisades is generally poor on all carriers, and Verizon does a slightly better job (as is generally the case in the Northeast with it's more challenging topography) than most, likely due to their still extensive use of their landline-"B" 800MhZ channels. However, there are still significant zones of poor/no coverage traveling east/west on US-6 and north/south on the Palisades Parkway, and more generally, on most of the other roads going through the Park. Additional, reliable coverage is needed not only for convenience but for safety's sake -- the park has a number of heavily travelled commuter routes and needs and demands better cellular coverage along said corridors. Coverage on Verizon is particularly poor (more so than on ATT Wireless which has slightly better coverage along US-6 from the rotary to NY-17) on the Palisades Interate Parkway between exists 18 and 17 (that is, heading west from the Bear Mountain Bridge where the Palisades turns south to head towards the rest area in the center median and down towards New Jersey) - all Verizon voice calls (and data connections) drop there, creating a relatively large area of no coverage where motorists can not call for help if needed. This has been this way for over 25 years and still nothing has been done to remedy the lack of coverage in tha area! This is even true post-3G shutdown / 4G migration - there is still no Verizon coverage in the area! Verizon customers who are on a contract plan (now generally to pay for new phones and equipment) may want to ask for their money back, since Verizon is or should be well aware of this drop and large dead area, hasn't corrected it, and allows the issue to continue. Most recent instance on the Palisades, as well as on US-6 just west of the Palisades rotary, was on 01/02/2023.
Rockland County, Sloatsburg: Verizon calls drop along NY-17, and suffer from generally poor to no coverage (both voice and data) along NY-17, mainly between Washington Avenue (just south of where the 55MPH zone ends heading south), Seven Lakes Drive, and Sterling Mine Road, which generally corresponds to all of the Sloatsburg area along NY-17. Coverage is also poor from Sterling Mine Road for two miles until the JCT of NY-17 and I-87/NYS Thruway. Additionally, coverage is poor to nonexistent along Sterling Mine Road westward from NY-17 as it crosses from NY to NJ into Ringwood, with generally poor coverage through Ringwood State Park until hitting NJ-208/Skyline Drive. Interestingly, coverage along the NYS Thruway/I-87 doesn't seem to suffer as much in the Sloastburg area, as apparenty Verizon Wireless has optimized coverage for the Thruway. Why they can't do this as well for (the toll-free) NY-17 is unknown, but the problem has existed for as long as there has been cellular service in the area, which, as of 2019, is about 35 years! It's incredible that on a heavily travelled route like NY-17, just north of I-287, Verizon has practically no coverage over such a large area and that after so many years nothing has been done about it. (In all fairness, AT&T Wireless, and of course Sprint and T-Mobile aren't much better, which seems like a good reason to have more cellular carriers and more competition than the current trend of fewer by way of consolidation.) Most recently observed: 04/21/2019.
Suffolk County, Huntingon: Verizon Wireless drops calls 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 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 with Verizon, and although North Country Road is a bit hilly and windy, it is quite close to NY-25A (indeed, it used to carry NY-25), so it's unclear why Verizon service is so poor in the Mt. Sinai/Miller Place areas. Most recent instance: 11/25/2016
Suffolk County, Mt. Sinai: Verizon Wireless drops calls along Mt. Sinai-Coram Road, at the JCT with North Country Road (likely an old alignment of NY-25A, as it is along other stretches of the North Shore as well). Calls drop in both directions (heading northwest to Mt. Sinai or southeast to NY-25A). Part of a series of drops and an area of generally poor coverage north of NY-25A along North Country Rd, from just east of downtown Port Jefferson, all the way along North Country (or other primarily E/W roads along the North Shore) to Miller Place (near the firehouse), where North Country then heads east/southeast to rejoin the current NY-25A. Note this isn't unique to Verizon; all the other carriers have poor coverage and multiple drops from Mt. Sinai to Miller Place as well. Most recent instance: 11/02/2017.
Suffolk County, Northport: Verizon Wireless drop calls 1/2 mile west of the JCT of NY-25A and Woodbine Ave approximately 50% of thr time; the remainder of instances will hold but the call quality becomes quite noticeably degraded. One of the first instances occurred on 08/29/2012 (but there were earlier ones which we had not documented, even with analog service); most recent instance occurred on 01/10/2017.
Suffolk County, Port Jefferson: Verizon Wireless drops occur along NY-25A/North Country Rd (also named Main St. in Port Jeff) at the JCT with Old Town Rd. Calls initiated, for example, to the west at Stony Brook, or the the east in downtown Port Jefferson will often drop along NY-25 near Old Town Rd. Most recent instance occurred on 11/02/2017.
Suffolk County, Port Jefferson: Verizon Wireless drops just east of downtown port Jefferson along Old Post Road East, at Crystal Brook Hollow Rd., and the continuation of Old Post Rd. further east towards Mt. Sinai. (Basically, Old Post Rd. E. is the continuation of NY-25A from downtown Port Jeff, if, heading east, one doesn't make the right to head south in downtown near the ferry terminal and instead continues straight, which seems like an old alignment of NY-25A. Heading eastwards on Old Port Rd. E., the road appears to stop at Crystal Brook Hollow Rd., which is where the Verizon drop occurs. At the intersection, making a left turn and then shortly after that a right will continue along Old Post Rd (no "East" anymore) to Mt. Sinai, where Verizon and all the carriers have a lot of coverage issues and drops, and eventually to North Country Rd. (which in parts still is and seems likely in other parts to have been) the alignment for NY-26A, or continuing south on Mt. Sinai-Coram Rd. to the current NY-25A. Most recent instance occurred on 11/02/2017.
Suffolk County, Smithtown: Drops occurs in the vicinity of NY-25/Jericho Turnpike and Calvert Road. Most recent instance occurred on 12/15/2014.
Westchester County, Elmsford: A relatively new drop (late-2017), perhaps due to some general Verizon re-alignment of frequencies(?) where of course they want to "encourage" people onto their ("droppier") LTE bands and off of 800MHz (purely for the customer's benefit, of course... It couldn't be it's just what Verizon wants and, as has become so commonplace these days, they just self-servingly massage and contort some response to say how they are really doing it JUST for the customer, and mos people go along with it because they are too busy downloading the newest application to chase Pokemons around the streetand can't be bothered with more complicated matters, right?), along the Taconic State Parkway, south of I-287, near the JCT with NY-100B. Calls begin to attenuate just south of the NY-100B/Dobbs Ferry Rd. overpass, and by the uphill stretch south of I-287 (where people exiting at the poorly-engineered left exit for I-287W bunch up 2 miles south of the exit and slow the whole parkway down!), calls generally drop. Most recent instance occurred on 04/07/2018.
Westchester County, Kithawan/NY-134: Another relatively new drop (late-2017), perhaps due to some general Verizon re-alignment of frequencies(?) where of course they want to encourage people onto the "droppier" LTE and off 800MHz (purely for the customer's benefit, of course...), along the Taconic State Parkway, just south of Exit 11/NY-134 and a few miles south of the New Croton Reservoir. T-Mobile used to be the only carrier to drop in the area, but it appears that Verizon wishes to join TMO's ranks!. Most recent instance occurred on 06/17/2019.
Westchester County, North Salem/(to CT/Fairfield County/Ridgefield): Verizon calls drop along BOTH NY-116 (CT-116) near the NY/CT line. NY/CT-116 is the "northern" access road to Ridgefield, CT, from Westchester, NY, used to access I-684 and NY-22 from Ridgefield. Calls initiated on one side of the line (for example, at the Golden's Bridge, NY Metro North Station, used heavily by commuters from Ridgefield, CT due to inadequate service on (closer) the Danbury Branch) will drop heading along NY-116 just east of the JCT with NY-121. There is weak to no coverage along NY/CT-116 for approximately a mile into Ridgefield, CT, where coverage resumes. While the lack of coverage along NY/CT-116 near the state line may be the immediate cause of the drop at times, the underlying issue may more likely be the perennial problems Verizon has with handoffs between different systems, a vestige of the various systems they integrated years ago (in this case the NY/00022/B and the CT/00119/A systems), and which appears to be the cause of a similar drop along NY/CT-35 which suffers no extended area of no coverage. (See below). The stretch of no coverage along NY/CT-116 also affects data service and results in a data drop along NY/CT-116. Initially observed: 1990 (YES, in 1990!), most recent instance: 09/09/2016. (A drop which has been going on for *26* years!!; as an aside, AT&T, Sprint, and TMO drop there as well, but we expect better from Verizon, and all the wealthy Ridgefield residents, and indeed, all the wealthy residents of the area on both sides of the state line, expect a lot better!)
Westchester County, North Salem/(to CT/Fairfield County/Ridgefield): Verizon Wireless calls drop along NY-35 at the NY/CT line, at the JCT of NY-35 with Peaceable Street (which heads NE to downtown Ridgefield), Old South Salem Rd, and NY-123. Unlike the above NY/CT-116 drop, the NY-35 Verizon drop does not appear to be due to a lack of coverage - there appears to be continuous coverage along NY/CT-35, even at the state line. Yet, for whatever reasons, voice calls will drop near the state line, even though there is reasonably good coverage in the area. This appears to be one of the usual "inter-system" drops Verizon still seems to have a problems with (like the NY/CT-55 drop, see the "Dutchess County" section of this list) which was never properly remedied (like the I-84 drop between the NY/00022/B and the CT/00119/A systems). (Data calls will hold along NY-35 between CT and NY, unlike the NY-116 drop, above, where data drops as well.) First observed: 1990 (yes, again, 1990 is correct, over 26 years ago!), most recent instance: 09/09/2016
Westchester County, Purchase: Verizon calls drop heading southbound along I-684 as it transitions to the Hutchinson River Parkway. Calls begin to deteriorate passing under I-287 (and the associated interchange ramps for the Hurtch/Merritt/I-684/I-287 interchange), and by the time the Hutchinson River Parkway is reached (where all lanes have merged into only two, about a mile north of the service area in the center of the Hutch near the large "pine tree" cell-tower), calls drop completely. Occurs more often at night than day, and is relatively recent - in mid-2017 this wasn't a problem. Most recent instance: 06/12/2018
Westchester County, Purchase: Handoffs (digital B/00022 BAMS NYC Metro to either digital A/00119 BAMS Wallingford or analog B/00088 SNET-Cingular CT markets) along the Merritt will not work. Calls initiated near the JCT of the Hutchinson River Parkway, I-287 and I-684, which is in the general area of Purchase, drop after the Greenwich Mobile station near the old Meritt Parkway toll plaza. Analog 00022/B to analog 00088/B seem to work. This was brought to BAMS (and then Verizon's) attention in Jan 1999 and they have never managed to get it to work. Opened 01/06/1999, unresolved as of yet. This drop was verified again on 03/26/2007. As of late 2014, this issue (on the digital side, obviously, since there is no more analog service, unfortunately!) has been remedied for the most part, however, in rush-hour traffic heading back to Greenwich, there are from time to time drops between the Greenwich service plaza and the area where the old Greenwich tolls were. There are also data drops on the NY side, which are discussed in the Verizon Wireless Data Drops and Problems list. Most recent (albeit rare) voice drop in the area occurred on 11/19/2014.
Westchester County, Rosedale: Calls drop on the Hutchinson River Parkway about one mile south of the JCT with Mamaroneck Ave. while traveling north on the Hutchinson River Parkway at Mile Marker 13.3, which is close to Exit 22. Most recent instance occurred on 09/30/2011. It was reported to Verizon on 03/31/2005. No resolution as of yet.
Westchester County, Scarsdale (Highland): Verizon Wireless calls drop along Cushman Road, and Verizon has generally poor coverage and "lossy" service along Cushman from Mamaroneck Rd and NY-22 (White Plains Rd.) all the way to NY-125 (Old Mamaroneck Rd). Scarsdale is one of the more affluent areas of Westchester County south of White Plains, and it's surprising to see such poor coverage in the area - Verizon's coverage in this section of Scarsdale is more typical of coverage patterns of the early 1990s than of 2016!. (As an aside, data service seems to hold - outdoors - but indoors Verizon data service is also problematic, but not as bad as voice, which experiences regular drops outdoors, let alone indoors, along Cushman and the general series of E/W roads between NY-22 and NY-125 in Scarsdale. Last observed: 07/21/2016.
Westchester County, Shrub Oak/Jefferson Valley: Verizon Wireless drops calls along the Taconic State Parkay, approximately 2 miles north of the JCT with US-6, but south of the JCT with Bryant Pond Rd. (Eg, shortly after the point at which the TSP drops a lane and reverts back to its original, narrower, 2-by-2, design as it heads north). There have always been coverage issues between US-6 and Bryant Pond Rd, and data calls sometimes drop there (mainly at night...why?), but as of early 2018, voice drops have occurred on a few occassions, or if a given voice call doesn't drop, the audio drops out for over 20 seconds at highway speeds. Last observed: 03/01/2018.
Westchester County, South Salem: Verizon drops calls along NY-123 just north of the JCT with Donant Valley Rd. There is generally good coverage on both sides of the drop, so this may be due to poor handoffs between Verizon's NY/B/00022 and CT/A/00119 system. Last observed: 06/01/2018.

Pennsylvania

Chester County, West Grove: Drops occur approximately 50% of the time while travelling on US-1 at Mile Marker 14.5, just south of the JCT of US-1 and PA-841. Most recent instance occurred on 11/30/2011.
I-83 at the Maryland-Pennsylvania State Line: Calls drop heading Northbound on I-83 during the transition from the Washington/Maryland-00018/B system to the Harrisburg/Ex-Alltel-00096/B system. Drops occur in both directions, e.g., northbound or southbound. Verizon has been contacted about this issue and Verizon agreed to do drive tests in the area to diagnose and fix the issue, which as of yet has not been resolved. Last tested: 09/10/2006.
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 and data. Most recent instance occurred on 06/12/2016.
Fulton County, Todd: Drops occur while driving south on PA-16 just south of US-30 while proceeding down a hill. Most recent instance occurred on 06/12/2016.
Fulton County, Warfordburg: Verizon calls drop just north of the Maryland/Penn line (Mason-Dixon Line) along I-70 at the JCT with PA-484/Warfordsburg Rd. This is likely due to a poorly implemented (or no) handoff between the Verizon/00096 system and the US Cellular/01794, and many of the drops in lower Fulton County along the Mason-Dixon (iterated on this list) line may be a result of these poor or non-existent handoffs in the general area. Calls are the northbound I-70 PA Rest Area/Welcome Center are especially problematic as the service area appears to straddle both systems. This is especially problematic for MVNOs such as Straight Talk (for their customers on Verizon) as depending on their location in the rest area parking lot, they may or may not be able to place calls (Straight Talk/Verizon customers can ONLY place calls on the Verizon network in that area, and if their phone tries to instead register on a stronger US Cellular/01794 singal, it will be rejected. This drop/handoff issue is somewhat odd as along other major corridors (such I-81 and I-70), calls between the Verizon/DC/00018, Verizon/Harrisburg/00096 and the US Cellular/01794 hand off well for Verizon customers; it seems that only along I-70 at the PA/MD line and northwards towards I-76/The PA Turnpike is this a problem. Most recent instance occurred on: 06/12/2016
Lancaster County, Lyndon (Lancaster): Verizon calls drop along US-222, just south of Lancaster/US-30, north of Lydon, along US-222, where the Verizon/DC-Baltimore/00018 system hands off to the Harrisburg/00096 system. Most recent instance occurred on: 02/10/2022.
Philadelphia (City & County): Verizon Wireless drops calls around 40% of the time along I-95 under the Ben Franklin Bridge/I-676. These drops occur late at night and do not seem to be a problem relating to network congestion. Most recent instance observed on: 03/12/2017.
Philadelphia (City & County): I-95; calls often drop while drving past the Philadelphia Eagles stadium (just south of JCT I-76 and north of the Philadelphia Navy Yards). The drops occur at all hours, even late at night, so it does not appear to be related to any congestion or heavy network use issue. Thus, a Verizon calls placed in Center City, which progresses along I-95 southwards, will often drop just south of I-76, while passing the sports complex to the right. Last occurred: 12/15/2018.
Pike County, Bushkill (Delaware Water Gap National Recreation Area): Verizon Wireless voice calls drop along US-209/Federal Road, from the junction with Broadhead Rd/Mile Marker 18 (from the north) all the way to where US-209 crosses Suzie Creek and US-209's name changes to Milford Road, where coverage resumes, for a distance of about 5 miles. Verizon (as well as T-Mobile, Sprint, and AT&T Wireless) had very poor to non-existent coverage along this stretch of US-209, however, as of 2018, Verizon has improved its coverage somewhat and has only two drops, this instant one in the Buskill Falls Road general area (MM18), and the Dingman's Ferry drop, at Mile Marker 14, below. Drop occurred: 10/20/2015, updated 01/20/2018.
Pike County, Dingman's Ferry (Delware Water Gap National Recreation Area): Verizon Wireless drops calls along US-209/Federal Road at the JCT with PA-739 at Mile Marker 14. Coverage is generally poor for a mile or so north and south of the JCT with PA-739. This drop and the Bushkill drop, above, are the only two observed areas of drops along US-209 in the Del Water Gap Rec. Area Park as of early 2018, which is somewhat of an improvement from 2015 - but Verizon still needs to do some work to fix both drops and ensure better overall signal stregnth and coverage along the route. Drop last occurred: 01/20/2018.
Pike County, Spring Hill: Verizon Wireless calls drop along I-84 near Mile Marker 15 in the Newfoundland/Sterling/Spring Hill area. Calls drop near the overpass with Neville/Springhill Rds, in both directions (E/W). Drop last occurred: 09/16/2016

Rhode Island

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.
Providence County, Scituate: At the RI/CT line, calls drop along US-6 and will not hand off from the RI/New England/B-00028 market to the CT/A-00119 market, either analog or digital. There is decent coverage near both sides of the line, but for some reason Verizon never bothered to either cover or allow handoffs there. All calls with Verizon drop heading West along US-6 nearly at the state line (or a 1000 feet into CT) and resume after going up the hill on US-6 or CT-52(?) (CT Turnpike/I-395 RI Extension). Nextel has better coverage in the immediate area but generally drops further west on US-6 in CT at the apex of the road prior to the descent to the I-395 JCT. Cingular GSM is even better, but voice quality is very muffled at the immediate CT/RI border. Reported 04/25/1999, unresolved as of yet.
Washington County, Westerly: Just north of the state line on I-95, coverage on the Verizon/BAMS B/00028 side is pretty poor, and the Cingular/SNET/B from CT (not the Cingular/SNET/A from RI) bleeds in and causes roaming charges to appear (on generally older plans) before Verizon phones can re-register with the RI/00028/B system. Last observed 10/01/2006.

Vermont

Bennington County, Pownal area: Coverage continues from the Verizon system in the Williamstown, Mass area (00119/A) on US-7 past the state line continuing six miles northward to Pownal, VT. However, by Mile Marker 6, coverage begins to degrade and drops shortly thereafter, probably as a result of an incomplete handoff to the US Cellular 01484/B system. (And Verizon/00300 service doesn't commence again heading east until Newfane, just west of Brattleboro, on VT-9). Most recent instance occurred on 07/13/2008.
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.
Windham County, Whitingham: There is barely any coverage on MA-8A between the JCT of MA-116 and up to VT-9. Coverage remains spotty until slightly north of Coltrane and just south of VT-9. Most recent instance occurred on 05/23/2010.

Virginia

Clarke County, Berryville: Drops occur while driving north on I-81 at or slightly after the Virginia/West Virginia line. All calls seem to drop while transitioning from the Verizon Wireless/00018 DC-area system to the US Cellular/1794 "Western Maryland" system. This incident affects both cellular and data connections; all will drop. Most recent instance occurred on 02/10/2013.
Culpeper County, Culpeper, Virginia: Drops occur while travelling on US-15 at the JCT of US-15 and VA-844/Fayettesville Rd, slightly south of the JCT US-15 and US-17 and approximately ten miles north of Culpepper. Most recent instance occurred on 01/03/2010.
Fairfax County, Fairfax: Drops occur while driving either eastbound or westbound on I-66 at Mile Marker 68 the JCT with US-29. Most recent instance occurred on 12/03/2007.
Fairfax County, McLean/Tysons Corner: Verizon Wireless calls drop along the inner loop (northbound) of the Washington DC Beltway/I-495 just north of the JCT with VA-193/Georgetown Pike, just south or at the JCT of the GW Parkway. Verizon calls drop around 50% of the time, in both directions (that is, on either the inner loop/northbound, or the outer loop/southbound). Most recent instance occurred on 06/03/2019.
Fairfax County, McLean: Perhaps associated with the above VA-193/Georgetown Pike drop; Verizon calls drop just outside of the Beltway near the intersection of Rector Lane and VA-738/Old Dominion Road (Old Dominion is numbered VA-738 nort/west of VA-12 3/Dolly Madison/(Chain Bridge Rd.), but it's an extension of VA-309 from south/east of VA-123). Calls initiated on The Georgetown Pike/VA-193 in the area of Great Falls will fade and drop along Old Dominion heading east, just before or upon passing Rector Lane. Most recent instance occurred on 08/25/2021.
Washington DC Metro: Although there is coverage on the Orange Line at Virginia Square/George Mason University, calls cannot be placed. Most recent instance occurred on 02/24/2011. On and off again problems continued until at last summer 2013; needs further testing to see if it should be placed in the "corrected" section yet.

Washington DC

Note: Voice coverage on Metro, although never great, was in many ways better when analog service was available, and "through coverage" from station to station generally worked well in many segments of the system. Additionally, ATT Wireless customers could drop to analog and utilize the Verizon Wireless DC Metro system. After analog was removed, no roaming (even on Sprint postpay it seems) occurs on the Verizon system, and calls tend to drop in all cases in the tunnels between systems. There does not seem to be a single case of coverage not dropping between any of the underground stations/segments in the DC Metro any longer, and reliable voice coverage is generally relegated to stations only, like most of the other carriers. Effectively, Verizon Wireless' voice coverage in the DC Metro system has taken a step _back_ under digital-only coverage, and despite repeated inquiries with them about large segments of the northwestern leg of the Red Line which used to have coverage between stations and now does not, nothing has been done. It is (or was) possible to cover the tunnels properly and have decent "through" coverage as evidenced by Verizon's analog service, so it is unclear why they are not willing to provide that level of service currently as of late 2014.

Washington DC Metro: Drops occur on the DC Metro Red Line between Twin Brook and White Flint. Most recent instance occurred on 10/20/2010.
Washington DC Metro: Drops occur on the DC Metro Red Line between White Flint and Grosvenor. Most recent instance occurred on 10/20/2010.
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. Moreover, drops seem to only occur between Medical Center and Grosvenor when travelling inbound; they do not occur between Grosvenor and Medical center when travelling outbound. Most recent instance occurred on 11/04/2010.
Washington DC Metro: Drops occur and no coverage exists on the DC Metro Red Line between Medical Center and Bethesda. Most recent instance occurred on 12/19/2011.
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 04/27/2010.
Washington DC Metro: Drops occur on the DC Metro Red Line between Friendship Heights and Tenleytown. Most recent instance occurred on 03/31/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 11/23/2010.
Washington DC Metro: Drops occur on the DC Metro Red Line just north of Van Ness. Most recent instance occurred on 05/30/2008.
Washington DC Metro: Calls drop on the Red Line between Tenleytown and Woodley Park. Most recent instance occurred on 09/28/2009.
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 drop on the Red Line between Woodley Park and DuPont Circle. Most recent instance occurred on 09/28/2009.
Washington DC Metro: No coverage exists between DuPont Circle and Farragut North on the Red Line. Drops occur just north of Farragut North station, and the lack of coverage extends beyond DuPont Circle station. Most recent instance occurred on 09/28/2009.
Washington DC Metro: Calls drop upon entering/exiting Dupont -- Calls which are initiated inside the Dupont Circle Station will drop upon exiting, and calls which are initiated outside the station will drop upon entering, eg, calls do NOT hand off between the "towers" (microcells) inside the station and those outside. Efffectively, calls initiated outside the Dupont Circle station will drop towards tjhe bottom of either the north or south escalator banks, and conversely, calls initiated inside the Dupont station will drop upon exiting from either the northern or southern escaltors entrances. AT&TWS, T-Mobile, and Sprint are all able to transition calls from the outside to the inside (or inside to outside) without issue; yet Verizon, which covers Metro better than any other carrier (which isn't saying much!) can't manage this (at Dupont as well as many other stations, such as Courthouse in VA). Most recent instance occrurred: 05/05/2016.
Washington DC Metro: Drops occur while traveling west on the Orange Line (running concurrently with the Blue) between Metro Center and Farragut West. Most recent instance occurred on 12/22/2009.
Washington DC Metro: Drops occur on the Orange/Blue line between Farragut West and McPherson. Most recent instance occurred on 04/27/2010.
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: There is no coverage on the Red Line between Farragut North and just north of Metro Center. Most recent instance occurred on 09/28/2009.
Washington DC Metro: Calls initiated at the lower level of Metro Center where the Orange and Blue lines are will drop after riding up the escalator to the Red line/Shady Grove-bound side. Most recent instance occurred on 10/03/2011.
Washington DC Metro: Drops occur on the Red Line between Metro Center and Gallery Place. Most recent instance occurred on 05/29/2008.
Washington DC Metro: No coverage exists at Gallery Place station on 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: Drops occur on the Red Line between Gallery Place and Judiciary Square. Most recent instance occurred on 05/29/2008.
Washington DC Metro: Drops occur on the Red Line between Judiciary Square and Union Station. Most recent instance occurred on 06/29/2008.
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.
Washington DC Metro: Drops occur on the Orange Line (running concurrently with the Blue) between McPherson and Metro Center.
Washington DC Metro: Orange/Blue Line Metro Center lower level: Areas of the lower level of Metro Center have always been problematic for Verizon, but as of mid-2016, coverage has been particularly challening there, with strong signal indicated, but it is nearly impossible to place/receive voice calls or initiate data sessions, even during off-peak hours when there are few people in the station. Initially observed 06/12/2016, most recent instance occurred on 01/03/2017.
Washington DC Metro: Red Line Metro Center upper level: Areas on the upper level (which has generally been more problem-free with Verizon) seem to have been experiencing the same problems as the lower level, that is, as of mid-2016, coverage has been particularly challening on both levels, for all lines (Red, Blue, Orange/Silver), with strong signal indicated, but it is nearly impossible to place/receive voice calls or initiate data sessions, even during off-peak hours when there are few people in the station. Initially observed 06/12/2016, most recent instance occurred on 01/03/2017.
Washington DC Metro: Drops occur while riding on the Orange Line between Rosslyn station and Courthouse station. Most recent instance occurred on 02/23/2009.
Washington DC Metro: Drops occur while riding on the Orange Line (running concurrently with the Blue). While traveling either eastbound 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. However, drops do not occur when travelling westbound. Most recent instance occurred on 10/08/2009.
Washington DC Metro: Coverage is heavily distorted on the upper level of L�Enfant Plaza station on the Yellow/Green line on the southbound platform. Drops did not occur but coverage was distorted. 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: Calls drop south of L'Enfant Plaza on the Yellow Line as it breaks away from the Green Line towards the dedicated Yellow Line bridge crossing the Potomac River. Calls tend to drop shortly after the switch track area where the Yellow Line heads southwest in the tunnel prior to emerging to the open air segment leading to the bridge. However, drops do not occur while travelling northbound. Most recent instance occurred on 06/16/2008. This seemed to have been corrected as of 02/26/2009. However, it occurred once again on 04/28/2009.
Washington DC Metro: Calls drop between L�enfant Plaza and Pentagon on the Yellow line. Most recent instance occurred on 11/29/2010.
Washington DC Metro: Phone displays four or five bars worth of coverage on the Yellow Line (running concurrently with the Blue) within the Crystal City station but the characteristics of Verizon's service within the station make it difficult to place or receive calls for some unknown reason. Calls can be placed or received with a greater degree of success towards the northern end of the station as compared to the southern end, however, generally, some aspect of Verizon's coverage within the station results in increased difficulties and delays when placing and receiving calls. Most recent instance occurred on 05/20/2008.
Washington DC Metro: While traveling on the Yellow Line (running concurrently with the Blue) between Crystal City and National Airport, calls drop immediately south of the Crystal City station while still in the tunnel prior to the open cut leading to the elevated airport trackway. Calls will drop in both directions in approximately the same place. Most recent instance occurred on 05/20/2008.
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: Drops occur while riding south on the Orange and Blue Lines between Capitol South and Eastern Marcus/Market. Most recent instance occurred on 03/14/2012.
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 08/03/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.
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 on 07/22/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 12/19/2011.
Washington DC Metro: While walking out of the Pentagon City Station and into the Pentagon City Mall, drops occur at the doors between the two. Most recent instance occurred on 07/13/2008.

West Virginia

Morgan County, Berkeley Springs: There is very poor coverage on WV-9 between Berkeley Springs and Paw Paw. Coverage should be better as this location is just south of I-68. Most recent instance occurred on 01/23/2011.

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, Brookfield: Verizon voice call drops and fade-outs occur maybe 75% of the time at the JCT of US-7/US-202 where the US-7 freeway (prematurely) ends at a traffic light, generally in the northbound direction. Calls placed south of this intersection (for example initiated while on I-84) will begin to degrade approximately 1/2 of a mile prior to the traffic light/intersection (where the flashing "Stop Ahead" warning sign illuminates when the signal ahead is red) and tend to drop right at or shortly after the intersection heading north. Most recent instance occurred on 01/31/2015; appears to have been more or less corrected as of December, 2020.
Fairfield County, New Canaan/Norwalk: Drops occur between Mile Markers 24 and 25 on the Merritt Parkway, approximately one mile north of the town line for Westport. Most recent instance occurred on 05/19/2009; appears corrected as of 06/05/2017.
Hartford County, Hartford, JCT I-91 / I-84: Not a drop per se, but analog calls get VERY distorted in the downtown Hartford area. This started around 6/20/2003 and has not been corrected. Probably a trunking problem; if the user holds on to the call and the caller has not hung up since he/she can't hear the user, the call can continue once the hand off has occurred, but right at the I-84/I-91 ramps and in an approx. 1 mile radius from there many analog calls become so poor that the service is unusable. Noted 06/21/2003 and many times after that without improvement; didn't want to deal with Verizon customer support saying "Well, it's analog and we don't support that" or some dolt trying to sell a digital plan, so hopefully they'll eventually catch it. Some things are too much of a pain to deal with them about...:(. Resolved: 07/10/2005
I-84 WB at the CT/NY line: Neither analog nor digital calls will hand off heading eastbound on I-84 and crossing the CT line from North Salem, NY to Danbury, CT. (WESTBOUND does work as of 03/21/2003, only EASTBOUND now drops). Reported to BAMS/Verizon on 03/16/1999, resolved in BOTH directions on or before 01/02/2007. There is still very weak coverage on the CT/A/00019 system directly proximate to the CT/NY border (near the CT "Welcome"/Rest Area, but digital calls will hand off both Eastbound and Westbound now in most cases. Resolved: 01/02/2007.
New Haven County, Derby: Absolutely shameless lack of coverage along a (shamelessly unbuilt) freeway. CT-34 serves as the main road between New Haven and Danbury, with much greater volume than it was ever built to accommodate. Although the CT-34 freeway still remains unbuilt, there is a good deal of traffic on it, and yet Verizon and a number of other carriers have absolutely no coverage on it at all between a few miles north of CT-8 (after the Yale Boathouse) and a few miles north of the dam near Newtown and the JCT with I-84. (Interestingly, it is reported that Nextel has coverage there as of 1/25/2003; tests will be needed here.) No service at all; absolutely dead, so handoffs aren't even an issue ;(. Reported 11/19/1996, and BAMS/Verizon has done nothing at all to improve (or provide any sort of) service in that area at all since, hence, unresolved as of yet. Resolved by mid-2008; most carriers have no problem anymore along CT-34 between I-84 and the CT-34 freeway stub in New Haven, including Verizon. As to the CT-34 freeway, well, much like the US-7 freeway between the Merritt (CT-15) and I-84, or the motorist-killing US-6 freeway (ex-I84) segments from Bolton (Manchester) to the Willamantic bypass and from the bypass to I-395 and then onwards to Providence (and RI, which was in part the impetus for killing the project in the 1980's now wants something built), or the CT-11 freeway (which if it were finished in the 1970s would have cost $20 million and now some nuts have the idiot idea to toll it to pay the $700 million it will cost to finish), or the US-44 freeway to provide more direct access to the NW sections of the state, of the CT-10 freeway, or...,or.... etc; so noting Connecticut's apparent inability to get highway projects done, it's no wonder they are now spending millions of dollars to remove sections of the already built CT-34 freeway stub instead of using that money to continue it along the right of way which already exists. (Even if it meands bulldozing whatever clinic was built in the right of way in the early 2000's, serving as New Haven's own version of the Manhattan 42nd St 8th AVE IND "lower level" to block the 7IRT expansion westward, and connecting it past the Yale Bowl to the existing CT-34 parkway.) Connecticut's moto is something like "Qui Transtulit Sustinet" - "He who Transplants (a vine) (will be) Sustains(ed)", but with the degree of unecessary traffic in CT, it's unlikely that any transplanted vine would survive a trip across the state and wilt and die sitting in slow and (with proper planning) avoidable traffic! :)
New Haven County, Waterbury: Bad analog drops while traveling west up the hill away from CT-8. This does not seem to affect digital, and it may be a result of a few mistuned analog phones, but both of them have a sudden burst of loud static and then drop heading west on I-84 just past the JCT of CT-8. Last occurred: 07/01/2003. Resolved: 10/10/2006.
New Haven County, Waterbury: Calls drop on I-84 approximately a quarter of a mile west of Exit 17 in the vicinity of CT-64/Chase Parkway. Most recent instance occurred on 09/07/2008.
I-95 SB at the CT/NY line: Both digital and analog calls will not hand off and drop between the Rye Playland connector to I-95 and the Larchmont RR station parking lot underpass (near the NYS Thruway toll plaza). AT&T Wireless explained in 1996 that in terms of analog handoffs (e.g., CT-BAMS/A to NY-ATTWS/A) BAMS/Verizon did not want to pay for the extra trunks necessary to connect to AT&T's switch which covers towers serving south of Larchmont to BAMS's switches (roughly), so calls WILL hand off to NY but only as far as Larchmont, after which since areas south of that are served by a separate AT&T (now Cingular) switch, since BAMS doesn't want to pay to send trunks there as well, calls will drop. (this seems silly; BAMS/Verizon should hand a call off to Cingular/NY, and then from there Cingular should route the call via its own internal network and not expect BAMS to send trunks to all the crazy network of switches which AT&T set up in NY before their merger with Cingular.) As to digital, e.g., BAMS/ CT-A/00119 digital to BAMS/NY-B/00022 digital, calls just drop near JCT I-287 SB (or slightly south of that), but almost always at or before the Rye Playland connector. BAMS/Verizon was informed of this on 06/12/1998, they have never resolved it. (2012 note: The above pertains to ANALOG service which is no longer available. Under analog, Verizon Wireless callers who placed a call in the CT/00119 market and travelled south to NY State handed off to the MetroOne/CellularOne/Cingular/ATTWS NY-00025 system, and were serviced by ATT Wireless' NYC Metro 00025 analog system. When analog unfortunately went away, so did this problem, as CT digital callers are not handed off the AT&T Wireless' NY/00025 system (they can't be since Verizon is CDMA and ATT is GSM), but instead handed off to Verizon's NY/00022 system as they travel into NY State.)

Delaware

I-95/I-495 SB split: At the PA/DE state line, where I-495 (Wilmington Bypass) splits off of I-95, digital calls (CDMA) will get somewhat distorted at times and drop approx 40% of the time. Coverage is VERY good in the area so drops are hard to understand. Last observed, 04/10/2006, appears to have been fixed as of 04/18/2007.

Maryland

Cecil County, Conowingo Dam: Voice calls on Verizon drop and data signals are very tenuous about 1.5 miles south of the Conowingo Dam while approaching the JCT of US-1 and MD-22. The coverage in this area is very poor and stays that way until about 3-4 miles north of MD-276 (which becomes DE-276 in Delaware). It is just not a good level of coverage, and even though the data is somewhat better, it too gets very, very weak. Drop occurred on 03/26/2005 and was reported to Verizon on 04/06/2005. There has been no disposition as of yet, last observed 05/19/2012. As of late 2014, a majority of these calls no longer drop, but on occassion some do, so this entry is being maintained here until the problem is fully remedied. Nov 2015 update: Data sessions drop 50% of the time at on near Conowingo, voice calls generally transit properly over the dam. Coverage still needs to be improved in the area, but at least as far as voice calls go, there is usually "through coverage" on US from Bel Air/MD-24/MD-924 to the PA/MD line. This drop appears to have been corrected as of Jan 15, 2023 (and tested on a Verizon-provided phone). There is a slight bit of a data drop (ping packets stop briefly on the south side of the dam, but it does not seem to too dramatically affect VoLTE calls.
Cecil County, Rising Sun: US-1 at Westwood Rd., approx 4 miles north of the Conowingo Dam and approx 3 miles north of JCT US-1/US-222. While traveling north on US-1 after the Conowingo Dam at Havre de Grace/Port Deposit, US-1 heads into a small "valley", and all calls (analog and digital; even 3-watt analog) drop in the vicinity of Westwood Rd. Note that Nextel and SWBell (Cingular) seem to (poorly) be able to maintain a connection there, while BAMS/Verizon always drops. This is also quite close to I-95 (only a few miles "inland"), so the fact that such poor coverage exists there on Verizon is surprising. Reported 02/20/1998, last observed 01/16/2006, corrected by late 2012, and calls (voice and data) no longer seem to drop there.
Cecil County, Perryville: While driving south on I-95 and just south of the Havre de Grace bridge, calls drop upon reaching Mile Marker 89. The drops occur at the point where the Philadelphia, Delaware and Cecil County Maryland system (00008 system) hands off to the DC/Baltimore system (00018 system). It has always been a problem and continues to be a problem. Calls do not hand off in that area and are dropped, even though there is plenty of coverage there. Most recent instance occurred on 04/18/2007. UPDATE- After repeated testing, this drop appears to have been corrected as of 12/03/2008.

Massachusetts

Calls now successfully transition from Massachusetts into Vermont. Most recently tested and found to have been corrected on 05/23/2010.

New Jersey

Mercer County, Princeton: calls initiated in the NY/00022 system drop upon entering the Philadelphia/South Jersey/00008 system, generally upon entering Princeton proper on US-206 south. Calls will then drop again 1.5 miles south of the JCT with NJ-27 and US-206 (i.e., the center of town) while traveling southward on US-206. Additionally, system "bleeds" from Philly/00008 towers (same market, but towers south of Trenton on the PA side of the Delaware River in PA) may result in roaming charges for older rate plans despite being clearly in NJ. Last tested: 01/14/2006, appears to have been fixed as of 04/18/2007.

New York

Dutchess County, East Fishkill: Taconic State Parkway; Verizon calls drop south of the JCT of the Taconic State Parkway and NY-55 at Mile Marker 43/7, just south of the Park and Ride and what used to be a rest area. Last tested: 02/01/2005, and corrected by early 2010.
Dutchess County, East Fishkill: Calls consistently drop on the Taconic State Parkway ("secret" NY-987) about 1/10th of a mile south of JCT of NY-82. The problem occurs while descending from the top of the hill just before the first exit "ramp" for NY-82. Cell One/Dobson TDMA has a similar problem there, while their GSM is slightly better but becomes nearly inaudible. The call will not drop, but will sound garbled. Although this drop appeared to have been fixed as of 07/21/2008, it occurred again on 03/06/2011. Repeated tests in 2013 and 2014 indicate that the drop is mainly fixed, but that once in a while drops still occur there, although it is less than 5% of time time. In any case, Verizon's voice coverage of the "southern" Taconic State Parkway JCT with NY-82 (there is also a more northern JCT) has the fewest drops of all the major carriers there -- AT&T Wireless drops regularly, and TMO and Sprint barely have coverage there to begin with and drop nearly if not all the time at that location. Appears to have been correct by mid-2012, and still no drops there in 2018.
Dutchess County, LaGrange: Drops occur on the Taconic State Parkway approximately a quarter of a mile south of the JCT of NY-82. This drop was duplicated on several different handsets and thus it cannot possibly be an equipment malfunction of some type. Most recent instance occurred on 05/01/2011, corrected by early 2015, and Verizon Wireless calls no longer appear to drop here.
Dutchess County: I-84 between the NY (00022) and Mid-Hudson (00486/00404) markets: EB and WB along I-84, approx 3 miles east of JCT Taconic State Parkway (TSP) near EB rest stop or WB NY State Police barracks, at apex of hill on I-84, all calls (analog and digital) drop between the NY/B-00022 and Orange/Poughkeepsie/B-00404/00486 markets. Opened 10/11/1997, resolved, "only" 9 years later, by 8/2006. (Calls can even be initiated now in Beacon, and drive all the way to Mass along I-84 without a drop; the semi-bad area in Waterbury at JCT I-84/CT-8 has been fixed. Thus, both eastbound and westbound transitions on Verizon Wireless between the 00022 and 000486/00404 markets on I-84 in New York now seem to work. Resolved 01/02/2007.
Nassau County (Long Island): Poor voice quality and occasional drops for digital and static for analog calls while heading westbound on NY-25A at the Rosslyn viaduct (bypass over the town). Calls initiated in Greenvale will deteriorate at the LIRR bridge and continue to have problems and/or drop completely as while driving west downhill over the viaduct. Reported 10/17/1997, retested 06/25/2003, appears to have been fixed as of 02/06/2007.
Nassau County, Carle Place: On the Long Island Railroad (LIRR) main line between Mineola and Carle Place, drops occur on a relatively consistent basis in both directions. Most recent instance occurred on 01/12/2009, appears to have been fixed as of 05/19/2022.
Nassau County, Long Island/Cold Spring Harbor: There is no coverage at the JCT of NY-25A and NY-108. Most recent instance occurred on 07/31/2012, appears to have been fixed as of 05/19/2022.
Queens County - Cunningham Park: Drops occur while driving on I-295 on the southbound transition ramp to the Grand Central Parkway. The drop occurs when going either east or west onto the GSP. Most recent instance occurred on 12/13/2010. Appears to have been corrected as of 04/29/2012.
Queens County - Queens: Drops occur on the Grand Central Parkway slightly east of the JCT of the GCP and the Cross Island Parkway. Most recent instance occurred on 09/10/2008. Appears to have been fixed around the same time as the above drop, eg, April 2012.
Rockland County: Calls drop where I-287 multiplexes with I-87 near Exit 16E about 1/4 mile south of the Garden State Parkway NY State extension. Last occurred on 09/21/2004, reported to Verizon on 09/23/2004, corrected on or about October 2015.
Westchester County: I-84 North Salem EB: Handoffs (digital B/00022 BAMS NYC Metro to either digital A/00119 BAMS Wallingford or analog B/00088 SNET-Cingular CT markets) along I-84 will not work. Calls drop after CT Welcome Center west of Danbury. Analog 00022/B to analog 00088/B seem to work. This was brought to BAMS (and then Verizon's) attention in Dec 1998 and they have never managed to get it to work. Opened 12/14/1998, resolved by Summer of 2006.
Westchester County, Brewster: I-84 at the JCT of I-684, Brewster: Calls drop right at the state line when proceeding eastbound transitioning from the NY/B-00022 system to the CT/A-00119 system. Interestingly, the handoffs between systems work fine when traveling westbound and transitioning from the CT/A-00119 system to the NY/B-00022 system. Coverage is relatively good on either side of the state line, so the drops must be occurring due to a handoff issue between towers. When contacted, Verizon agreed that such a situation was ridiculous and that if it works in one direction, it should work in the other. Last observed on 05/25/2004, reported to Verizon on 05/26/2004, no resolution yet.
Westchester County, Greenburgh: Drops occur on the Sprain Brook Parkway at Mile Marker 6.5. Most recent instance occurred on 07/04/2011, resolved by late 2015.
Westchester County, Yorktown: Calls drop while driving either north or south on the Taconic State Parkway, approximately two miles north of the JCT with the Bear Mountain Parkway. Coverage drops just south of US-6 and approximately two miles north of the JCT of US-202/NY-35 southbound. Most recent instance occurred on 09/01/2011. As of late 2013, this problem appears to have been corrected, and calls on the TSP ("secret" NY-987) no longer drop at or near the JCT with US-6 and/or the "special" ramp to the shamelessly-still-unfinished connector to the Bear Mtn Parkway (which just dumps traffic onto NY-35/US-202 instead of connected to the actual Parkway about a mile to the West -- typical NY State (lack of) planning and follow-through).
Westchester Couty, I-95 Port Chester NB: Handoffs (digital B/00022 BAMS NYC Metro to either digital A/00119 BAMS Wallingford or analog B/00088 SNET-Cingular CT markets) along I-95 will not work. Calls drop near the Greenwich truck scales. Analog 00022/B to analog 00088/B seem to work. This was brought to BAMS (and then Verizon's) attention in Dec 1998 and they have never managed to get it to work. Opened 12/14/1998, resolved by mid-2005.

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: 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 fixed as of 07/27/2010, although voice quality is generally poor and inaudible between the two stations.
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. This seems to have been corrected as of 02/26/2009, but audio quality is poor and attenuates between the two stations.
Washington DC Metro: Drops occur on the Yellow Line between Pentagon City and L�Enfant Plaza station. After leaving the Pentagon traveling north into the District, the train goes over the Potomac and then proceeds into a tunnel, at which point calls drop. Most recent instance occurred on 12/22/2008. This seems to have been corrected as of 02/26/2009.
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. This seems to have been corrected as of 07/13/2008, and there is relatively good coverage at the Clarendon station currently.
Washington DC Metro: No coverage exists at the DuPont Circle station on the Red Line. Even though 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.
Washington DC Metro: Very poor to no coverage at the Farragut North station on the Red Line. Although it had been the case that drops occured between Farragut North and DuPont Circle stations, the lack of coverage at this station is a new phenomenon which started in 2012 with the station's reconstruction. Upon contacting Verizon Wireless and speaking to a mid-level rep named "Tyler" on 02/11/2013, we were told that Verizon technicians will investigate this issue and attempt to determine the cause of it. On 10/04/2014, after the construction had been completed, there is still no coverage there (there is a little bit which "bleeds in" at the north end of the station as well as at the station attendant area on the Mezzanine, but no systemic coverage as the other stations have), and it appears that despite our calling them and making them aware of the issue, they've done nothing in over a year to fix it after it was specifically reported to them! As an update, as on January 2015, there is STILL no Verizon coverage at the Faragut North Red line station (nor AT&T Wireless, nor Sprint; need to test TMO, ie, ask someone with a TMO phone on the platform to if it's not just us!). Most Recent instance occurred on 12/30/2014. Finally - Verizon seems to have actually fixed this as of June 2015, and there is very good coverage at Farragut North. (But it still drops both ways in the tunnel towards Metro Center and Dupont). Corrected as of 6/15/2015.

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 (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/12/2024