- Detected by Pingoru
- May 07, 2026, 05:16 PM UTC
- Resolved
- May 07, 2026, 06:03 PM UTC
- Duration
- 46m
Affected: app.iz1.sharpen.cxSharpen QInsightsInbound VoiceOutbound Voice
Timeline · 4 updates
-
investigating May 07, 2026, 05:16 PM UTC
Our engineering teams are aware of an infrastructure issue that is impacting call routing, WebRTC connectivity for users, and various page navigation efforts (Insights, Admin pages, Logic configuration editors, etc). We have pin-pointed the fault zone and have all necessary resources engaged to restore services as quickly as possible.
-
identified May 07, 2026, 05:18 PM UTC
Our engineering teams are actively working through corrective actions, and further status updates will be provided as a resolution timeline is established.
-
monitoring May 07, 2026, 05:41 PM UTC
The corrective action has been deployed in our infrastructure, and all identified service fault-zones have been addressed. Insights reporting, call routing, and WebRTC connection are now responsive and behaving in the expected fashion. We're actively monitoring with our engineering team. If you're continuing to see impact, please reach out to the Care Team via your existing support case!
-
resolved May 07, 2026, 06:03 PM UTC
Validation testing performed across the application suite has confirmed recovery to all impacted systems. In the event you are still encountering lingering effects tied to interaction routing, WebRTC connectivity problems, or an inability to access a specific configuration page within the app - please reach out to our Care Team for further assistance!
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 02:48 PM UTC
- Resolved
- Feb 20, 2026, 09:13 PM UTC
- Duration
- 6h 24m
Affected: Inbound Voice
Timeline · 5 updates
-
investigating Feb 20, 2026, 02:48 PM UTC
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.
-
investigating Feb 20, 2026, 05:51 PM UTC
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.
-
identified Feb 20, 2026, 06:24 PM UTC
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.
-
monitoring Feb 20, 2026, 07:12 PM UTC
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.
-
resolved Feb 20, 2026, 09:13 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 05:50 PM UTC
- Resolved
- Feb 20, 2026, 12:04 PM UTC
- Duration
- 18h 14m
Affected: Sharpen QInbound Voice
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- Dec 30, 2025, 09:09 PM UTC
- Resolved
- Dec 30, 2025, 09:52 PM UTC
- Duration
- 43m
Affected: app.sharpencx.comSharpen QDashboardsInsights
Timeline · 4 updates
-
identified Dec 30, 2025, 09:09 PM UTC
Users of the Sharpen platform in IZ0 are likely experiencing a variety of symptoms mostly impacting Sharpen Q and Insights. Our teams are engaged working to resolve the issue as soon as possible.
-
identified Dec 30, 2025, 09:13 PM UTC
Sharpen Q has been restored. We are now working on restoring Insights defects and expect recovery shortly.
-
monitoring Dec 30, 2025, 09:34 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 30, 2025, 09:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 08:48 PM UTC
- Resolved
- Nov 17, 2025, 09:12 PM UTC
- Duration
- 24m
Affected: Dashboards
Timeline · 3 updates
-
investigating Nov 17, 2025, 08:48 PM UTC
We are currently investigating a failure to load Insights Dashboards
-
monitoring Nov 17, 2025, 08:59 PM UTC
A fix has been implemented and we are monitoring the results. A refresh of the Insights dashboard will be necessary to restore functionality.
-
resolved Nov 17, 2025, 09:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 14, 2025, 01:08 PM UTC
- Resolved
- Nov 14, 2025, 10:48 PM UTC
- Duration
- 9h 39m
Affected: Inbound VoiceEmailEmail
Timeline · 21 updates
Read the full incident report →
- Detected by Pingoru
- Oct 26, 2025, 01:06 AM UTC
- Resolved
- Oct 26, 2025, 01:38 AM UTC
- Duration
- 32m
Affected: Sharpen QOutbound Voice
Timeline · 2 updates
-
investigating Oct 26, 2025, 01:06 AM UTC
Starting at approximately 8PM Eastern, users in the Queue application are experiencing a "Could not place call" error in the UI. We're aware of the problem and actively engaged with our engineering teams to restore functionality as quickly as possible. Further updates will be provided as soon as we have recovery actions identified.
-
resolved Oct 26, 2025, 01:38 AM UTC
Outbound calling was restored at 9:26PM Eastern, and all monitoring/validation testing since that time has consistently shown recovered call processing behavior. In the event you're still experiencing an issue, please reach out to the Care Team!
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 07:44 PM UTC
- Resolved
- Oct 21, 2025, 01:18 AM UTC
- Duration
- 5h 34m
Affected: app.sharpencx.comapp.iz1.sharpen.cx
Timeline · 3 updates
-
identified Oct 20, 2025, 07:35 PM UTC
As part of the wide-ranging impact that various technical vendors are experiencing (as part of this Amazon Web Services disruption), the Sharpen team is tracking a variety of issues across our platform that involve: - Delayed interaction routing/connectivity behavior - Inability to place outbound calls - Web Chat functionality inconsistencies - SharpenDB querying or data-return issues - Missing or unresponsive interaction control buttons in the Queue interface Our teams are actively working to update the application, in order to address service dependencies or availability issues throughout the platform. We'll continue to update this tracking item as more zones of impact are identified.
-
identified Oct 20, 2025, 07:44 PM UTC
We are continuing our efforts to work through these issues - focusing on ways to avoid impacted AWS end-points/services. As certain features are restored to an operational status, we'll continue to update this tracking item.
-
resolved Oct 21, 2025, 01:18 AM UTC
This incident has been resolved as of 6:53 PM Eastern time upon the conclusion of the AWS incident. Our teams continue to monitor for any additional impact.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 01:40 PM UTC
- Resolved
- Oct 20, 2025, 07:41 PM UTC
- Duration
- 6h
Timeline · 4 updates
-
identified Oct 20, 2025, 01:40 PM UTC
Due to an outage with our cloud service provider, the SharpenDB end-point is experiencing degraded availability and is not able to consistently return data. Navigating to the Sharpen Admin --> config tab --> SharpenDB container may show a "Zero Tables Found" error, and various DB lookups (initiated through Classic Logic, Logic+, or through Query API) may not return any results. We've engaged with our cloud service provider and are working on restoring functionality for SharpenDB as quickly as possible. Updates will follow as additional details or restoration timelines are identified.
-
identified Oct 20, 2025, 04:14 PM UTC
Our cloud service provider (AWS) has isolated the source of the network connectivity/end-point misbehavior, and are actively working towards resolution. We don't yet have a recovery timeline to share, but will provide further status updates when stability returns to effected services.
-
monitoring Oct 20, 2025, 06:28 PM UTC
Our Development Team has performed an update to circumvent some of the dependencies/communication issues being experienced with our cloud services provider (AWS). We're performing validation testing for SharpenDB's access and querying capabilities, and are seeing a restoration in availability for that portion of the platform. Please test at your discretion, as we continue to make updates and improve platform stability.
-
resolved Oct 20, 2025, 07:41 PM UTC
This unique tracking items is being closed out, in preference of centrally tracking known areas of impact through a general tracking item (that ties back to the identified service interruption with cloud service provider AWS). Further updates on SharpenDB performance, API end-point engagement, and any other newly identified fault-zones will be communicated using our general tracking item hosted on the Status Page.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 12:43 PM UTC
- Resolved
- Oct 21, 2025, 01:11 AM UTC
- Duration
- 12h 27m
Affected: Service Desk PortalEmail RequestsNotifications
Timeline · 2 updates
-
investigating Oct 20, 2025, 12:43 PM UTC
Due to a outage with a cloud service provider, the Sharpen Service desk is experiencing reachability issues. The SharpenCare team is still reachable via phone or chat, however web tickets cannot be viewed or submitted. We are monitoring updates from our service provider for resolution.
-
resolved Oct 21, 2025, 01:11 AM UTC
This incident has been resolved with the resolution on the AWS outage at 6:53 PM Eastern Time. Our team has validated the restoration of this service.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2025, 05:53 PM UTC
- Resolved
- Oct 02, 2025, 02:46 PM UTC
- Duration
- 20h 53m
Affected: CX
Timeline · 9 updates
Read the full incident report →
Notice September 18, 2025 - Detected by Pingoru
- Sep 18, 2025, 03:55 AM UTC
- Resolved
- Sep 18, 2025, 06:12 AM UTC
- Duration
- 2h 16m
Timeline · 5 updates
-
investigating Sep 18, 2025, 03:51 AM UTC
Starting at approximately 9:30PM Eastern, calls routing through our IZ0 infrastructure that engage a transfer action (whether that be a queue-based "Max Wait" or "Exit No Agents" condition or an agent-initiated transfer to a different queue) are experiencing an unexpected termination. Test calls hitting one of these transfer conditions will hear a series of beeps, followed by the unexpected disconnect.
-
identified Sep 18, 2025, 03:55 AM UTC
We've identified a routing issue within our infrastructure that's uniquely tied to transfer functionality (both queue and agent-initiated) and are working towards a fix. All available resources have been engaged at this time, and we're actively working towards recovery as quickly as possible. Further updates will be made to the status page when we've reached a point of recovery.
-
identified Sep 18, 2025, 04:51 AM UTC
Our teams are currently working towards rolling out the hot-fix/update across Sharpen's infrastructure. As soon as that effort has been completed, we'll initiate validation testing and confirm recovery of the system. Further updates will be posted to the status page as soon as that task finishes.
-
monitoring Sep 18, 2025, 05:18 AM UTC
The corrective hot-fix has been deployed throughout our infrastructure, and initial validation testing has confirmed a restoration in queue-based and agent-initiated transfer functionality. Please verify with end-users if they're seeing a restoration in functionality. If ongoing impact is experienced, please reach out to the Care Team for further troubleshooting/analysis - with example users/extension info/QCMIDs that can be reviewed.
-
resolved Sep 18, 2025, 06:12 AM UTC
Continued validation testing and monitoring efforts have shown comprehensive recovery across the Sharpen Q system. This incident is being transitioned into a monitoring status. In the event that new misbehaviors or lingering symtoms/issues are encountered, please reach out to the Care Team.
Read the full incident report →
- Detected by Pingoru
- Aug 29, 2025, 03:27 PM UTC
- Resolved
- Aug 29, 2025, 03:57 PM UTC
- Duration
- 30m
Affected: Inbound Voice
Timeline · 3 updates
-
investigating Aug 29, 2025, 03:27 PM UTC
Inbound numbers that route through a Logic+ are resulting in dead-air. We are currently investigating and working towards a resolution
-
monitoring Aug 29, 2025, 03:40 PM UTC
We identified the root cause impacting inbound calls routed through Logic+ and have applied corrective measures. Calls are now completing successfully. We will continue to closely monitor the service to ensure full stability.
-
resolved Aug 29, 2025, 03:57 PM UTC
The issue with inbound calls routed through Logic+ has been fully resolved. All services are operating normally.
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 02:02 PM UTC
- Resolved
- Aug 25, 2025, 02:52 PM UTC
- Duration
- 50m
Affected: Inbound Voice
Timeline · 4 updates
-
investigating Aug 25, 2025, 02:02 PM UTC
Starting shortly after 09:00AM Eastern, Inbound numbers that route though a Logic+ configuration are intermittently resulting in a dead-air or delayed playback misbehavior.
-
investigating Aug 25, 2025, 02:07 PM UTC
We're aware of an ongoing/active issue, that is causing Inbound calls to experience dead-air or extremely delayed prompt playback - specifically when the number processes through a Logic+ configuration. We're investigating some infrastructure alerts that were triggered, and have all necessary team members engaged to troubleshoot the issue. We'll post further status updates as additional details become available.
-
identified Aug 25, 2025, 02:32 PM UTC
We've isolated the underlying issue within our infrastructure, and have taken initial steps to reroute traffic away from the misbehaving pathway causing the intermittent disconnects, delayed prompt playback, or dead-air. Our internal teams are actively preparing a code-change to completely address the problem, and we expect to have that pushed out to our Production systems in the next few minutes.
-
resolved Aug 25, 2025, 02:52 PM UTC
Our IZ1 infrastructure update has been deployed to the Production system, and initial validation efforts have shown full recovery to previously impacted call-flows routing though Logic+. In the event that you're still experiencing symptoms tied to dead-air, latent prompt playback, or unexpected disconnects through a Logic+ bot, please reach out to the Care Team with examples of the misbehavior and we'll troubleshoot further!
Read the full incident report →
- Detected by Pingoru
- Aug 23, 2025, 06:38 PM UTC
- Resolved
- Aug 23, 2025, 07:16 PM UTC
- Duration
- 38m
Affected: Sharpen QOutbound Voice
Timeline · 3 updates
-
investigating Aug 23, 2025, 06:38 PM UTC
We are currently investigating an issue impacting the inability to place outbound calls in our IZ1 infrastructure.
-
monitoring Aug 23, 2025, 07:05 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 23, 2025, 07:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 23, 2025, 05:37 PM UTC
- Resolved
- Aug 23, 2025, 06:14 PM UTC
- Duration
- 37m
Affected: app.iz1.sharpen.cx
Timeline · 4 updates
-
investigating Aug 23, 2025, 05:37 PM UTC
We are aware of a potential service disruption impacting our IZ1 Infrastructure that may result in inbound calls not reaching queues. We have all necessary resources engaged to restore service. Additional details will be provided soon.
-
identified Aug 23, 2025, 05:53 PM UTC
We have identified the cause and are working on a corrective fix.
-
monitoring Aug 23, 2025, 06:02 PM UTC
We have corrected the issue impacting IZ1 application availability and are continuing to monitor.
-
resolved Aug 23, 2025, 06:14 PM UTC
This incident has been resolved. Any agents experiencing lingering impact may need to log out of app.iz1.sharpen.cx and log back in.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 09:41 PM UTC
- Resolved
- Aug 06, 2025, 11:05 PM UTC
- Duration
- 1h 23m
Affected: Sharpen QInbound VoiceOutbound Voice
Timeline · 5 updates
-
investigating Aug 06, 2025, 09:41 PM UTC
Some users in the IZ0 isolation zone (app.sharpencx.com) are unable to establish a Sharpen Q phone connection. We have all necessary resources engaged and are working to resolve the issue as soon as possible. If you are experiencing this issue, leveraging an alternative audio endpoint such as a configured IP phone or mobile phone may be a sufficient workaround.
-
investigating Aug 06, 2025, 09:57 PM UTC
We are continuing to investigate this issue. We have confirmed this is not impacting all users, but is most present for newly logged in users. All necessary team members continue to be engaged until resolution is achieved.
-
identified Aug 06, 2025, 10:30 PM UTC
We have identified the fault zone and are working on corrective actions. This continues to be isolated to only new connections. If your users have existing connections, refreshing the browser or logging out and back in will cause the agent to experience this issue.
-
monitoring Aug 06, 2025, 10:57 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Aug 06, 2025, 11:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2025, 11:53 AM UTC
- Resolved
- Jul 10, 2025, 12:12 PM UTC
- Duration
- 18m
Affected: app.iz1.sharpen.cxSharpen Q
Timeline · 3 updates
-
investigating Jul 10, 2025, 11:53 AM UTC
Users of the Sharpen Q application in our IZ1 isolation zone (app.iz1.sharpen.cx) may be experiencing moderate to severe delays in the application. We have all necessary resources engaged to identify and resolve the issue as soon as possible.
-
monitoring Jul 10, 2025, 12:06 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 10, 2025, 12:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 03:10 PM UTC
- Resolved
- Jun 27, 2025, 04:41 PM UTC
- Duration
- 1h 31m
Affected: app.sharpencx.comapp.iz1.sharpen.cx
Timeline · 4 updates
-
investigating Jun 27, 2025, 03:10 PM UTC
We're aware are of an issue, where certain Inbound Routes are encountering a mapping issue with Logic+. Inbound calls to an impacted number may experience an unexpected disconnect. We're actively troubleshooting the issue and will post additional information to the status page as more details become available.
-
identified Jun 27, 2025, 04:17 PM UTC
We've identified an infrastructure discrepancy, where Inbound call-routing servers are not able to properly reference/interact with the Logic+ service end-point. We're taking steps to correct this issue via a hot-fix, and will perform validation testing shortly after (to confirm previously non-working Inbound routes have their service restored).
-
identified Jun 27, 2025, 04:30 PM UTC
The hot-fix corrective action has been pushed to our IZ1 infrastructure, and validation test calls have confirmed in-place recovery. Previously impacted routes should now be routing as expected. We're in the process of pushing the same hot-fix to IZ0 now.
-
resolved Jun 27, 2025, 04:41 PM UTC
This issue has now been fully resolved as of 12:32PM Eastern for IZ0 (resolved at 12:28PM Eastern for IZ1). Validation test calls have confirmed that Inbound routes engaging Logic+ are fully operational. We're continuing to monitor the system. Please engage the Care Team if you're seeing any lingering misbehavior associated to Inbound Logic+ routing.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2025, 03:19 PM UTC
- Resolved
- Jun 17, 2025, 05:18 PM UTC
- Duration
- 1h 59m
Affected: app.iz1.sharpen.cxAPISharpen Q
Timeline · 5 updates
-
investigating Jun 17, 2025, 03:19 PM UTC
Users of the Sharpen Q platform in IZ (app.iz1.sharpen.cx) may be experiencing slowness, disrupting the successful execution of Sharpen Q functions. We have all necessary subject matter experts engaged to resolve the issue as soon as possible.
-
investigating Jun 17, 2025, 03:34 PM UTC
We have isolated the fault zone and are organizing next steps to correct the issue.
-
monitoring Jun 17, 2025, 03:54 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 17, 2025, 05:02 PM UTC
We are continuing to monitor recovery. We have seen recovery for for most organizations at this point, and are continuing to investigate remaining symptoms for those who are still experiencing impact.
-
resolved Jun 17, 2025, 05:18 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2025, 01:22 PM UTC
- Resolved
- Jun 17, 2025, 03:15 PM UTC
- Duration
- 1h 53m
Affected: Dashboards
Timeline · 3 updates
-
investigating Jun 17, 2025, 01:22 PM UTC
We are currently investigating an incident preventing public dashboard (https://dashboard.iz1.sharpen.cx/...) pages from rendering correctly in our IZ1 isolate zone. Attempts to load the page are resulting in a blank white screen. If you are experiencing this issue, dashboards can still be accessed via the authenticated dashboard editor (https://app.iz1.sharpen.cx/dashboardBuilder/ in insights. We have all necessary resources engaged and are working to restore this service as soon as possible.
-
investigating Jun 17, 2025, 02:28 PM UTC
Our Dev Team has identified the underlying issue; which is causing resource directories to not be referenced properly for the Insights application (impacting Public dashboard URLs, the editor interface, etc). We're in the process of performing a hot-fix to restore functionality. Additional information will be shared as soon as recovery has been established.
-
resolved Jun 17, 2025, 03:15 PM UTC
We've corrected the resource referencing issue in Insights for IZ1 customers. All validation efforts are now showing that the editor interface, Public dashboard links, agent vues, etc work as expected. We're monitoring the situation and running additional tests, but all services within Insights have been restored at this time.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2025, 11:28 AM UTC
- Resolved
- Jun 13, 2025, 11:52 AM UTC
- Duration
- 23m
Affected: Insights
Timeline · 2 updates
-
investigating Jun 13, 2025, 11:28 AM UTC
We are currently investigating an issue where Insights Dashboards are loading as a white screen in our IZ0 Isolation Zone. Customers accessing dashboards through direct links may encounter a blank white screen and fail to load. Our team is actively working to resolve the issue.
-
resolved Jun 13, 2025, 11:52 AM UTC
The impact to Insights Dashboards rendering a white screen in IZ0 has been resolved. A refresh of any impacted dashboard will be necessary to restore functionality.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2025, 03:19 PM UTC
- Resolved
- Jun 03, 2025, 05:11 PM UTC
- Duration
- 1h 52m
Affected: app.iz1.sharpen.cxSharpen Q
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- May 30, 2025, 07:25 PM UTC
- Resolved
- May 30, 2025, 08:03 PM UTC
- Duration
- 38m
Timeline · 4 updates
-
investigating May 30, 2025, 07:25 PM UTC
We are currently investigating an issue impacting inbound call handling in the IZ1 region. Callers may experience intermittent delays connecting or experience a busy signal.
-
identified May 30, 2025, 07:45 PM UTC
Initial efforts have led to a recovery in busy signals for inbound calls in the IZ1 region. However, a smaller percentage of calls may still experience intermittent delays when connecting. Our team is still diligently working to correct the issue.
-
monitoring May 30, 2025, 07:48 PM UTC
Inbound call handling in the IZ1 region has recovered, and normal service has resumed. We are continuing to monitor the platform to ensure continued stability. No further impact is expected at this time.
-
resolved May 30, 2025, 08:03 PM UTC
The issue impacting inbound call handling in the IZ1 region has been fully resolved. Call traffic is operating normally, and no further disruptions are expected. Thank you for your patience while we worked to restore service.
Read the full incident report →