Consumerist Says AT&T Site Won't Sell iPhone In NYC, Citing Network
cowp writes "A Consumerist tipster couldn't get AT&T's website to sell him an iPhone when he shopped using an NYC ZIP code, but could when he tried other cities' ZIPs. Consumerist asked an AT&T CSR and seems to have gotten confirmation that this is carrier policy: 'Yes, this is correct the phone is not offered to you because New York is not ready for the iPhone. You don't have enough towers to handle the phone.' Considering Apple's gadget is currently the most popular handset in the US, its exclusive carrier's inability/unwillingness to support the device in the country's largest market is pretty huge news. If this proves true, I'd expect curtains for AT&T's exclusivity deal when it comes up for renewal." If you're in NYC, can you confirm or deny this outlandish-sounding claim?
Updated 20091227 1:03 GMT by timothy: Headline, now corrected, inaccurately named Apple rather than AT&T. Mea culpa.
There's been a lot of coverage indicating problems with iPhones in New York, including one Gizmodo piece saying a 30% dropped call rate is apparently normal.
512 MB RAM, 20 GB disk, 200 GB transfer, five datacenters. $19.95/month.
I live in NYC under a 114xx zip code and had no problems buying one in person at an ATT store. I bought it the weekend after Thanksgiving so it was about a month ago. Maybe they changed it since then.
Everybody outside of the tech world knows what an iPhone is.
Not everybody outside of the tech world knows what the E55, Hero, or GW620 are.
True, but promisingly I've been seeing a lot of my non-tech friends carrying around new Android devices lately.
"The difference between genius and stupidity is that genius has it's limits" - Albert Einstein
Interestingly, here in rural Alaska we get at least 20% dropped iPhone calls. After a particularly annoying one (I was within 200 yards of the tower, line of sight, over water) I complained to the local AT&T rep and the FCC.
About 2 weeks later, I got this nice call from an AT&T droid who says he was asked by the FCC to look into this. After a few pleasantries, he suggested 1) Making sure the battery was charged (OK), 2) Turning off 3G (already done, don't have 3G here in the boonies) and getting closer to the tower. I explained that if I got any closer to the tower on the last dropped call, I'd have to marry it.
His final suggestion was to take it up with Apple, maybe I needed a new handset.
I suppose it's something of a start but AT&T isn't going to solve very much of the problem this way.
Faster! Faster! Faster would be better!
Go back to the FCC and resubmit your complaint. Obviously AT&T simply read you the script to meet the barest of "compliance" requirements...by sending you to some script reader in a call center. They won't do jack shit until the FCC requires them to. Or, you're able to find someone within the local ranks at ATT that are willing to listen to you, not just some corporate weenie.
Actually you may have been too close. I am far from a wireless engineer but I do know that depending on the antennas used the base of a tower can be a dead zone. I've seen this in the wireless ISP world a few times and its frustrating.
It's like a ghost town compared to a few Asian cities. Light traffic, hardly any people, clear air, you could almost eat off the concrete. :-)
I live in Manila, we have 10,500 people per square kilometer across the metro on average, though some of the slum areas are as high as 40k - and yes, they all have cell phones - we send 140 billion text messages a year, the entire country is bathed in 3.5G, surprisingly you can actually get the juicy speed goodness anywhere at any time too, so the telco drones must be doing something right.