New Nexmo source IP subnet for callback whitelisting
Scheduled Maintenance Report for Nexmo
Completed
The scheduled maintenance has been completed.
Posted 14 days ago. Nov 28, 2018 - 00:00 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted 15 days ago. Nov 27, 2018 - 00:00 UTC
Scheduled
On the 27th November 2018 Nexmo will be adding a new subnet 169.63.86.160/28 to the range we use to send callbacks via HTTP requests from our US data centre. These callbacks may include SMS delivery receipts, inbound SMS, Voice API callbacks, NCCO download requests, audio file download requests. If you are whitelisting traffic from Nexmo then you will need to make the necessary updates on your side to avoid any disruption to your traffic.

On December 17th, 2018 we will be deprecating the following subnets - 174.36.197.192/28, 173.193.199.16/28 and 174.37.245.32/29. Any time after this date you may wish to remove these subnets from your firewall configuration. We will no longer use these IPs to send traffic to our customers.

More information can always be found on this in our Knowledge base article What IP addresses should I whitelist (https://help.nexmo.com/hc/en-us/articles/204015053-What-IP-addresses-should-I-whitelist-in-order-to-receive-HTTP-requests-from-Nexmo-) in order to receive HTTP requests from Nexmo - please subscribe to follow this article to ensure you receive updates for the latest information on our IP ranges.

We apologise in advance for any inconvenience this may cause. If you have any questions about this please don’t hesitate to contact your account manager or submit a support request at https://help.nexmo.com.
Posted 21 days ago. Nov 20, 2018 - 16:33 UTC
This scheduled maintenance affected: SMS API (Outbound SMS, Inbound SMS), Voice APIs (See https://goo.gl/2WoAtx for Current known problems) (TTS API, SIP, Voice API), and Number Insight API, Verify API and Verify SDK, Chat App API, Developer API.