I'm getting about 1MBPS upload in central Florida. Actually faster than my WiFi.
Strange, I also live in central Florida (Palm Bay) and am getting capped upload speeds around the OP's average.
I'm getting about 1MBPS upload in central Florida. Actually faster than my WiFi.
Weird, when I use the speedtest.net and FCC apps, I get 96k upload readings. When I use Xtreme Labs Speedtest app, I get 244k. I'm not sure why they're different... I wonder if anyone else is having the same experience.I'm glad we can put the "upload cap" theory to rest. However, some parts of AT&T's response do not make sense and are just plain inaccurate:
"...we are providing normal 3G uplink speeds and consistent performance for affected customers with HSUPA-capable devices."
100 kbps is NOT "normal 3G uplink speeds", though I'll give them the "consistent" part. It definitely has been consistently near 100 kbps for the last 5 days! But "normal" non-HSUPA upload speed is certainly faster than 100 - more like 200-300 with a theoretical limit of 384 kbps.
Weird, when I use the speedtest.net and FCC apps, I get 96k upload readings. When I use Xtreme Labs Speedtest app, I get 244k. I'm not sure why they're different... I wonder if anyone else is having the same experience.
Is there anybody here that is still running iOS 3.1.3 or older on either the 3G or the 3GS? If so, please report your upload speeds here in this thread and I'll pass that info along to the engineering teams.
The more information that I can give the people in the AT&T Wireless Engineering department the faster we can come to a resolution.
Me too.Weird, when I use the speedtest.net and FCC apps, I get 96k upload readings. When I use Xtreme Labs Speedtest app, I get 244k. I'm not sure why they're different... I wonder if anyone else is having the same experience.
Trying to get information, that's all.so is this something caused by iOS 4?
Denver is still 60kbit/sec uploads verified by speedtest.net and dslreports speedtest.![]()
Seattle still has upstream bandwidth crippled. AT&T can go f/uck a goat. They need to resolve this asap. Or I'm gonna be expecting a f/ucking credit for the three days of edge speeds I'm paying overpaying for.
July 7 2010 @11.53pm
Seattle still has upstream bandwidth crippled. AT&T can go f/uck a goat. They need to resolve this asap. Or I'm gonna be expecting a f/ucking credit for the three days of edge speeds I'm paying overpaying for.
July 7 2010 @11.53pm
Seattle still has upstream bandwidth crippled. AT&T can go f/uck a goat. They need to resolve this asap. Or I'm gonna be expecting a f/ucking credit for the three days of edge speeds I'm paying overpaying for.
Here to comfirm that we in NYC do NOT have 3G upload speeds that AT&T claims that is providing to the customerswhile the fix is in the works.
WE STILL GET ODD CAP AT NUMBER 100kbps WHICH IS DEFINITELY NOT EVEN HALF OF WHAT 3G UPLOAD SHOULD LOOK LIKE.
sorry for shouting. It's still very clear that the upload instead of being limited by 3G standard at 384kbps is still limited by human cause at 100kbps.
I used to get more than 300kbps on my old iPhone 3G, two years ago.
On a sidenote, I wouldn't trust extreme labs test, it's always been giving me jacked up results even when testing my own WiFi i would get more than what my connection's limit is.
Use speedtest.net or FCC Mobile Broadband Test.
What's your upload speeds?Me, I can see the uploads. Also, more evidence AT&T is doing what they say is that we have reports of people in affected cities reporting back their usual upload speeds.
AT&T said they are providing the uploads speeds for customers, however because of server problems, you won't see it. In other words, no capping so capping theorist can calm down.
Me, I can see the uploads. Also, more evidence AT&T is doing what they say is that we have reports of people in affected cities reporting back their usual upload speeds.