VOIP Tech Chat → Google Voice Down?

Both my google voice and wife's google voice DIDs don't seem to be working today. Calling the DID gives an all circuits are busy message. Anyone else have the same issue?

Mine is working.

Looks like others with the same issue here:
»productforums.google.com ··· MP0kZB3c

Strange... I just tried calling my number and it is working fine for me. But I think there was a problem earlier in the day, based on how some people were calling me (although nobody mentioned anything).

I too get a busy signal when calling my Google Voice number.

Google does seem to be having some problems and it's not just incoming DIDs but my OBis and Talkatone can't seem to connect to Google's servers at all.

We use Bandwidth.com for most of our origination and termination and have had customers complaining most of the day. Outbound calls sometimes wont connect or have choppy audio. Inbound calla take forever to start ringing if they do at all.

As of now all our customers DIDs seem to ring to the all circuits busy message. I have had to temporarily shift outbound traffic to another carrier because of the issues.

IiRC, Google uses Bandwidth so that may be why.

I was having a little bit of trouble receiving incoming calls earlier today (it went straight to a busy signal), but outgoing calls worked fine.

I can confirm Bandwidth is having issues, even for DIDs on the complete opposite corner of the country.

It seems to me to be a case of promising geographic redundancy but not actually implementing it properly.

My GV and VOIPo DIDs are still not working since yesterday. Both I believe are with Bandwidth.com. It goes to fast busy right away. Nobody can call me except overseas.

As of yesterday around 9:00pm CDT, my GV number is back in service.

Yes, my GV number now works as expected! Glad we are back in business.

Calling my brother's mnemonic NYC GV number, in 347 NPA, from TMo in Northern California, results in an "all circuits are busy now, please try your call later. 83T", or "we're sorry, our circuits are busy now; will you please try your call again later. 1 32 8 9", or some other similar message (i heard at least 3 different messages, calling from the same phone). His mobile phone with a North Carolina 252 NPA works fine, though. But I personally can't blame Google here, 347 NPA is obviously affected, and locals have bigger fish to fry.

My GV in Bay Area 650 seems to work, but, due to all my calls being routed through CallCentric, my setup is currently messed up. :/ CallCentric has really let me down with their amateur setup; even my IPKall was routed through CallCentric, I thought I could trust them, yet CallCentric has acted completely inadequate and came unprepared, letting me down, and not even telling me that I'll be affected, so that I could take adequate measures (I learned through service actually being down, and even their hostnames don't resolve). CallCentric sucks big time.

Lets keep the CC bashing to the CC uber-thread please.

I understand your frustration.