T-Mobile customers with an 805 area code can't recieve phone calls from people outside of T-mobile right now. The issue started yesterday and contintues today with no estimated resolution time.

They offered me 75 bonus minutes to "help" me. Would be nice if people could call me and use those minutes.

If that's really true wouldn't that mean that the voicemail access for the entire system be down as well since +18056377243 is a T-Mobile area code/prefix.

i called the voicemail number I think two days ago and it didnt work...got a verizon error message. Didnt try on my t-mobile phone.

i got an error message from my house phone too a couple of days ago...

I've been using my phone no problem. I'm 805. I have received about ten calls today and yesterday, from non Tmo phones from all over the country. You may be having a problem, but not everyone is.

Some sort of translation error between SBC aka AT&T and Verzion landline. Prefixes in 215 and 296 are affected. Waiting on that bloated pig of a company....AT&T to get the problem resolved. Could be days......

Tmobile customers could still call Tmobile 805 customers. I would assume that the VM wouldn't be a cellular number either so it would most likely not be controlled by the same system as the affected ones.

Also, the system came back online late friday or early saturday, though I did not receive the text message informing me of this that tech support had promised to send when everything was well again.

Overall it's kind of left me upset at them as an organization. It would take me 20 minutes of holding and talking with customer and then tech support before they would hand me off to engineering who would inform me immediately that there was a system wide problem. Then to have confrontational support didn't help.

I've always liked the service and had great customer support until this incident. I think I'm going to wait and see how the new services pan out before signing up for another year or two. Maybe it's time to switch.

805-637 is a T-Mobile office prefix.

As far as your "incident" be careful what you wish for. You may have had one bad incident, but are you willing to go to the competition (such as cingular) who has no reputation for good customer service and be willing to be under a commitment for one or two years just because of one incident?

I've had a couple of less-than-positive experiences with TMo's customer service group. Recently the whole data network in my area was out for well over a week and all the reps I talked to about it kept telling me there was nothing wrong with the network and the problem had to be with my phone. I even started calling to put friends on the phone who had the same problem being able to access any data service on their phones. All of a sudden the problem went away after about 10 days of no service. TMo claimed they had no knowledge of the problem or how it was fixed.

During this process I felt TMo was really dropping the ball. I started looking around and I have to say that the options were poor and really bad. The logical options were Verizon or Cingular. Wanting GSM service so I can buy any phone I wish and also go overseas and get service, Verizon got crossed off the list pretty fast. Looking at Cingular I was pretty underwhelmed. I got a prepaid Cingular phone to test the service. Despite using essentially the same towers, Cingular seemed to have poorer service. And Cingular's rate programs are really not very attractive.

TMo has lost some of their traditional excellence in customer service for which they really distinguished themselves in the past. With that said, they are the best or the worst. I've had other carriers and doubt you'd find yourself happier anywhere else.

I would understand if a certain prefix had this type of issue, but an entire area code?
That would mean that everywhere from SLO, Santa Maria, Santa Barbara, Ventura/Oxnard/Camarillo areas would be inaccessible from the outside world, that's a good three counties that would have the same problem. Assuming no changes these three counties still share the same area code. Perhaps, a switch for a given prefix is all mushed up.

I started problems with the 805-MESSAGE number yesterday. And it seems to be isolated to certain numbers only. If I used my 310 cell # to dail 805-MESSAGE, and enter my 202 cell, I'd get the message that the VM box is invalid, but if I entered my friends numbers of area code 401 and 646, it works and asks for the pin number.

However, if I called 805-MESSAGE from a 202 number, I'm able to access my 202 VM.

Everything was working fine up until last night. Called tech support and they kept insisting that it's a problem with my phone. Needless to say, nothing's been resolved. I hate companies (cable companies included) that always blame customers equipment when something goes wrong instead of checking their end first.

EDIT: I did a search, and there was another thread about the 805-MESSAGE, and there were a few other numbers to call to access the VM system: 201-349-0010, 808-255-9999 and 602-570-9999. Calling any of the numbers from my 310 #, I'm able to access my 202 VM, something I've been having problems with the 805-MESSAGE. It's all very strange.

I have a prepaid T-Mo To Go SIM card right now, and I noticed the same thing. Today, I switched my number to my local area (801), and I get incoming calls now.

Again, I'm in Ventura County and haven't had any problems for the last month. I really think more people would be complaining if there was a company wide problem.