SharpenCX Outage History

SharpenCX is up right now

SharpenCX had 43 outages in the last 2 years totaling 41h 3m of downtime — averaging 1.8 incidents per month.

There were 43 SharpenCX outages since August 12, 2024 totaling 41h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sharpencx.com

Major May 14, 2025

IZ1 Intermittent dropped Sharpen Q calls delivered from Logic+ IVR

Detected by Pingoru
May 14, 2025, 03:11 PM UTC
Resolved
May 14, 2025, 06:09 PM UTC
Duration
2h 58m
Affected: Sharpen QInbound Voice
Timeline · 4 updates
  1. investigating May 14, 2025, 03:11 PM UTC

    We are currently investigating an issue that's causing between 30 and 45% of inbound calls to be dropped if they have been transferred to Sharpen Q from a Logic+ IVR. All necessary resources are engaged to identify and resolve this issue.

  2. investigating May 14, 2025, 03:33 PM UTC

    This has been isolated to a very small set of customers. The majority of users are not impacted by this incident. We continue our investigation to identify and correct this issue.

  3. monitoring May 14, 2025, 04:52 PM UTC

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

  4. resolved May 14, 2025, 06:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 8, 2025

Reporting and Insights Unavailable in IZ0

Detected by Pingoru
May 08, 2025, 06:03 AM UTC
Resolved
May 08, 2025, 11:25 AM UTC
Duration
5h 22m
Affected: DashboardsInsights
Timeline · 2 updates
  1. investigating May 08, 2025, 06:03 AM UTC

    We're currently investigating an issue affecting customers in IZ0 where the Insights page and dashboards are not loading as expected. Users may see partial content or a blank screen when accessing these features.

  2. resolved May 08, 2025, 11:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 10, 2025

Intermittent Dead Air (IZ1)

Detected by Pingoru
Apr 10, 2025, 01:34 PM UTC
Resolved
Apr 10, 2025, 02:05 PM UTC
Duration
30m
Affected: Inbound Voice
Timeline · 3 updates
  1. identified Apr 10, 2025, 01:34 PM UTC

    Callers to the platform of IZ1 customers (those logging into app.iz1.sharpen.cx) may be experiencing dead air or disconnected calls when calling. This may be impacting up to 70% of calls, but is quite intermittent in its impact. We have all necessary resources engaged to resolve the issue and are working on a corrective action to deploy as soon as possible.

  2. monitoring Apr 10, 2025, 01:57 PM UTC

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

  3. resolved Apr 10, 2025, 02:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 9, 2025

Intermittent dead air calls (IZ1)

Detected by Pingoru
Apr 09, 2025, 03:59 PM UTC
Resolved
Apr 09, 2025, 04:40 PM UTC
Duration
41m
Affected: Inbound Voice
Timeline · 5 updates
  1. identified Apr 09, 2025, 03:59 PM UTC

    Customer in IZ1 (app.iz1.sharpencx.com) may be experiencing intermittent disruption to inbound calls

  2. identified Apr 09, 2025, 04:07 PM UTC

    We have identified the fault zone for this issue and are working through remediation options to restore service as soon as possible.

  3. identified Apr 09, 2025, 04:19 PM UTC

    We have identified the source of the problem and are finalizing our corrective actions plans. We're targeting resolution within the next 15 minutes.

  4. monitoring Apr 09, 2025, 04:27 PM UTC

    We are seeing initial signs of recovery, and are closely monitoring.

  5. resolved Apr 09, 2025, 04:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 3, 2025

Sharpen Q Caller ID Disruption

Detected by Pingoru
Mar 03, 2025, 03:05 PM UTC
Resolved
Mar 03, 2025, 05:55 PM UTC
Duration
2h 49m
Affected: Sharpen QSharpen QInbound VoiceOutbound Voice
Timeline · 2 updates
  1. investigating Mar 03, 2025, 03:05 PM UTC

    We’ve detected a partial disruption to caller ID name lookups in Sharpen Q. Some users might see "Unknown Caller" displayed for the caller ID name on certain incoming voice calls. We’ve pinpointed the problem to our supporting callerID lookup provider and are actively working to fix it as quickly as possible. Though some caller ID names are missing, calls are still routing normally and displaying the correct caller ID number.

  2. resolved Mar 03, 2025, 05:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 28, 2025

IZ1 Inbound Logic+ IVR transfer to queue disruption

