I took my iphone on my business trip from PA to RI Here is what I have discovered:
Speed tests using http://i.dslr.net/tinyspeedtest.html
PA:
Traveling N on I81 to Rt 84 E
Wilkes Barre Area: 627,401,615,709,622, 722, 874 (yesterday in this area I had full 4 bars 3G and no connection for data, today all is ok)
NY State
Rt 84 E
Edge 109
3G 758, 841, 1004
Conn
Rt 84 E
Danbury 3G 183, 344
Furthur East 1082,1060,764,915,1243
Waterbury 3G 1099, 767,925 (exit 25) 1418
stopped on rt 691 in Conn 4 3G readings in a row: 1310, 1363, 1332, 1238
RI
Lincoln RI
3G 68 thats right 68 terrible, switched off to Edge now 176
3G in RI is apparently down just like last night in Wilkes Barre PA. Large cities have overload problems. ATT better address this issue and stop blaming the iphone. Seems their 3G network is overloaded certain times of the day causing the 3G connection to crawl or not connect at all. I am now convinced its the network not the iphone.
Any input or additions welcomed.
I will also provide an update tomorrow night on my return route.
Charlie C
Speed tests using http://i.dslr.net/tinyspeedtest.html
PA:
Traveling N on I81 to Rt 84 E
Wilkes Barre Area: 627,401,615,709,622, 722, 874 (yesterday in this area I had full 4 bars 3G and no connection for data, today all is ok)
NY State
Rt 84 E
Edge 109
3G 758, 841, 1004
Conn
Rt 84 E
Danbury 3G 183, 344
Furthur East 1082,1060,764,915,1243
Waterbury 3G 1099, 767,925 (exit 25) 1418
stopped on rt 691 in Conn 4 3G readings in a row: 1310, 1363, 1332, 1238
RI
Lincoln RI
3G 68 thats right 68 terrible, switched off to Edge now 176
3G in RI is apparently down just like last night in Wilkes Barre PA. Large cities have overload problems. ATT better address this issue and stop blaming the iphone. Seems their 3G network is overloaded certain times of the day causing the 3G connection to crawl or not connect at all. I am now convinced its the network not the iphone.
Any input or additions welcomed.
I will also provide an update tomorrow night on my return route.
Charlie C