Investigating - Please be advised that due to local issues with our suppliers in Turkmenistan, we have temporarily lost reach to 43801 MTS Turkmenistan.

We are working on resolving these issues as soon as possible and we will post any updates here.
Feb 19, 16:05 UTC
Investigating - Please note that we are experiencing latency in accessibility to records for SMS and Calls.
Latency affects requests from our Dashboard, and the Nexmo Developer API (https://docs.nexmo.com/tools/developer-api/search-message).
Delivery is not impacted by this issue.
Jan 30, 19:47 UTC
SMS API Operational
Outbound SMS ? Degraded Performance
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-related API's Operational
Call API 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 ? Degraded Performance
Nexmo Dashboard Degraded Performance
Website Operational
Billing and Payments Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
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
Feb 18, 2017

No incidents reported.

Feb 17, 2017
Resolved - This issue has been resolved.
Feb 17, 11:06 UTC
Monitoring - A fix has been deployed and we are now seeing all Verify requests being completed or expiring as expected.

We will continue monitoring to ensure the degradation is completely resolved.
Feb 17, 11:33 UTC
Investigating - We are currently experiencing a degraded performance on Verify, impacting expiration/completion time for certain verification IDs.

This is currently being investigated by our engineers.
Feb 17, 10:22 UTC
Resolved - This incident is confirmed as resolved since 3am UTC.

A post-mortem analysis will be published as soon as we complete internal reviews.
Feb 17, 09:32 UTC
Monitoring - A workaround has been implemented, and we are no longer rejecting SMPP bind requests.

We will continue monitoring until a final fix is deployed.
Feb 17, 03:05 UTC
Investigating - Please note we are experiencing a technical problem affecting SMPP customers. Bind requests might be facing rejections.

Customers using our REST APIs are not impacted.
Feb 17, 02:51 UTC
Feb 16, 2017
Resolved - This incident is now confirmed as resolved.
Feb 16, 04:14 UTC
Monitoring - We have been notified that these issues are now resolved and message delivery should be back to normal. We are currently monitoring the situation.
Feb 16, 00:05 UTC
Identified - After further investigation we have identified that this issue is also impacting traffic sent with certain Dedicated Shortcodes, certain Shared Shortcodes for US 2FA traffic as well as Toll Free Numbers.
Current impact includes delays and possible failures and/or rejections.
We will update this announcement as soon as we have more information.
Feb 15, 21:01 UTC
Investigating - We are currently investigating messaging issues to US carriers. Current findings lead to these issues impacting at least messages sent using US Toll Free Numbers. We are working with our supplier to get this resolved as soon as possible.

We will update this announcement as soon as we have further information.
Feb 15, 20:36 UTC
Feb 14, 2017

No incidents reported.

Feb 13, 2017

No incidents reported.

Feb 12, 2017

No incidents reported.

Feb 11, 2017

No incidents reported.

Feb 10, 2017

No incidents reported.

Feb 9, 2017
Resolved - This issue is now resolved.
Feb 9, 15:37 UTC
Investigating - Please be advised that due to local issues with our suppliers in Philippines, we have temporarily lost reach to Sun (51505).
Feb 9, 06:48 UTC
Feb 8, 2017

No incidents reported.

Feb 7, 2017

No incidents reported.

Feb 6, 2017
Resolved - This incident has been resolved.
Feb 6, 18:50 UTC
Investigating - Please be advised that due to local issues with our suppliers in Bangladesh, we have temporarily lost reach to 47007 Airtel.

We are working on resolving these issues as soon as possible and we will post any updates here.
Feb 6, 17:56 UTC
Feb 5, 2017

No incidents reported.