Monitoring - There are no delays being observed at this moment and we are continuing to monitor to work towards a full resolution.
Apr 20, 17:45 UTC
Identified - We are currently facing intermittent SMS delays towards Indonesia.

A short term solution to minimise the message delays has been implemented, while we work on a full resolution to the problem.
Apr 20, 07:09 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 APIs (See https://goo.gl/2WoAtx for Current known problems) 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
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 24, 2018

No incidents reported today.

Apr 23, 2018

No incidents reported.

Apr 22, 2018

No incidents reported.

Apr 21, 2018

No incidents reported.

Apr 19, 2018
Resolved - This incident was resolved at 17:09 UTC.
Apr 19, 19:42 UTC
Investigating - "Analytics" (i.e. aggregate data) shown in the dashboard are incomplete. Traffic data from today 12:17 PM UTC onward is not included in these statistics.

Searching for individual transactions is not impacted.

No product services - such as sending/receiving SMS or making voice calls - are impacted.

We will post updates here as we have more information
Apr 19, 13:18 UTC
Apr 18, 2018
Resolved - This incident is now resolved.

Start time: 7:25 pm UTC
End time: 8:07 pm UTC
Apr 18, 20:36 UTC
Investigating - We are currently experiencing problems with one of our Pre-approved SMS alerts shortcode routes. As a result you may experience failures on your shortcode traffic.
Apr 18, 19:30 UTC
Apr 17, 2018

No incidents reported.

Apr 16, 2018

No incidents reported.

Apr 15, 2018

No incidents reported.

Apr 14, 2018

No incidents reported.

Apr 13, 2018
Resolved - We regret that this longstanding issue has still not been resolved. Unfortunately the rebuilding of aggregate data from a range of sources is a delicate operation and we are committed to ensuring that the result is absolutely accurate. In consideration of the scale of the impact and the delay in resolution, we have made the decision to track further progress at https://help.nexmo.com/hc/en-us/articles/360001020387 in the Current Known Issues section of our Knowledgebase rather than as an incident. You can follow updates by subscribing to that article.
Apr 13, 14:34 UTC
Update - Unfortunately, Dashboard statistics are not up-to-date yet.

We are close to completing the entire re-processing of data, and will update this announcement with the final confirmation.
Apr 6, 06:15 UTC
Update - We apologize for the time it is taking to get this issue fully resolved. Due to the volume of data involved re-processing is taking a considerable amount of time. The current ETA for final resolution is March 29th.
Mar 27, 09:41 UTC
Update - We are re-processing our transactional logs in order to accurately re-build all aggregate statistics for March 7th 2018. This is estimated to be finished by the end of this week. We will update this incident posting once work is complete.

Aggregate statistics prior to and following March 7th are *not* impacted.
Mar 14, 11:41 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 8, 12:06 UTC
Update - Aggregate traffic data for March 7th 2017 is still inaccurate, but data from today (March 8th) is complete. We are working on reprocessing the raw transactional data for March 7th to ensure all dashboard statistics are complete and accurate.
Mar 8, 12:06 UTC
Investigating - "Analytics" (i.e. aggregate data) shown in the dashboard are incomplete. A substantial portion of traffic data from today (March 7th UTC) is not included in these statistics.

Searching for individual transactions is not impacted.

No product services - such as sending/receiving SMS or making voice calls - are impacted.

We will post updates here as we have more information
Mar 7, 17:40 UTC
Apr 12, 2018
Resolved - This incident is now resolved. Records for SMS and calls on the Nexmo Dashboard or Developer API can be read in real time again.
Apr 12, 12:13 UTC
Update - All the SMS CDR should be available. Our engineering team is running further checks and monitoring the situation.
Apr 10, 13:20 UTC
Monitoring - About 10% of the SMS CDR's still face latency that can reach up to 24h. Other CDR's are now processed in real time again. We will keep you posted on the further development.
Apr 10, 09:11 UTC
Identified - We are currently experienced latency in searching for traffic records for SMS or calls. The latency is observed in both searches using the Nexmo Dashboard and Developer API. The impacted data range is 6 days, but not only a subset of this traffic. Our Engineering team is currently working on getting all the data available.

Delivery of SMS and connection of calls are not impacted by this incident.
Apr 9, 11:25 UTC
Apr 11, 2018

No incidents reported.