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.

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.

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.

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.

A fix has been implemented and we are monitoring the results.

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.

"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