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 API Operational
Call API Operational
TTS API Operational
SIP ? Operational
Number Insight API Operational
Verify API and Verify SDK Operational
Chat App API Operational
Developer API ? Operational
Nexmo Dashboard Operational
Website Operational
Operational
Degraded Performance
Partial Outage
Major Outage
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
May 28, 2016

No incidents reported today.

May 27, 2016

No incidents reported.

May 26, 2016
Resolved - The problem causing delays to SMS records is now resolved.
All data in our Search Message APIs is again up to date.
May 26, 03:31 UTC
Investigating - We are experiencing latency in accessibility to records for SMS. Latency affects requests from the Nexmo Developer API (https://docs.nexmo.com/tools/developer-api/search-message).

Delivery of SMSs is not impacted by this incident.
May 25, 02:38 UTC
May 24, 2016

No incidents reported.

May 23, 2016
Resolved - This issue is now resolved.
May 23, 17:10 UTC
Investigating - We have identified problems with our Developer, Verify and SDK API's. We are investigating and we will update this announcement as soon as the problems are resolved.
May 23, 16:52 UTC
May 22, 2016

No incidents reported.

May 21, 2016

No incidents reported.

May 20, 2016

No incidents reported.

May 19, 2016

No incidents reported.

May 18, 2016
Resolved - This incident has been resolved.
May 18, 03:46 UTC
Monitoring - We have regained access to Iraq Asiacell. We are currently monitoring the situation.
May 17, 16:50 UTC
Investigating - Please be advised that due to local issues with our suppliers in Iraq, we have temporarily lost reach to Asiacell (41805).
May 17, 15:23 UTC
May 16, 2016

No incidents reported.

May 15, 2016

No incidents reported.

May 14, 2016

No incidents reported.