Detected by Pingoru
Feb 28, 2025, 05:28 PM UTC
Resolved
Feb 28, 2025, 05:40 PM UTC
Duration
12m
Affected: Inbound Voice
Timeline · 3 updates
  1. identified Feb 28, 2025, 05:28 PM UTC

    An issue has been identified that is blocking certain incoming IVR calls processed through Logic+ from successfully connecting to agents in Sharpen Q. We have all necessary resources engaged to restore service.

  2. monitoring Feb 28, 2025, 05:36 PM UTC

    We have implemented a fix and are assessing recovery.

  3. resolved Feb 28, 2025, 05:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 6, 2025

Sharpen Q Disruption (IZ0)

Detected by Pingoru
Jan 06, 2025, 01:21 PM UTC
Resolved
Jan 06, 2025, 01:51 PM UTC
Duration
29m
Affected: Sharpen Q
Timeline · 4 updates
  1. investigating Jan 06, 2025, 01:21 PM UTC

    We are aware of an issue impacting Sharpen Q operations in our IZ0 isolation zone. We have all resources engaged to resolve the issue as soon as possible.

  2. identified Jan 06, 2025, 01:30 PM UTC

    We have identified the source of the issue and have implemented corrective actions. We're assessing the results of the change and will notify once resolution has been confirmed.

  3. monitoring Jan 06, 2025, 01:34 PM UTC

    The fix has been confirmed. All systems look stable. We will continue to monitor for 15 minutes and then mark this item as resolved.

  4. resolved Jan 06, 2025, 01:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 19, 2024

Sharpen Database Availability Issue - IZ1 - 19DEC24

Detected by Pingoru
Dec 19, 2024, 03:04 PM UTC
Resolved
Dec 19, 2024, 06:47 PM UTC
Duration
3h 42m
Affected: Inbound Voice
Timeline · 5 updates
  1. identified Dec 19, 2024, 03:04 PM UTC

    We are currently investigating an issue where Call Flows using SharpenDB2 for data dips are failing, resulting in inbound interaction failures or routing misbehavior. We have identified the issue and are working with our vendor to resolve.

  2. identified Dec 19, 2024, 05:02 PM UTC

    Corrective actions/efforts are still underway with our vendor (AWS) -- where the underlying database communication issue has been identified. We'll proceed with validation efforts and post further updates to this status page, as soon as restoration has been achieved.

  3. identified Dec 19, 2024, 05:53 PM UTC

    In collaboration with AWS we have identified a path to resolution. We expect resolution within 4 hours and will be providing hourly updates as we progress.

  4. monitoring Dec 19, 2024, 06:32 PM UTC

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

  5. resolved Dec 19, 2024, 06:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 10, 2024

IZ0 Application Delays and Connection Issues - 10DEC24

Detected by Pingoru
Dec 10, 2024, 07:54 PM UTC
Resolved
Dec 10, 2024, 09:20 PM UTC
Duration
1h 25m
Affected: app.sharpencx.comSharpen Q
Timeline · 3 updates
  1. investigating Dec 10, 2024, 07:54 PM UTC

    We're aware of an issue for customers hosted within our IZ0 infrastructure - where app behavior is significantly delayed/unresponsive. Symptoms range from seeing a "Connecting..." overlay appear in the Sharpen Q application, to being unable to answer interactions in a timely fashion. End users may also be experiencing problems with modifying their status or logging in/out of the application. We have all technical resources engaged at this time and are actively troubleshooting the issue.

  2. monitoring Dec 10, 2024, 08:13 PM UTC

    We've identified an error trend within our infrastructure, and our Development Team has taken initial steps to correct the misbehavior. Our initial validation tests show a return to app responsiveness (being able to make/take calls, change statuses, etc). We're continuing to monitor our infrastructure for any indicators or error trends. Please reach out to the Care Team if you're seeing signs of sustained disruption.

  3. resolved Dec 10, 2024, 09:20 PM UTC

    Recovery from this misbehavior was established at approximately 3:00PM Eastern, and we have not encountered any further responsiveness/delay issues across the application. Service has been fully restored, but we'll continue to monitor the situation. Please reach out to the Care Team in the event you have end users that are still encountering lingering symptoms.

Read the full incident report →

Major November 21, 2024

IZ1 users (app.iz1.sharpen.cx) unable to login

