Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
LOL at "less than two percent of the wireless customer base."

So, 2% = every user in every major market? Ridiculous.

I didn't have the upload speed issue. I live here in Houston, so I think that's a fairly large market. I guess only bits and parts were affected since I saw that there were some issues in West Houston.
 
LOL at "less than two percent of the wireless customer base."

So, 2% = every user in every major market? Ridiculous.

no... Every iPhone4 user in every market.

From ATT: 87,000,000 subscribers
From Apple. 1.7Million iPhone 4s
From 2nd grade math: 1.7M/87M = 1.95% which is nicely less than 2%

funny how it works out like that.
 
And more to the point, for the problem to come about, one must be using an HSUPA device and transfer data through a part of the network that makes use of the relevant hardware. So while all HSUPA devices may demonstrate the end result of this bug, it will not impact everyone.

Kind of interesting to see the reaction to this, actually. I spent a few years working for CISCO. People have no idea how common stuff like this really is.


Where did you find such a fine tinfoil hat?

The iPhone 3G and 3G ARE affected. I have a 3G with iOS4 and I have been having UL and DL issues for several days now. Perhaps ATT is having a secondary network issue they aren't talking about... all I can say is that I'm lucky to get UL speeds of 100kbps, and I typically don't get DL speeds greater than ~150 - 250kbps. Last week I was managing around 2-2.5 Mbps down, so something certainly changed.
 
no... Every iPhone4 user in every market.

From ATT: 87,000,000 subscribers
From Apple. 1.7Million iPhone 4s
From 2nd grade math: 1.7M/87M = 1.95% which is nicely less than 2%

funny how it works out like that.

I thought it was 1.7 Million iPhones sold worldwide - so all of them would not be on the AT&T network. But when you add in other HSUPA smartphones and laptop cards the 2% figure seems reasonable.
 
They certainly did finally cknowledge the problem but didn't give us time frame.
Let me ask all of you: do you honestly believe that AT&T would make this kind of statement if we didn't start the tread expressing our problem, so that respectable blogs like Engadget, Gizmodo, Tuaw can pick up the story and ASK for the official statement from AT&T ?
Probably not. To sum it all, I'm very proud of macrumors community for staying on top of this issue, and ultimately helping everyone in getting this problem fixed. Hopefully.

I pinged an insider at ATT... he said

The Lucent Alcatel issue is [in most major cities].... to stop a meltdown, some features had to be turned off until a software patch is developed to address the bug, and this basically limits throughput on higher performing 3G devices.

We were told a fix will be within a month.
 
Its only a problem in certain markets so 2% sounds very reasonable. AT&T is not out to get you.

I never said AT&T was, "out to get us." I am merely making a point that the number of users affected doesn't matter; they are using PR spin to try and downplay the problem. My point is simply that the number of users is inconsequential, if 50 people, or 50,000 people are affected, and are still paying full price for their service, then, IMHO, the problem should and must be fixed without delay and without any qualifiers or excuses.
 
At least it is a software fix. This is complicated stuff (I used to work in mobile tower planning).
 
They certainly did finally cknowledge the problem but didn't give us time frame.
Let me ask all of you: do you honestly believe that AT&T would make this kind of statement if we didn't start the tread expressing our problem, so that respectable blogs like Engadget, Gizmodo, Tuaw can pick up the story and ASK for the official statement from AT&T ?
Probably not. To sum it all, I'm very proud of macrumors community for staying on top of this issue, and ultimately helping everyone in getting this problem fixed. Hopefully.

Are you also proud of proclaiming that "the capping or throttling is absolutely deliberate," despite the protestations of MR members (me among them) who suggested that the problem might be technical?

And for the record, I think AT&T would have fixed the problem just as quickly whether you snarked about it on MR or not. AT&T's engineers are as dedicated to doing their jobs properly as anyone else. They routinely address all kinds of problems, including ones that you don't even notice, and I doubt they read MR for guidance.
 
I never said AT&T was, "out to get us." I am merely making a point that the number of users affected doesn't matter; they are using PR spin to try and downplay the problem. My point is simply that the number of users is inconsequential, if 50 people, or 50,000 people are affected, and are still paying full price for their service, then, IMHO, the problem should and must be fixed without delay and without any qualifiers or excuses.

1. People aren't paying for a certain speed, they're paying for access. They still pay the same price regardless of speed, and I bet the contract states that speeds are not guaranteed.

