question

This reply was created from a merged topic originally titled Inbound Calls from AT&T. Same issue as two days ago from another thread ( https://community.ringcentral.com/ringcentral/topics/inbound-call-issues-for-at-t-phones)

. Incoming calls from AT&T wireless phones (unsure if other carriers are affected as well) are saying that the call cannot be completed as dialed.
This issue is persistent and is making me research a new solution to my business phone needs.
THIS NEEDS TO BE FIXED PERMANENTLY!!!! We are literally losing thousands of dollars of business when customers are unable to reach our business.
Ringcentral never offers to compensate or even credit our account for these constant issues.
At least once or twice a month this issue happens, they claim it is a routing table issue with the carrier, and after 24 hours it gets resolved. Now it has happened twice in two days. Unacceptable.

I had issues again with conference bridge again 1+(267) 930-4000 this morning at 9 AM EST.  We all were getting intercept message.  We decided to start using Vonage bridge for future calls.

Please let me know the location of the destination number? 

Update: the underlining carrier has reported an issue in the area and they are currently working to resolve this. RingCentral does not have a current ETA on resolution.

Any updates?  This outage is going through its third hour now, blocking calls to me from the largest cell provider in the area.  Support just 'escalates'.

I am concerned that this issue is taking so long to resolve from Verison and ATT customer to reach my sales team. I have lost $$$$$$$ because my customers think I did not pay my bill. I cannot even forward my RC call. RC has to get their SH_T together. I am shopping for a new provider.

I'm am having the same issue and can understand the frustration.  This is the 3rd repair ticket in 2 weeks, and a total of 5 days combined without service.  No inbound calls from persons using a cell phone, which is probably 80% of my callers.  

I just got an email from RingCentral which says:  "The underlying carrier has reported to us there is a fiber cut in the area."  If the problem was a cut cable, why would I still have internet?  Why would I still be able to place calls?  

Given this outage is affecting multiple carriers' customers who are trying to call Ring Central numbers, I'm guessing Ring Central has a POP (point of presence; effectively 'equipment' to handle their customers call routing in the area) in Tampa Bay area for inbound calling, and that equipment is what's unreachable; otherwise, it would not be affecting multiple carriers.

That being the case, and if a fiber cut truly is to blame, then what this situation has revealed is that Ring Central has no physical redundancy in the fiber that connects their Tampa Bay-area network POP, since, normally a fiber cut would cause no outage unless an entity were single homed, i.e. physically connected via only one link.

This is pretty poor network design for a metro area with 3mil people in it.  The fact that they refuse to name the carrier whose fiber is supposedly to blame is also questionable; prevents any validation of what's being stated.  There's not a huge number of fiber transport providers in Tampa Bay, and all the big ones can typically have fiber cuts remedied within hours, yet we're nearing hour five now...

It just came back online for me.  Now receiving calls from mobile users. 

My calls from a ringcentral phone to another rc phone that has forwarding enabled rings once then the call is automatically ended and i get sent to voicemail for one user, Likewise calling from my t-mobile to a ringcentral central phone that forwards also has no luck. Both est, both in new york.