Update - The issue with the processing delays has been resolved due to an implemented workaround. Currently terminating a recording using 'endOnSilence' is not available.
Apr 26, 15:58 UTC
Update - We are continuing to investigate this issue.
Apr 26, 13:56 UTC
Investigating - We are currently experiencing delays in connecting calls to conversations for Voice API calls. There is a delay of approximately 1 minute between the first call being answered and the actions in the NCCO being consumed. End users receiving calls are hearing only silence between answering the call and any actions being processed. This can result in end users waiting before hearing a Stream or Talk action, or connecting into an active conversation.

SIP and the deprecated voice APIs are not impacted by this issue.

We are working on resolving this and will post updates here.
Apr 26, 08:55 UTC
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 ? Degraded Performance
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
Apr 27, 2017

No incidents reported today.

Apr 25, 2017
Resolved - This issue has now been resolved
Apr 25, 13:06 UTC
Monitoring - Our routes are now functional towards Iran - MCI (43211), we will be monitoring the delivery to this network closely.
Apr 25, 08:00 UTC
Investigating - Please be advised that due to local issues with our suppliers in Iran, we have temporarily lost reach to MCI (43211)
We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 25, 07:46 UTC
Resolved - This incident has been resolved.
Apr 25, 02:28 UTC
Investigating - Please be advised that due to local issues with our suppliers in Venezuela, we have temporarily lost reach to Movistar (73404).

We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 24, 23:28 UTC
Apr 24, 2017
Resolved - This incident has been resolved.
Apr 24, 19:33 UTC
Investigating - Please be advised that due to local issues with our suppliers in Iran, we have temporarily lost reach to MCI( 43211)

We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 24, 17:11 UTC
Apr 23, 2017

No incidents reported.

Apr 22, 2017
Resolved - This incident has been resolved.
Apr 22, 23:27 UTC
Investigating - Please be advised that due to local issues with our suppliers in UK, we have temporarily lost reach to 3 (23420).

We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 22, 17:18 UTC
Apr 21, 2017

No incidents reported.

Apr 20, 2017
Resolved - This incident has been resolved.
Apr 20, 18:49 UTC
Investigating - Please be advised that due to local issues with our suppliers in Iraq, we have temporarily lost reach to Zain( 41820)

We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 20, 17:51 UTC
Due to issues in one of our Data Centers, all calls placed to our Voice API from the EMEA or North America regions may have failed with error code 502 during the time of this incident.
The duration of the incident was : Thursday 20th of April at 16:30 UTC to Thursday 20th of April at 17:04 UTC
This incident is fully resolved.
Apr 20, 16:52 UTC
Resolved - support@nexmo.com is back up. Any email sent in the past hour may have bounced back.

Apologies for any inconvenience this may have caused.
Apr 20, 06:58 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
Apr 20, 06:48 UTC
Apr 19, 2017

No incidents reported.

Apr 18, 2017

No incidents reported.

Apr 17, 2017
Resolved - This issue has now been resolved.
Apr 17, 03:38 UTC
Investigating - Please be advised that due to local issues with our suppliers in Iraq, we have temporarily lost reach to Zain( 41820)

We are working on resolving these issues as soon as possible and we will post any updates here.
Apr 16, 23:09 UTC
Apr 15, 2017

No incidents reported.

Apr 14, 2017

No incidents reported.

Apr 13, 2017

No incidents reported.