This incident has been resolved.

The teams are continuing to monitor performance. Consumption has caught up and service is operational although reporting will need to complete processing of backlogged requests.

The development team made a change to the API which has helped alleviate latent conditions. Error rates are now showing marked improvement; however reporting has a large backlog of requests that will need to finish processing. Monitoring to ensure mitigation strategy is successful. Updates to follow.

The issue has been isolated to an API for the service. Investigation continues. Next update 5:30pm EST or as information becomes available.

Queries are continuing to run slow with up to one hour between report request and arrival for some users while a delays of a few seconds for performance dashboards and interaction searches. The development teams are continuing to investigate latent conditions. Next update 4:00pm EST or as information becomes available.

The teams are continuing to work on fix actions for the issue. Queries are processing, but are latent. Next status 2:30pm EST.

The development team added additional nodes which are now online and shards relocated. Slow query performance may still be an issue for users. The teams are continuing investigation and next steps. Next update 1:30pm EST.

Users may continue to experience latency when performing queries. Investigation into underlying cause and mitigation continues. Next update 12:30 pm EST.

The development team has taken steps to help speed recovery by scaling down a dependent service. Users may experience continued delays with querying data until service health improves. The teams are currently monitoring and determining additional fix actions as warranted. Next update 11:30 am EST.

Users in the America's region may be experiencing delays with call detail records. The development teams are currently triaging and determining next steps. Next update 11 am EST or sooner as information becomes available.