Is SharpenCX down?
Last checked 7m agoNo incidents right now.
SharpenCX is operational right now. Last checked 7m ago; the most recent incident resolved 46d ago.
Real-time SharpenCX status, recent outages, and incident history — pulled directly from SharpenCX's official status page at https://status.sharpencx.com every 5 minutes. Pingoru tracks 39 SharpenCX services and has captured 3 incidents in the last 90 days (99.86% uptime). Get email, Slack, Discord, or webhook alerts the moment SharpenCX reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Sharpen Q
Timeline · 3 updates
- investigating · Aug 03, 2026, 06:09 PM UTC
We are currently investigating an issue with SharpenQ in the IZ1 isolation zone causing performance degradation. Long call connection lengths and one way audio may be experienced.
- monitoring · Aug 03, 2026, 07:30 PM UTC
A fix has been implemented and we are currently monitoring the performance of SharpenQ.
- resolved · Aug 03, 2026, 07:52 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- app.iz1.sharpen.cxInbound Voice
Timeline · 3 updates
- investigating · Jul 22, 2026, 10:30 PM UTC
We're currently investigating an issue affecting inbound calling in the IZ1 environment. Some customers may experience failed or dropped inbound calls during this time. Our team is actively working to identify the root cause. We'll post an update as soon as we have more information.
- monitoring · Jul 22, 2026, 11:01 PM UTC
We've identified the issue affecting inbound calls to Classic Logic on IZ1 and applied a fix. Calls should be working again, and we're continuing to monitor to confirm full stability.
- resolved · Jul 22, 2026, 11:10 PM UTC
Inbound calls routed to Classic Logic on IZ1 saw dead silence starting around 5:42 PM ET. Our team traced this to a database performance issue affecting voice processing and had it fixed by 6:56 PM ET. Calls are back to normal now.
Latest: Inbound calls routed to Classic Logic on IZ1 saw dead silence starting around 5:42 PM ET. Our team traced this to a database performance issue affecting voice processing and had it…
-
- Sharpen QOutbound Voice
Timeline · 4 updates
- investigating · Jul 10, 2026, 06:21 PM UTC
We are currently aware of an issue in our IZ1 isolation zone affecting Sharpen Q performance, including delays in call connection, audio quality impact, and delays with Outbound Calls connecting. Our team is actively investigating and working toward a resolution.
- identified · Jul 10, 2026, 07:21 PM UTC
We believe we have identified the issue impacting SharpenQ performance in IZ1 and are implementing a fix.
- monitoring · Jul 10, 2026, 07:39 PM UTC
A fix has been implemented and we are observing Sharpen Q performance improvement for call quality and outbound call delays. We are continuing to monitor for ongoing stability.
- resolved · Jul 10, 2026, 08:49 PM UTC
We've continued to see platform stability/recovery improve since our engineering teams implemented a fix action. Outbound calling capabilities, queue performance, call quality, etc have all restored to baseline levels of functionality. In the event that you're continuing to see impact with certain queues, end-users, or specific actions within the Sharpen application suite - please reach out to our Care Team via your existing support case.
Latest: We've continued to see platform stability/recovery improve since our engineering teams implemented a fix action. Outbound calling capabilities, queue performance, call quality, etc…
-
- IZ1 SharpenQ Incident ResolvedStarted Aug 03, 2026, 06:09 PM UTC · Resolved Aug 03, 2026, 07:52 PM UTC · 1h 42m
- Started Jul 22, 2026, 10:30 PM UTC · Resolved Jul 22, 2026, 11:10 PM UTC · 40m
- IZ1 SharpenQ Incident ResolvedStarted Jul 10, 2026, 06:21 PM UTC · Resolved Jul 10, 2026, 08:49 PM UTC · 2h 27m