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
Dec 16, 2017
Resolved - This incident has been resolved.
Dec 16, 04:02 UTC
Identified - We have been notified of delays impacting the return of delivery receipts on Sprint. Outbound (MT) or Inbound (MO) messages aren't impacted at this time.

We will update this notification as soon as this is resolved.
Dec 15, 22:43 UTC
Dec 15, 2017
Resolved - This incident has been resolved.
Dec 15, 19:49 UTC
Investigating - Please be advised that due to local issues with our suppliers in Syria, we have temporarily lost reach to Syriatel (41701).

We are working on resolving these issues as soon as possible and we will post any updates here.
Dec 14, 19:58 UTC
Dec 13, 2017
Resolved - This incident has been resolved.
Dec 13, 03:40 UTC
Investigating - We regret to announce that we have lost reach to Laos Mobile Beeline (Vimpelcom). This may result in SMS traffic either being delayed or API requests being rejected upfront (with no cost).

We are working closely with our suppliers to find a resolution as quickly as possible and will keep you updated you on our progress. We apologize for any impact to your business.
Dec 12, 17:50 UTC
Dec 11, 2017

No incidents reported.

Dec 10, 2017

No incidents reported.

Dec 9, 2017

No incidents reported.

Dec 8, 2017
We regret to inform you that one of our suppliers recently experienced connectivity issues to the Nexmo platform which has impacted US Toll Free and US shortcode inbound SMS, outbound SMS, and delivery receipts.

Inbound messages sent between 13:45:00 UTC and14:20:00 UTC MO messages were queued on supplier’s platform. As of 17:50:00 UTC, these messages have been processed and submitted to customers.

Outbound messages sent at 13:45:00 UTC to 2017-12-08 14:20:00 UTC were rejected, and will need to be resubmitted at the customer's discretion.

Delivery receipts for messages were queued as of 13:45:00 UTC but has been cleared as of 19:55:00 UTC.
Dec 8, 21:14 UTC
Dec 7, 2017

No incidents reported.

Dec 6, 2017

No incidents reported.

Dec 5, 2017
Resolved - This incident has been resolved.
Dec 5, 21:01 UTC
Investigating - We regret to inform that currently we are experiencing a quality degradation to US Mobile T Mobile network. This might result in messages being delayed or rejected. We are closely working with suppliers to reach a speedy resolution and will update you on the progress.
Dec 5, 15:58 UTC
Dec 4, 2017

No incidents reported.

Dec 3, 2017
Resolved - This incident has been resolved.
Dec 3, 03:21 UTC
Investigating - Please be advised that due to local issues with our suppliers in Cambodia , we have temporarily lost reach to Metfone(45608).

We are working on resolving these issues as soon as possible and we will post any updates here.
Dec 2, 21:07 UTC