Update - The issue with the processing delays has been resolved due to an implemented workaround. Currently terminating a recording using 'endOnSilence' is not available.
Apr 26, 15:58 UTC
Update - We are continuing to investigate this issue.
Apr 26, 13:56 UTC
Investigating - We are currently experiencing delays in connecting calls to conversations for Voice API calls. There is a delay of approximately 1 minute between the first call being answered and the actions in the NCCO being consumed. End users receiving calls are hearing only silence between answering the call and any actions being processed. This can result in end users waiting before hearing a Stream or Talk action, or connecting into an active conversation.
SIP and the deprecated voice APIs are not impacted by this issue.
We are working on resolving this and will post updates here.
Apr 26, 08:55 UTC
This issue has now been resolved
Apr 25, 13:06 UTC
Our routes are now functional towards Iran - MCI (43211), we will be monitoring the delivery to this network closely.
Apr 25, 08:00 UTC
Please be advised that due to local issues with our suppliers in Iran, we have temporarily lost reach to MCI (43211)
We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 25, 07:46 UTC
Due to issues in one of our Data Centers, all calls placed to our Voice API from the EMEA or North America regions may have failed with error code 502 during the time of this incident.
The duration of the incident was : Thursday 20th of April at 16:30 UTC to Thursday 20th of April at 17:04 UTC
This incident is fully resolved.
Apr 20, 16:52 UTC