Sharpen Status

Resolved: This issue was resolved at 9:25 PM ET 2026-02-19. Our status page mechanism encountered an issue at the time of us marking resolution. This is retroactive conclusion of the incident.

Investigating: Data, Monitoring, and testing has confirmed recent fixes have resolved this issue.

Investigating: We are continuing to monitor and test to validate improvement following our recent 2 fixes.

Investigating: We are continuing working through our second fix and will update this page when it is complete.

Investigating: Our initial fix is showing significant effectiveness, drastically improving the timeliness of Sharpen Q voice interaction related interactions. Call delivery, answer times, and interaction call controls should mostly be restored at this point. We've identified an additional fix which will bring further improvements shortly.

Investigating: We are continuing to investigate this issue. We have introduced 1 fix and are working on another which we expect will improve performance.

Investigating: We are continuing to investigate the issue. We're receiving additional reports of some users experiencing intermittent 504 Gateway timeout errors. We are including this symptom in our investigation as it likely shares the same root cause.

Investigating: Thank you for your continued patience. We continue to aggressively address the intermittent service degradation impacting call connection times (agent-caller delay) and interface responsiveness. We will continue to pursue resolution as soon as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Thank you for your continued patience. We are continuing to investigate the issue with all necessary resources involved. The problem is localized, but thus far our remediation efforts have not sufficiently remediated impact. We are continuing to explore all options to resolve the issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate the issue and have all necessary resources engage to resolve the issue as soon as possible.

Investigating: We are currently investigating reports of degraded call quality affecting some customers, intermittently. The following behaviors have been reported beginning around 12:00 PM ET:

• Delays (up to 25+ seconds) between a call connecting and the interaction appearing in the agent interface
• Dead air on inbound calls prior to ringing and after agent answer
• Calls populating in queue but experiencing delays before being assigned to an agent
• Absence of hold music for callers waiting in queue
• Inability to place calls on hold

Our team is actively investigating the cause. We will provide an update as soon as additional information is available.

Affected: Voice interactions

Resolved: This issue was resolved at 9:25 PM ET 2026-02-19. Our status page mechanism encountered an issue at the time of us marking resolution. This is retroactive conclusion of the incident.

Investigating: Data, Monitoring, and testing has confirmed recent fixes have resolved this issue.

Investigating: We are continuing to monitor and test to validate improvement following our recent 2 fixes.

Investigating: We are continuing working through our second fix and will update this page when it is complete.

Investigating: Our initial fix is showing significant effectiveness, drastically improving the timeliness of Sharpen Q voice interaction related interactions. Call delivery, answer times, and interaction call controls should mostly be restored at this point. We've identified an additional fix which will bring further improvements shortly.

Investigating: We are continuing to investigate this issue. We have introduced 1 fix and are working on another which we expect will improve performance.

Investigating: We are continuing to investigate the issue. We're receiving additional reports of some users experiencing intermittent 504 Gateway timeout errors. We are including this symptom in our investigation as it likely shares the same root cause.

Investigating: Thank you for your continued patience. We continue to aggressively address the intermittent service degradation impacting call connection times (agent-caller delay) and interface responsiveness. We will continue to pursue resolution as soon as possible.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: Thank you for your continued patience. We are continuing to investigate the issue with all necessary resources involved. The problem is localized, but thus far our remediation efforts have not sufficiently remediated impact. We are continuing to explore all options to resolve the issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate the issue and have all necessary resources engage to resolve the issue as soon as possible.

Investigating: We are currently investigating reports of degraded call quality affecting some customers, intermittently. The following behaviors have been reported beginning around 12:00 PM ET:

• Delays (up to 25+ seconds) between a call connecting and the interaction appearing in the agent interface
• Dead air on inbound calls prior to ringing and after agent answer
• Calls populating in queue but experiencing delays before being assigned to an agent
• Absence of hold music for callers waiting in queue
• Inability to place calls on hold

Our team is actively investigating the cause. We will provide an update as soon as additional information is available.

Affected: Voice interactions

Resolved: Service health-checks and sustained monitoring of our call routing systems have shown recovery to the platform. Validation testing across Classic Logic configurations or inbound routes that send calls directly to queue are routing in a timely fashion.

In the event you have users still encountering connection issues, please reach out to the Care Team with examples of the misbehavior.

Monitoring: The corrective changes have been made across our infrastructure, and we're actively monitoring the system/running health-checks. The expectation is that call routing through Classic Logic, call audio/quality, and interaction handling behavior should be considerably improved for impacted users.

Identified: We've identified the underlying issue and are working with our internal teams to get a fix deployed across our Production environment. We're targeting a comprehensive roll-out for our infrastructure in the next 30 minutes. Further updates will follow as soon as corrective actions have been fully implemented.

Investigating: An attempted remediation effort was made to address calls dropping in Classic Logic. While that did have the expected outcome, a second new set of symptoms were introduced. This includes delays in calls routing to agents in SharpenQ, and delays when agents attempt to connect to the interaction. Our teams are continuing to investigate with all available resources.

Investigating: We're currently investigating an issue for IZ1 customers, where Inbound routes pointed to a Classic Logic configuration are experiencing unexpected disconnects. We're actively able to reproduce the problem and are working to restore service as soon as possible.