2. Of course it's being fixed without delay. You don't think AT&T and Alcatel are just sitting around twiddling their thumbs, do you? The fix will take time to develop, then it needs to be tested thoroughly so this doesn't happen again, and then it will take time to deploy it to the, I'm guessing thousands, of cell sites affected by this.
 
I never said AT&T was, "out to get us." I am merely making a point that the number of users affected doesn't matter; they are using PR spin to try and downplay the problem. My point is simply that the number of users is inconsequential, if 50 people, or 50,000 people are affected, and are still paying full price for their service, then, IMHO, the problem should and must be fixed without delay and without any qualifiers or excuses.

Wake up from dreamland. The world of telecommunications and software is much more complicated. You cannot fix every problem in real time on the day it is found.
 
It even hit san antonio....I was getting 512k down and 125k up around 5 pm yesterday....then an hour later I was getting 4.1meg down and 1.3megs up.

Today I am getting 3 megs down and 1.3 megs up.

Gotta love it. This is way more stable than sprints 4g on the Evo...at least in San Antonio.
 
Everyone - iPhone 3G and Palm Pre are also capped!

I have been testing this since last week and both phones are capped. I have an iPhone 3G on 3.0 and I am getting like 50kbs. My wifes Pre is at 100kbs even. My coworker has a 3GS and he is around 50 like me.

AT&T IS FULL OF IT!

This is not just effecting iPhone 4 users. It's all 3G enabled phones.

Why do people not read?

JESUS H DIAZ read the freaking story you are responding to...

If it is a software issue with their wireless towers/network then it will effect everyone. Nobody from AT&T said it just impacted iPhone 4 users.

Seriously, why do only 5% of the people on MacRumors ever read the articles or stories they comment on?
 
I never said AT&T was, "out to get us." I am merely making a point that the number of users affected doesn't matter; they are using PR spin to try and downplay the problem. My point is simply that the number of users is inconsequential, if 50 people, or 50,000 people are affected, and are still paying full price for their service, then, IMHO, the problem should and must be fixed without delay and without any qualifiers or excuses.

If they had failed to specify how many users were affected you would claim that was PR spin too, wouldn't you? And how does specifying that number suggest that they are not fixing the problem without delay?

Besides, I'm sure Wall Street wants to know how many users are affected even if you don't.
 
No one is going to take the blame. They are going to put the blame on someone else!

Such babies AT&T and Apple

It's not about blame. It's about offering consumers an explanation, not an excuse.

Complex systems commonly have problems that are oftentimes non-intuitive. Just be happy they identified the problem and are fixing it.
 
Everyone - iPhone 3G and Palm Pre are also capped!

I have been testing this since last week and both phones are capped. I have an iPhone 3G on 3.0 and I am getting like 50kbs. My wifes Pre is at 100kbs even. My coworker has a 3GS and he is around 50 like me.

AT&T IS FULL OF IT!

This is not just effecting iPhone 4 users. It's all 3G enabled phones.

Which is exactly what the statement from AT&T says, if you bothered to read it.
 
I say UNLOCK it!!

Just sell the damn thing officially unlocked like recently in the UK and before in many other countries!!

Customers will be happy to choose their carrier and a lot of people will not have any more reasons to complain (although I'm sure they will find something else to complain about but that's not the point).

Then AT&T would have to step up or move to the side, competition is always the best incentive to take things up a notch.

I have been using my officially unlocked OZ purchased iphone (3G and 3Gs, tried purchasing the iPhone 4 in Glasgow but they had ran out) in Dubai(and worldwide since fortunately I get to travel to 4 continents sometimes in the same month) without a single problem, when in Eurpoe I use my prepaid Vodafone and in Australia I use 3 without a problem, In Dubai we have the shi**est operators on the planet (maybe, lol), if not just google: Dubai Etisalat and see for yourself.
 
Are you also proud of proclaiming that "the capping or throttling is absolutely deliberate," despite the protestations of MR members (me among them) who suggested that the problem might be technical?

And for the record, I think AT&T would have fixed the problem just as quickly whether you snarked about it on MR or not. AT&T's engineers are as dedicated to doing their jobs properly as anyone else. They routinely address all kinds of problems, including ones that you don't even notice, and I doubt they read MR for guidance.

Yes because it was a human move. As you can read in a few posts above yours, they had to shut of major cities affected to prevent a meltdown and turn off hsupa. It wasn't a machines decision to start a war against humans or whatever, it was AT&T engineers that turned it off. Ands if it wasn't for our community, we wouldn't even know what's up.
 
