NUACOM Status

Resolved: Incident Resolved: A sudden spike in database load caused degraded performance across several services, which in turn left a number of recordings stuck in our processing queue.

What we did initially:

• Optimized the database cluster to eliminate the performance bottleneck
• Rolled out more internal alerts related to the database

Impact Remediation

• Manually cleared the backlog of unprocessed recordings
• Conducted end‑to‑end verification to ensure all services returned to normal operation

We apologize for the disruption and appreciate your patience.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Some of the customer accounts experienced delays in having their call connecting, we are investigating the issue, the system is fully operational.

Investigating: We are currently investigating this issue.

Resolved: Incident Resolved: A sudden spike in database load caused degraded performance across several services, which in turn left a number of recordings stuck in our processing queue.

What we did initially:

• Optimized the database cluster to eliminate the performance bottleneck
• Rolled out more internal alerts related to the database

Impact Remediation

• Manually cleared the backlog of unprocessed recordings
• Conducted end‑to‑end verification to ensure all services returned to normal operation

We apologize for the disruption and appreciate your patience.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Some of the customer accounts experienced delays in having their call connecting, we are investigating the issue, the system is fully operational.

Investigating: We are currently investigating this issue.

Resolved: Incident Resolved: A sudden spike in database load caused degraded performance across several services, which in turn left a number of recordings stuck in our processing queue.

What we did initially:

• Optimized the database cluster to eliminate the performance bottleneck
• Rolled out more internal alerts related to the database

Impact Remediation

• Manually cleared the backlog of unprocessed recordings
• Conducted end‑to‑end verification to ensure all services returned to normal operation

We apologize for the disruption and appreciate your patience.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Some of the customer accounts experienced delays in having their call connecting, we are investigating the issue, the system is fully operational.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

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

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: Incident Resolved: A sudden spike in database load caused degraded performance across several services, which in turn left a number of recordings stuck in our processing queue.

What we did initially:

• Optimized the database cluster to eliminate the performance bottleneck
• Rolled out more internal alerts related to the database

Impact Remediation

• Manually cleared the backlog of unprocessed recordings
• Conducted end‑to‑end verification to ensure all services returned to normal operation

We apologize for the disruption and appreciate your patience.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Some of the customer accounts experienced delays in having their call connecting, we are investigating the issue, the system is fully operational.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

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

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: Incident Resolved: A sudden spike in database load caused degraded performance across several services, which in turn left a number of recordings stuck in our processing queue.

What we did initially:

• Optimized the database cluster to eliminate the performance bottleneck
• Rolled out more internal alerts related to the database

Impact Remediation

• Manually cleared the backlog of unprocessed recordings
• Conducted end‑to‑end verification to ensure all services returned to normal operation

We apologize for the disruption and appreciate your patience.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Some of the customer accounts experienced delays in having their call connecting, we are investigating the issue, the system is fully operational.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

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

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.