All Systems Operational
SMS API Operational
Outbound SMS   ? Operational
Inbound SMS   ? Operational
SMPP   ? Operational
Europe traffic   ? Operational
North America (US, Canada & Caribbean) traffic   ? Operational
South & Central America traffic   ? Operational
Africa traffic   ? Operational
Asia & Oceania traffic   ? Operational
Voice APIs (See https://goo.gl/2WoAtx for Current known problems) Operational
TTS API   Operational
SIP   ? Operational
Voice API   ? Operational
Europe Traffic   Operational
North America (US, Canada & Caribbean) traffic   Operational
South & Central America traffic   Operational
Africa traffic   Operational
Asia & Oceania traffic   Operational
Number Insight API   Operational
Verify API and Verify SDK   Operational
Chat App API   Operational
Developer API   ? Operational
Nexmo Dashboard   Operational
Website   Operational
Billing and Payments   Operational
Reports API   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
On the 17th December 2018 Nexmo will be deprecating the range of IP addresses currently used for SMPP servers 0, 1 and 2.

Hostname - smpp0.nexmo.com
Current IP Address 174.37.245.38
New IP Address 108.168.254.225

Hostname - smpp1.nexmo.com
Current IP Address 174.37.245.37
New IP Address 108.168.254.238

Hostname - smpp2.nexmo.com
Current IP Address 174.36.197.197
New IP Address 108.168.254.239

The new IP addresses shown above are already live today. Therefore we would recommend that you bind either via hostname (which will not change) or the new IP addresses as soon as possible. After the December 17th the current/old IP addresses will no longer be available.

If you are whitelisting traffic in your firewall based on IP then you will need to add the new IP addresses as soon as possible. You must add the new IP address by December 17th to avoid any disruption to your traffic. On December 17th we will be modifying DNS A records to point all of the above hostnames to the new IP addresses.

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 on Nov 20, 16:37 UTC
rest.nexmo.com uptime
Fetching
api.nexmo.com uptime
Fetching
rest.nexmo.com response time
Fetching
api.nexmo.com response time
Fetching
smpp0.nexmo.com uptime
Fetching
smpp1.nexmo.com uptime
Fetching
smpp2.nexmo.com uptime
Fetching
smpp3.nexmo.com uptime
Fetching
smpp4.nexmo.com uptime
Fetching
Past Incidents
Dec 15, 2018

No incidents reported today.

Dec 14, 2018
Resolved - This incident has been resolved.
Dec 14, 02:02 UTC
Update - We are continuing to monitor for any further issues.
Dec 13, 18:58 UTC
Monitoring - Please be advised that local issues with the operator Claro 72405 in Brazil is now resolved, we are currently monitoring delivery to this network.
Dec 13, 11:44 UTC
Investigating - Please be advised that due to local issues with the operator Claro 72405 in Brazil, we are currently experiencing intermittent delivery to this network.

Their technical team is working on resolving this as soon as possible and we will post any updates here.
Dec 13, 05:51 UTC
Dec 12, 2018

No incidents reported.

Dec 11, 2018

No incidents reported.

Dec 10, 2018
Resolved - The issue has been confirmed as resolved.
Dec 10, 22:17 UTC
Update - We are continuing to monitor for any further issues.
Dec 10, 18:40 UTC
Monitoring - As of 18:08 UTC the issue has been resolved and we are monitoring the situation.
Dec 10, 18:38 UTC
Investigating - Currently we are experiencing issues with our US Shared Short Code API. As a result you may see a 504 server response for API requests to: https://rest.nexmo.com/sc/us/alert/json
No other services or APIs are impacted by this issue.

We will post updates as new information becomes available or when the incident is fully resolved.
Dec 10, 18:21 UTC
Dec 9, 2018

No incidents reported.

Dec 8, 2018

No incidents reported.

Dec 7, 2018
Resolved - This incident has been resolved.
Dec 7, 06:39 UTC
Monitoring - We have been informed that O2 has resolved this incident and we will continue to monitor the service performance.
Dec 7, 03:51 UTC
Identified - Please be advised that due to local issues with our suppliers in United Kingdom, you might experience latency issues to UK O2.

Our suppliers have identified the issue and are still working to resolve this. We will keep you updated if any progress.
Dec 6, 16:45 UTC
Monitoring - Please be advised that due to local issues with our suppliers in United Kingdom, we might experience latency issues to UK O2 (23410).

Our suppliers have identified the issue and are working to resolve this. We will keep you updated on any progress.
Dec 6, 12:53 UTC
Dec 6, 2018
Resolved - We have been informed that Softbank has resolved this incident.
Dec 6, 10:29 UTC
Investigating - Please be advised that Softbank (44020) is currently experiencing connection problems since 04:39 UTC, SMS and Voice services are impacted.
We will update once we have more information.
Dec 6, 08:30 UTC
Completed - The scheduled maintenance has been completed.
Dec 6, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 6, 07:00 UTC
Scheduled - Between [06-DEC-2018 07:00] UTC and [06-DEC-2018 10:00] UTC US Cellular will be performing emergency maintenance.

During the maintenance window, there may be periods of message latency and failures for both inbound and outbound SMS. Please contact support@nexmo.com if you have any questions.
Dec 5, 22:52 UTC
Dec 5, 2018
Postmortem - Read details
Dec 12, 13:21 UTC
Resolved - This incident has been resolved.
Dec 5, 22:29 UTC
Monitoring - Between 12:32 and 15:26 UTC, a number of Verify transaction flows were not fully completed. The outbound SMS steps of the Verify flow were not sent out due to an internal failure. The subsequent calls for the Verify request were successfully generated, however. This resulted in a lower rate of success for Verify requests during this period.

We believe this is now fixed, however, we will continue to monitor the performance of the Verify product to ensure that the issue has been fully resolved.
Dec 5, 16:11 UTC
Dec 4, 2018

No incidents reported.

Dec 3, 2018

No incidents reported.

Dec 2, 2018

No incidents reported.

Dec 1, 2018

No incidents reported.