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
Sep 24, 2017

No incidents reported today.

Sep 23, 2017

No incidents reported.

Sep 22, 2017

No incidents reported.

Sep 21, 2017

No incidents reported.

Sep 20, 2017
Resolved - This degradation was due to an undetected bug in a dashboard release which was deployed at 2:32PM UTC, and then rolled back at 3:29PM UTC. At this time there is no longer any issue with logging in for any users.

No product services - SMS or Voice - were impacted by this incident.

We apologize for any impact to your business.
Sep 20, 15:39 UTC
Investigating - Secondary dashboard users are currently unable to log into https://dashboard.nexmo.com if 2FA authentication has been enabled by the primary account owner. We are investigating this issue and will update as quickly as possible.
Sep 20, 15:26 UTC
Sep 19, 2017

No incidents reported.

Sep 18, 2017

No incidents reported.

Sep 17, 2017

No incidents reported.

Sep 16, 2017

No incidents reported.

Sep 15, 2017

No incidents reported.

Sep 14, 2017
Resolved - Incident has been resolved.
Sep 14, 15:47 UTC
Investigating - We are currently modifying Sender IDs on 5108 and 51011 due to issues with main suppliers. After a reroute CR is back to normal, hence quality is not affected. We are working on resolving CR issues with suppliers and will revert changes once back to normal.
Sep 14, 10:50 UTC
Postmortem - Read details
Sep 20, 15:05 UTC
Resolved - This outage has now been completely resolved, as of 15:02:35. We will publish a full post-mortem shortly.
Sep 14, 14:38 UTC
Update - This incident was resolved at 4:20 pm UTC.

This service is currently running from our disaster recovery location. Due to this, calls may experience additional latency.
Sep 13, 19:50 UTC
Monitoring - This incident was resolved at 4:20 pm UTC.
Sep 13, 16:45 UTC
Investigating - Please note that we are experiencing an outage in the US region since 15:31 UTC for the Voice API. Voice API requests are returning 500 HTTP responses and inbound calls are also affected by this outage.
Sep 13, 15:47 UTC
Sep 12, 2017

No incidents reported.

Sep 11, 2017

No incidents reported.

Sep 10, 2017

No incidents reported.