Yes because it was a human move. As you can read in a few posts above yours, they had to shut of major cities affected to prevent a meltdown and turn off hsupa. It wasn't a machines decision to start a war against humans or whatever, it was AT&T engineers that turned it off. Ands if it wasn't for our community, we wouldn't even know what's up.

Why does it matter? Did we all just step into a terminator movie? The guys insider said we, could just as easily mean they allowed the machines to throttle it, but who cares? I think I agree with you and probably responded to the wrong person. :)

Everyone - iPhone 3G and Palm Pre are also capped!

I have been testing this since last week and both phones are capped. I have an iPhone 3G on 3.0 and I am getting like 50kbs. My wifes Pre is at 100kbs even. My coworker has a 3GS and he is around 50 like me.

AT&T IS FULL OF IT!

This is not just effecting iPhone 4 users. It's all 3G enabled phones.

I agree with all the people suggesting you should RTFA, but I would be curious to know what upload speed you used to get on your iPhone 3G?
 
Why do people not read?

JESUS H DIAZ read the freaking story you are responding to...

If it is a software issue with their wireless towers/network then it will effect everyone. Nobody from AT&T said it just impacted iPhone 4 users.

Seriously, why do only 5% of the people on MacRumors ever read the articles or stories they comment on?

That's an easy one. They've been reflexively spewing vitriol for so long they've forgotten how to read for comprehension.
 
Ands if it wasn't for our community, we wouldn't even know what's up.

That's your opinion, unsupported by any evidence.

Has it occurred to you that it may have taken the engineers several days to troubleshoot the problem so that they could make a statement about it? Multiple people reported that AT&T CSRs acknowledged that there was a problem, although there was evident confusion on their part about what the problem actually was. Looks to me like it took a few days for AT&T's engineers to get together with Alcatel-Lucent's engineers and diagnose the problem. That seems completely normal to me.
 
Just tested for kicks. My upstream speeds are abysmal.
It seems the problem is relevant to my area.

The iPhone 3G and 3G ARE affected. I have a 3G with iOS4 and I have been having UL and DL issues for several days now. Perhaps ATT is having a secondary network issue they aren't talking about... all I can say is that I'm lucky to get UL speeds of 100kbps, and I typically don't get DL speeds greater than ~150 - 250kbps. Last week I was managing around 2-2.5 Mbps down, so something certainly changed.
If that's the case, and this is an issue people are experiencing across the country, then there's certainly something more to it. In any case, such a problem would probably be associated with either the repair process or fallout related to this problem (network errors; portions or capabilities of the network disabled; etc.). Would be nice to see data from more people.

no... Every iPhone4 user in every market.

From ATT: 87,000,000 subscribers
From Apple. 1.7Million iPhone 4s
From 2nd grade math: 1.7M/87M = 1.95% which is nicely less than 2%

funny how it works out like that.
Not all iPhone 4 users are impacted. It depends on area.
The gap would be filled by other HSUPA devices (there aren't many).

Which is exactly what the statement from AT&T says, if you bothered to read it.
Where does it say all 3G devices are involved in the article? Its wording is specific to 3G HSUPA-enabled devices, which excludes the iPhone 3GS and nearly every other phone out there. Only, what, the iPhone 4 and one or two Android phones are HSUPA-enabled?
 
That's an easy one. They've been reflexively spewing vitriol for so long they've forgotten how to read for comprehension.

That is true. Here is the process many users have developed as a reaction to new posts on Macrumors:

1. Click "Negative" on Story
2. Read first paragraph to identify target of aggression (AT&T or Apple in most cases)
3. Post a negative message about the appropriate target. It does not matter if this post is topical or in any way relevant.
4. Watch for replies quoting your post so you can call people fan boys.


A few of them use a little more style, but they still follow the exact same formula.

Here is an example story and this type of users response process:

Story:

Apple and AT&T have teamed up and found a cure for cancer in kittens.

Process:

1. Click Negative
2. Story is only one sentence, read the whole thing!
3. Post Reply:

Apple and AT&T suck, Verizon has been curing cancer for years with their Android phones. Steve jobs just wants to control kitten cancer so he can screw you over.

4. Wait. A reply: "Wow you seem a little off, mate"
5. Respond!:
**** Fan Boy loser. I bet you wear a black turtleneck.

---

We see this precise process played out over and over.
 
Lies

This is nothing but more lies from AT&T. Everybody's phone was getting HSUPA speeds in these areas, then all of the sudden the speeds are terrible. AT&T was trying to throttle people plain and simple and they got called out for it big time. They dropped the blame on another company.

How were people getting HSUPA speeds for a week before this supposed problem creeps up?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.