1 Answer
- Newest
- Most votes
- Most comments
0
I have to imagine this has happened sporadically, right? I've not seen such an issue, but I generally don't build Connect out of the East region. I suspect a support ticket is your only real way forward.
david
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
I think I may have resolved the issues actually. It was a combination of service provider failures and no notifications or alerts by them. Earlier this year we were using US west coast servers and those were not handling AWS Connect calls at all. The east coast servers have been the most reliable when using new and experimental AWS products and services.