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-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 ? Operational
Nexmo Dashboard Operational
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
Jan 24, 2017
Resolved - Searches on Nexmo Dashboard and Developer API are now working normally.
Jan 24, 06:03 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 6, 20:49 UTC
Resolved - support@nexmo.com is functional again
Jan 24, 05:13 UTC
Investigating - We are experiencing technical problems with our Support email address: support@nexmo.com

If you need to contact our Support team, our website continues fully available (https://help.nexmo.com).
Alternatively, you can also reach us on support@nexmo.zendesk.com
Jan 24, 04:21 UTC
Jan 23, 2017
Resolved - This incident has been resolved.
Jan 23, 22:29 UTC
Investigating - Please be advised that due to local issues with our suppliers in Syria we have temporarily lost reach to Syriatel (41701).
Jan 23, 17:08 UTC
Jan 22, 2017

No incidents reported.

Jan 21, 2017

No incidents reported.

Jan 20, 2017

No incidents reported.

Jan 19, 2017
Resolved - This incident has been resolved.
Jan 19, 22:39 UTC
Investigating - Please be advised that due to local issues with our suppliers in Turkmenistan we have temporarily lost reach to 43801
We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 19, 21:29 UTC
Resolved - Service is completely restored since 18/01/2017 at 16:44 UTC.
Jan 19, 00:39 UTC
Monitoring - Please be advised that the emergency maintenance has been completed. We are currently monitoring all the affected services.
Jan 18, 16:55 UTC
Identified - Emergency maintenance - 18/01/2017 - 16:00-18:00 UTC maximum (expected duration 45-60 minutes)

Please be advised that we will need to carry out emergency maintenance on our Singapore data center today at around 16:00 UTC.
In preparation to this maintenance we are performing operations that may have impact on Nexmo services in terms of latency.

Services that will be affected by this maintenance with latency will be redirected from our Singapore data centre.

This maintenance will last for up to two hours. As a consequence, in addition to the expected latency, some services will be unavailable for up to two hours:

Affected services that will be unavailable during the maintenance duration will be Chat App API, smpp3.nexmo.com and smpp4.nexmo.com
Jan 18, 15:45 UTC
Jan 18, 2017
Please be advised that we experienced an issue with outbound SIP requests from servers originating in Europe. Customers with traffic originating in other regions were not affected. Customer who experienced this issue will have received a response of 503. The origination depends on the geographic location of your servers.

We apologise for any inconvenience caused by this issue.
Jan 18, 12:32 UTC
Jan 17, 2017
Resolved - This incident has been resolved.
Jan 17, 20:34 UTC
Investigating - Please be advised that due to local issues with our suppliers in Portugal, we are encountering quality issues to NOS (26803).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 17, 16:43 UTC
Resolved - This incident has been resolved.
Jan 17, 20:34 UTC
Investigating - Please be advised that due to local issues with our suppliers in Portugal, we are encountering quality issues to MEO (26806).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 17, 16:44 UTC
Resolved - This incident has been resolved.
Jan 17, 20:33 UTC
Update - Please be advised that due to local issues with our suppliers in Portugal, we are encountering quality issues to Vodafone (26801).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 17, 16:02 UTC
Investigating - We are currently investigating this issue.
Jan 17, 16:01 UTC
Resolved - This incident has now been resolved
Jan 17, 12:54 UTC
Investigating - Please be advised that we have identified an issue with outbound calls when using Voice API which we are currently investigating. Inbound calls are not affected by this issue.

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 17, 12:25 UTC
Resolved - This incidence has now been resolved.
Jan 17, 11:30 UTC
Monitoring - The issue has been mitigated now while the issues are being resolved. We will continue to monitor closely to ensure quality is maintained.
Jan 17, 11:18 UTC
Investigating - Please be advised that due to local issues with our suppliers in Russia, we have temporarily lost reach to Beeline (25099).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 17, 10:52 UTC
Resolved - This incidence has now been resolved.
Jan 17, 11:29 UTC
Monitoring - The issue has been mitigated now while the issues are being resolved. We will continue to monitor closely to ensure quality is maintained.
Jan 17, 11:18 UTC
Investigating - Please be advised that due to local issues with our suppliers in Russia, we have temporarily lost reach to MegaFon (25002).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 17, 10:48 UTC
Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017
Resolved - T-Mobile USA have confirmed that the issue was resolved at 2017-01-14 02:26:00 UTC. Traffic is flowing as expected since this time.
Jan 14, 04:30 UTC
Monitoring - T-Mobile USA confirmed that the issue is now resolved. We will continue to monitor closely to ensure the quality is maintained.
Jan 14, 03:23 UTC
Identified - T-Mobile USA is currently experiencing issues with their platform. As a result messages sent to this carrier might deliver with delays or fail.

We will update this announcement as soon as this is resolved.
Jan 14, 00:05 UTC
Jan 13, 2017

No incidents reported.

Jan 12, 2017

No incidents reported.

Jan 11, 2017
Resolved - This incidence has now been resolved.
Jan 11, 18:05 UTC
Monitoring - At the moment we are experiencing delays from our suppliers, any excess messages will be queued until the issue is completely resolved.
Jan 11, 14:38 UTC
Investigating - Please be advised that due to local issues with our suppliers in Cambodia, we have temporarily lost reach to Smart (45606).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 11, 10:51 UTC
Resolved - This issue has now been resolved.
Jan 11, 13:26 UTC
Investigating - Please be advised that due to local issues with our suppliers in Laos, we have temporarily lost reach to Star Telecom (45703).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 11, 10:50 UTC
Jan 10, 2017
Resolved - This incident has been resolved.
Jan 10, 16:52 UTC
Investigating - Due to a network infrastructure issue (resulting in packet loss and high latency) in one of our data centers, customers may experience HTTP time-out errors in their requests to Nexmo Verify, Chat App and US Short Code APIs. We have escalated this issue urgently to the data center provider and will provide updates as we have them.
Jan 10, 12:22 UTC
Resolved - This incident has been resolved.
Jan 10, 06:25 UTC
Investigating - Please be advised that due to local issues with our suppliers in Cambodia, we have temporarily lost reach to Smart (45606).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 10, 02:53 UTC
Resolved - This incident has been resolved.
Jan 10, 06:19 UTC
Investigating - Please be advised that due to local issues with our suppliers in Laos, we have temporarily lost reach to Star Telecom (45703).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jan 10, 02:56 UTC