Telerivet experienced a notice incident on October 21, 2016, lasting 3d 16h. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Oct 21, 2016, 05:26 PM UTC
Due to a DNS outage in Nexmo's infrastructure, Telerivet is currently encountering errors when sending messages to Nexmo. We are working to resolve this issue.
- monitoring Oct 21, 2016, 05:36 PM UTC
We have temporarily hardcoded the IP addresses of Nexmo's servers on Telerivet's servers, so Nexmo should be working again.
- resolved Oct 25, 2016, 09:40 AM UTC
The outage of Nexmo on Friday was related to the large distributed denial of service attack against Dyn (https://en.wikipedia.org/wiki/October_2016_Dyn_cyberattack). No additional DNS outages have been observed since Friday.