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
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 20, 2018

No incidents reported today.

Jun 19, 2018

No incidents reported.

Jun 18, 2018
Resolved - This incident has been resolved.
Jun 18, 09:12 UTC
Update - We are now confident that the underlying cause was identified and corrected. We will be publishing a post-mortem to fully close the incident.
Jun 15, 14:50 UTC
Monitoring - A fix has been implemented to correct this behavior. Current messages should now we displaying the correct MSISDN as the originating number. We'll be monitoring to ensure there aren't any additional issues.
Jun 14, 20:30 UTC
Investigating - We are investigating an issue in the Nexmo dashboard and Developer Messages Search API where the originating phone number in inbound SMS (MO's) is showing as "[REDACTED]" rather than the number of the handset that sent the SMS.

The "MSISDN" (originating phone number) values sent in real-time to customer MO webhooks do not appear to be impacted.
Jun 14, 13:40 UTC
Resolved - This incident is confirmed to be fully resolved now. We will review details during the next few days and follow up sharing a public post-mortem.
Jun 18, 08:08 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 18, 03:29 UTC
Update - Our datacenter provider has confirmed resolution of this problem. We will keep a close eye on the connections during the next few hours.

The list of services that were impacted as been confirmed as:

- smpp3.nexmo.com, smpp4.nexmo.com, smpp3.nexmocn.com and smpp4.nexmocn.com
- Inbound calls to APAC Long Virtual Numbers
- Inbound SMS to Australia, Hong Kong, Singapore and Thailand numbers
- Outbound SMS to APAC destinations was partially affected, particularly towards Japan and Indonesia
Jun 18, 03:30 UTC
Update - We are continuing to investigate this issue.
Jun 18, 00:13 UTC
Investigating - Since 11:21 PM UTC we are experiencing a severe public network disruption in our Singapore datacenter. It is causing packet loss and high latency while connecting to endpoints served by that datacenter. Impacted services include:
- smpp3.nexmo.com
- smpp4.nexmo.com
- smpp3.nexmocn.com
- smpp4.nexmocn.com
- inbound calls to APAC Long Virtual Numbers
We will update this announcement as soon as we have more details available.
Jun 18, 00:11 UTC
Completed - The scheduled maintenance has been completed.
Jun 18, 08:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 04:00 UTC
Scheduled - One of Nexmo's suppliers will be conducting maintenance affecting only SMS to and from US Toll-Free numbers.
During the maintenance window, there may be short periods of latency for both inbound and outbound SMS. Any affected SMS will be queued for delivery throughout the maintenance and delivered as soon as possible once the maintenance is complete.

Please contact support@nexmo.com if you have any questions.

Time Zones:
US/Eastern: 06/17/2018 00:00 - 04:00
US/Central: 06/17/2018 23:00 - 02:00
US/Pacific: 06/17/2018 21:00 - 01:00
UTC: 06/18/2018 04:00 - 08:00
Jun 15, 23:39 UTC
Jun 17, 2018
Completed - The scheduled maintenance has been completed.
Jun 17, 09:17 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 17, 04:00 UTC
Scheduled - One of Nexmo's suppliers will be conducting maintenance affecting only SMS to and from US Toll-Free numbers.
During the maintenance window, there may be short periods of latency for both inbound and outbound SMS.
Any affected SMS will be queued for delivery throughout the maintenance and delivered as soon as possible once the maintenance is complete.

Please contact support@nexmo.com if you have any questions.

Time Zones:
US/Eastern: 06/16/2018 00:00 - 06:00
US/Central: 06/16/2018 23:00 - 05:00
US/Pacific: 06/16/2018 21:00 - 03:00
UTC: 06/17/2018 04:00 - 10:00
Jun 15, 23:31 UTC
Jun 16, 2018
Resolved - This incident has been resolved.
Jun 16, 16:24 UTC
Investigating - Please be advised that due to local issues with our suppliers in Cambodia, we have temporarily lost reach to Cellcard (45601)
Jun 16, 04:57 UTC
Jun 15, 2018
Resolved - This incident has been resolved.
Jun 15, 05:01 UTC
Investigating - Please be advised that due to local issues with our suppliers in Ethiopia , we have temorarily lost reach to Ethiopian Telecommunications Corporation (63601).
Jun 8, 13:03 UTC
Resolved - This incident has been resolved.
Jun 15, 02:42 UTC
Update - We are continuing to investigate this issue.
Jun 14, 22:17 UTC
Investigating - Please be advised that due to local issues with our suppliers in Argentina, we have temporarily lost reach to Movistar (722070).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jun 14, 22:15 UTC
Resolved - This incident has been resolved.
Jun 15, 00:06 UTC
Investigating - Please be advised that due to local issues with our suppliers in the Cambodia, we have temporarily lost reach to Cellcard (45601).

We are working on resolving these issues as soon as possible and we will post any updates here.
Jun 14, 09:58 UTC
Jun 13, 2018

No incidents reported.

Jun 12, 2018

No incidents reported.

Jun 11, 2018

No incidents reported.

Jun 10, 2018
Resolved - This incident has been resolved.
Jun 10, 18:08 UTC
Investigating - Please be advised that due to local issues with our suppliers in Cambodia , we have temporarily lost reach to Cambodia CamGSM(45601).
Jun 10, 06:16 UTC
Jun 9, 2018

No incidents reported.

Jun 7, 2018

No incidents reported.

Jun 6, 2018

No incidents reported.