1 Answer
- Newest
- Most votes
- Most comments
0
This was an issue with the carrier! You need to contact AWS support to open a case with the carrier to help you investigate the issue. In my case, the carrier updated the route to solve it.
answered a year ago
Relevant content
- asked a day ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hi Bahaa. So is it necessary to have the Developer/Business support plan for AWS to investigate this?