[flash24]

Rep said, everything should be back up and running on 12/12

[John Clark]

UMA down for me, as well. They told me it would be fixed last night. I guess that didn't hold true.

[monkeypaw]

Originally Posted by flash24

Mine is still down, southern Cali here

Other than about a 5 minute blip at 1:20PM, I've been up all day in Los Angeles. My connection has seemed to be a bit more stable than for many other folks.

[xyrcncp]

Originally Posted by sgtcasey

I'm still looking good on UMA since last night. The times I checked my 8320 it's had UMA on it the whole time I've been here at home.

Mine has been up since yesterday too. Side note, one thing I noticed though is that with very low use today my battery went from 80% at 2pm to 30% now (6pm). The phone has just been sitting on my desk. I guess I'll let it die as I've been trying to get my AOL IM to work and someone had posted in a thread before that they let their phone die and AOL IM started working again. I've been trying to get AOL IM to connect, but no dice and couldn't get no help.

[ericthebikeman]

Mine's been out all day. It was out for a good part of yesterday and came up briefly last night.
Minnesota

[John Clark]

Just recycled my connections and UMA came back again.

[xyrcncp]

UMA down again :(

[John Clark]

I had just changed the Beacon Interval from 50 to 75 and the router must have rebooted. When it came back just a few minutes ago UMA wouldn't connect but rebooted the device and got it back.

I probably need to just go do something else and get away from the PC AND the BB.

[absoluteevel]

Is it just me or did this string of outages start about the time that the router settings changes were posted? I wonder if all of us have better luck keeping connected now, so the system is overloading easier. heh

[xyrcncp]

Originally Posted by John Clark

I had just changed the Beacon Interval from 50 to 75 and the router must have rebooted. When it came back just a few minutes ago UMA wouldn't connect but rebooted the device and got it back.

I probably need to just go do something else and get away from the PC AND the BB.

lol...I would too, unfortunately I'm both studying and doing some work, so both the PC and BB are in front of me.

[bajjisw]

UMA is down again in Denver, CO, 6 PM MST.

To prior questions on IM: I had to call TMO and ask for the free blackberry feature / Blackberry add on and then IM worked (google).

Battery: I have noticed that the battery runs down much faster now, after I upgraded to 4.2.2.180. Could it be the combination of this, along with no blackberry data plan, in a place where there are blackberry enterprise servers (work) causes things to blow up ? Ah. there is also wi-fi at work, but it is EAP-TTLS/PAP which is not supported by BB.

[Helmdawg]

UMA seems to down in Philly as well

[absoluteevel]

While I have had it the past hour in Phoenix.

[markbb99]

When I called to get an update they gave me 200 minutes as an apology for lack of service. I don't use the minutes I have as a regular part of my plan - but I guess it's the thought that counts!

[John Clark]

I left for an hour or two and came back and UMA popped right up when I got home. I'm sure TMo is working overtime on this one.

[dinkelaker]

Thanks for keeping the thread going. Its kept me from losing my mind. The latest from Baltimore--worked yesterday evening, but it's cooked tonight.

[jaymd123]

So I did a little troubleshooting to see what's going on during this outage. It appears that I can't resolve the DNS of the UNC (nslookup punc.t-mobileuncs.com). I'm wondering if they are trying to somehow minimize traffic by removing the DNS entry. This would also explain why some people have service and not others when everyone should be connecting to the same server. I'm guessing the people who are still up have the DNS entry cached or their DNS server has a longer TTL for the record. Can anyone else confirm or deny this?

[jaymd123]

Originally Posted by jaymd123

So I did a little troubleshooting to see what's going on during this outage. It appears that I can't resolve the DNS of the UNC (nslookup punc.t-mobileuncs.com). I'm wondering if they are trying to somehow minimize traffic by removing the DNS entry. This would also explain why some people have service and not others when everyone should be connecting to the same server. I'm guessing the people who are still up have the DNS entry cached or their DNS server has a longer TTL for the record. Can anyone else confirm or deny this?

Nevermind, it looks like the IPSEC tunnel probably needs to be established before you can lookup the UNC. It was worth a shot

[mikekim76]

UMA is really getting on my nerve now!!!! Tmobile rep confirmed that they were adding more UMA servers last night, and will be perfectly fine starting today!! NOT... I can't believe they rolled out such incomplete service that is far away from market ready. I asked tmobile rep last night regarding this, and he said they tested this service since last year.... maybe they needed another year before rolling out to the market!!

[umaboy]

This whole thing is getting on my nerves also. More so I think because this whole thing could have been avoided. True enough, no one has control of the weather which lead to this whole mess. However, the technology is in place to deal with it (in regards to business continuity planning, disaster recover, and site failover). The T-Mobile IT department really dropped the ball in this area. Hopefully, the CIO of the company is making their rounds to find out why they could not execute the company's business continuity plan when it really needed to. This is why it is so important for a company to practice/drill such a plan because you never know when you'll need it one day. I'm sure they had one in place since we all have been able to get service every now and then. However, they must find out what part of the plan failed and fix it or their long term business performance will suffer because of it.