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
Jun 23, 2017

No incidents reported today.

Jun 22, 2017
Switzerland SMS - Inbound
Resolved - This incident is now resolved.
Jun 22, 17:02 UTC
Investigating - We are currently experiencing issues with inbound SMS on our Swiss Virtual numbers. These numbers aren't able to receive inbound SMS at this time. Please note that outbound SMS sent using your Swiss Virtual numbers as the sender ID should still deliver successfully, this is only an inbound issue.
Jun 22, 16:03 UTC
Jun 21, 2017

No incidents reported.

Jun 20, 2017
New TLS certificate for *.nexmo.com
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
Jun 20, 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.
Jun 5, 10:04 UTC
Customer Dashboard Analytics
Resolved - This incident has been resolved.
Jun 20, 06:38 UTC
Investigating - We are currently experiencing problems with Analytic's data in the Dashboard. Current reports and analytics data in the Customer Dashboard might not be accurate at this time. We will post an update as soon as this is solved.
Jun 19, 19:36 UTC
Jun 18, 2017

No incidents reported.

Jun 17, 2017

No incidents reported.

Jun 16, 2017
Dashboard Data delayed; Notifications missing
Resolved - All queues have cleared and customers are no longer experiencing delays.
We apologize for the disruption caused.
Jun 16, 19:52 UTC
Monitoring - The underlying cause of this issue has been resolved. Notifications are now being sent correctly. However customers will still see delays in data in the Nexmo dashboard while the existing queues are processed. We will post an update when data is back up-to-date.
Jun 16, 16:24 UTC
Investigating - Individual SMS and Voice record searches are unavailable for recent traffic in the Nexmo dashboard, and via the Developer API searches. Delays are currently less than one hour and we are working to resolve the issue.

Notification emails are also impacted by this platform issue so low-balance and virtual number release notifications are not being sent.

Inbound and outbound SMS and Voice traffic is *not* impacted. Payments and auto-reloads are *not* impacted.
Jun 16, 15:53 UTC
Jun 15, 2017
SMS delivery to Turkmenistan 43801
Resolved - This incident has been resolved.
Jun 15, 20:38 UTC
Investigating - Please be advised that due to local issues with our suppliers in Turkmenistan , we have temporarily lost reach to MTS (43801).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jun 15, 19:40 UTC
Emergency maintenance - Voice API - 15th June 2017 - 10:00 UTC
Resolved - This maintenance has been completed successfully.
Jun 15, 10:59 UTC
Investigating - We will be performing emergency maintenance on the Voice API infrastructure which may result in a brief time-out when issuing `GET` method on `/v1/calls`. There will be no impact on current and new calls during the maintenance. The maintenance is expected to last up to two hours.
We will provide further updates here.
Jun 15, 09:53 UTC
Jun 14, 2017

No incidents reported.

Jun 13, 2017

No incidents reported.

Jun 12, 2017
SMS delivery to Estonia 24802
Resolved - This incident has been resolved.
Jun 12, 17:48 UTC
Investigating - Please be advised that due to local issues with our suppliers in Estonia , we have temporarily lost reach to Elisa(24802).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jun 11, 20:35 UTC
Jun 10, 2017

No incidents reported.

Jun 9, 2017
SMS delivery to Cambodia - Smart Cambodia (45606)
Resolved - This incident has been resolved.
Jun 9, 04:53 UTC
Investigating - Please be advised that due to local issues with our suppliers in Cambodia, we have temporarily lost reach to Smart Cambodia (45606).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jun 9, 03:03 UTC
← Incident History Powered by StatusPage