New TLS certificate for *.nexmo.com
Scheduled Maintenance Report for Nexmo
Completed
A new TLS certificate has been deployed for *.nexmo.com.

If you face any certificate related rejection, please follow these steps:

1. Retrieve the new certificate from https://static.nexmo.com/tls/2017-06/wildcard.nexmo.com.pem (this certificate is relevant for *.nexmo.com).
2. Export it in the format you prefer.
3. Import it into your application.

If you need to update the root certificate authority, this is available on https://www.digicert.com/CACerts/DigiCertGlobalRootG2.crt
Posted 6 months ago. Jun 20, 2017 - 09:40 UTC
Scheduled
On June 20th, Nexmo will replace the public TLS certificate on *.nexmo.com. This change will have no impact for most customers, since our new certificate will be signed by the major certificate authorities.

If you store your certificates locally, your platform might be still set up to use the old certificate, which will get revoked on June 21st. Before then, you will need to:
1. Retrieve the new certificate from https://static.nexmo.com/tls/2017-06/wildcard.nexmo.com.pem (this certificate is relevant for *.nexmo.com).
2. Export it in the format you prefer.
3. Import it into your application.

(If you also use intermediate certificates, this can be found at https://static.nexmo.com/tls/2017-06/wildcard.nexmo.com-intermediate.pem.)

If you need further assistance, please do not hesitate to contact us at support@nexmo.com.
Posted 6 months ago. Jun 05, 2017 - 10:04 UTC
This scheduled maintenance affected: SMS API (Outbound SMS, SMPP), Voice-related API's (TTS API, Voice API), and Number Insight API, Verify API and Verify SDK, Developer API, Website.