Detected by Pingoru
Nov 21, 2024, 02:14 PM UTC
Resolved
Nov 21, 2024, 03:03 PM UTC
Duration
49m
Affected: app.iz1.sharpen.cx
Timeline · 4 updates
  1. identified Nov 21, 2024, 02:14 PM UTC

    We are aware of an issue in IZ1 (app.iz1.sharpen.cx) preventing users from being able to login. All resources are engaged and are working to restore service as soon as possible.

  2. identified Nov 21, 2024, 02:20 PM UTC

    We have isolated the issue and can confirm that users are intermittently able to access app.iz1.sharpen.cx, but some are still experiencing failure. We have all necessary resources engaged and will continue to work for the earliest possible service recovery.

  3. monitoring Nov 21, 2024, 02:34 PM UTC

    We are observing recovery as of 9:30 AM EST. We are continuing to monitor and identify the specific cause.

  4. resolved Nov 21, 2024, 03:03 PM UTC

    We continue to see sustained recovery. This incident is resolved. Thank you for your patience.

Read the full incident report →

Minor November 13, 2024

Insights Application Not Loading - Blank Screen

Detected by Pingoru
Nov 13, 2024, 06:54 AM UTC
Resolved
Nov 13, 2024, 08:30 AM UTC
Duration
1h 35m
Affected: InsightsInsights
Timeline · 3 updates
  1. investigating Nov 13, 2024, 06:54 AM UTC

    We're aware of an ongoing issue with the Sharpen Insights application suite - where navigating in-app, loading a saved Dashboard link, etc results in a blank white screen for all users. The issue has been reproduced by our Care Team in both IZ0 and IZ1 portions of our infrastructure. We're working to identify the underlying issue, and will share additional details as more information becomes available.

  2. identified Nov 13, 2024, 07:45 AM UTC

    We've identified the underlying issue that is causing the reporting end-point to be unresponsive/only load a blank page in the application. We're in the process of getting things corrected and will share another update when there is full restoration to Insights.

  3. resolved Nov 13, 2024, 08:30 AM UTC

    The underlying issue has been resolved for Insights, and the Care Team has verified all reports/dashboards/agent vues are loading at this time in IZ0 and IZ1.

Read the full incident report →

Minor November 7, 2024

Service Interruption - Sharpen Application Suite (IZ1)

Detected by Pingoru
Nov 07, 2024, 05:56 PM UTC
Resolved
Nov 07, 2024, 06:27 PM UTC
Duration
30m
Affected: app.iz1.sharpen.cxAPICXSharpen QDashboardsInsightsSIP RegistrationInbound Voice
Timeline · 3 updates
  1. investigating Nov 07, 2024, 05:56 PM UTC

    At approximately 12:45PM Eastern, our infrastructure team received an alert tied to Database availability. Services have automatically failed over to our backup infrastructure, and we're actively investigating the underlying cause - while performing additional process/app validations.

  2. monitoring Nov 07, 2024, 06:08 PM UTC

    Our Dev Team verified that all services auto-recovered after the database failover completed - and that full service availability has returned to the application. Any users experiencing continued symptoms with inbound call handling/alerting or outbound calling difficulty should log out and back into the application. Please reach out to the Care Team if continued impact is encountered. We're actively monitoring our infrastructure at this time, and have engaged with Amazon Web Services to identify root-cause of the availability/restart issue.

  3. resolved Nov 07, 2024, 06:27 PM UTC

    Transitioning to a resolved status, as all systems are back up and running - and we have full redundancy restored at the infrastructure level. A root-cause analysis report is being compiled at this time by our Development/Operations resources and the vendor (AWS), and will be sent out via cases that were opened with the Care Team when it is finalized.

Read the full incident report →

Minor November 6, 2024

Application Login Slowness - IZ1

Detected by Pingoru
Nov 06, 2024, 01:52 PM UTC
Resolved
Nov 06, 2024, 02:00 PM UTC
Duration
8m
Affected: app.iz1.sharpen.cx
Timeline · 2 updates
  1. investigating Nov 06, 2024, 01:52 PM UTC

    Customers running within our IZ1 infrastructure may notice delays with getting logged into the application. Upon navigating to app.iz1.sharpen.cx, it is taking upwards of 30 seconds for a login attempt to complete. Users may also experience delays with navigating between pages/toolsets in the Admin application.

  2. resolved Nov 06, 2024, 02:00 PM UTC

    The underlying issue within our Infrastructure was identified and corrected. Login behavior is back to a fully operational status. If any users are still encountering problems at this time - have them fully log out of the application, then log back in (to force their browser session to pull an updated session configuration).

Read the full incident report →

Minor October 29, 2024

Sharpen Service Desk Interruption

Detected by Pingoru
Oct 29, 2024, 06:23 PM UTC
Resolved
Oct 29, 2024, 06:23 PM UTC
Duration
Affected: Email Requests
Timeline · 1 update
  1. resolved Oct 29, 2024, 06:23 PM UTC

    Working with our Service Desk vendor (JIRA), the Care Team discovered that our "[email protected]" inbox monitoring entered a degraded state on 18OCT24. The underlying issue has been resolved as of 2:05PM Eastern on 29OCT24. If you had submitted a new service request or responded to an existing incident via to the "[email protected]" inbox between those dates, your message was unable to trigger the necessary automation for support case generation and updates to have been received. Please reach out to us in the event you are still experiencing any misbehavior associated to use of the Sharpen product suite or are having difficulty getting in contact with our Care Team!

Read the full incident report →

Major September 14, 2024

Reports of agents in IZ1 isolation zone unable to place outbound calls

Detected by Pingoru
Sep 14, 2024, 02:03 PM UTC
Resolved
Sep 14, 2024, 03:44 PM UTC
Duration
1h 40m
Affected: Sharpen QVirginiaOutbound Voice
Timeline · 5 updates
  1. investigating Sep 14, 2024, 02:03 PM UTC

    We have received reports of agents being unable to place outbound calls from the IZ1 isolation zone. We are investigating and will post updates here as more information is available.

  2. investigating Sep 14, 2024, 02:24 PM UTC

    We continue to investigate this behavior with our internal development and infrastructure teams. Once an update is available we will post it here.

  3. investigating Sep 14, 2024, 02:48 PM UTC

    We continue to narrow down on the issue internally and hope to have an update shortly.

  4. investigating Sep 14, 2024, 03:27 PM UTC

    Thank you for your patience as we work through this impacting event. Investigation continues into the cause of the behavior. You may see different unexpected behaviors with Sharpen Q as we work through mitigating efforts to resolve the issue.

  5. resolved Sep 14, 2024, 03:44 PM UTC

    We've identified the issue and have corrected it. This incident has been resolved.

Read the full incident report →

Notice August 28, 2024

IZ1 Service Disruption

Detected by Pingoru
Aug 28, 2024, 08:24 PM UTC
Resolved
Aug 28, 2024, 09:04 PM UTC
Duration
39m
Affected: app.iz1.sharpen.cxSharpen Q
Timeline · 6 updates
  1. investigating Aug 28, 2024, 08:24 PM UTC

    We are aware of a potential service disruption in our IZ1 isolation zone. We have all necessary resources engaged to restore service. Additional details will be provided soon.

  2. investigating Aug 28, 2024, 08:31 PM UTC

    Users of the Sharpen Q platform within our IZ1 isolation zone (app.iz1.sharpen.cx) may have experienced intermittent degradation starting at 4:22 PM EDT. All necessary resources are engaged and working to fully restore service as soon as possible

  3. monitoring Aug 28, 2024, 08:37 PM UTC

    We have identified the fault as an underlying AWS service crash. Recovery was automatically established, and we are monitoring for sustained recovery.

  4. identified Aug 28, 2024, 08:39 PM UTC

    We have identified there are still some lingering interruptions to functions such as hanging up calls. Our team continues to employ corrective actions to restore service as soon as possible.

  5. monitoring Aug 28, 2024, 08:49 PM UTC

    All corrective actions have been implemented and we are observing recovery. We will continue to monitor for the next 15 minutes.

  6. resolved Aug 28, 2024, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2024

"Unknown Caller" Caller ID name

Detected by Pingoru
Aug 12, 2024, 07:27 PM UTC
Resolved
Aug 13, 2024, 01:27 AM UTC
Duration
6h
Affected: Sharpen QSharpen Q
Timeline · 4 updates
  1. investigating Aug 12, 2024, 07:27 PM UTC

    We are aware of an issue impacting caller ID names displaying as "Unknown Caller". This is an expected fallback for a name lookup failure with our carrier. We are currently working with our vendor to resolve.

  2. identified Aug 12, 2024, 07:50 PM UTC

    Our vendor has identified the cause of this incident and is working towards a resolution.

  3. monitoring Aug 12, 2024, 09:14 PM UTC

    Our vendor has implemented a resolution and is currently monitoring results.

  4. resolved Aug 13, 2024, 01:27 AM UTC

    Since 3:39 PM EDT, we have observed about 90% recovery from our CNAM carrier, resulting in a small amount experiencing the original "Unknown caller" symptom. We extended the monitoring period in anticipation of 100% recovery within normal business hours, but it has not yet been observed. We continue to request updates from our carrier in effort to expedite full resolution. Since the observed impact is now below our Severity 4 impact levels, we are resolving this notification and resuming updates with individually impacted customers. Should you have continued concerns regarding this impact, open a support request at support.sharpencx.com

Read the full incident report →