IZ0 - Sharpen Q Outbound Calling Incident
This incident has been resolved.
Home
/
Status
/
Service
AI-powered cloud contact center software for seamless customer interactions.
Source
auto
Category
AI
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 26m ago
44
Components
0
Active incidents
0
Maintenance
33.33%
90d uptime
IZ0 - Sharpen Q Outbound Calling Incident
Jun 2, 11:20 AM
Normalized official status-page data for incidents, maintenance, components, and history.
33.33%
Known uptime
3 known history days
44
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
AI
Operational
AI
Operational
API
Operational
API
Operational
CX
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
2
outage days
0
maintenance days
87
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
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!
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.
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.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved. Both IZ0 and IZ1 are working as expected.
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!
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.
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.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Sharpencx status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.sharpencx.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 44 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Isolation Zone 0 | Operational | Group | Not recorded |
Isolation Zone 1 | Operational | Group | Not recorded |
Points of Delivery A POD, or a Point of Delivery contains the fullness of the Sharpen application to deliver in a specific region. | Operational | Group | Not recorded |
Points of Presence A POP or Point of Presence is a regionalized voice environment that allows for lower voice latency and a localized presence. This contains components, but not the entirety of the Sharpen application like a POD (Point of Delivery) | Operational | Group | Not recorded |
SharpenCare Service Desk | Operational | Group | Not recorded |
Oregon | Operational | Component | Not recorded |
Service Desk Portal Web application used for submitting SharpenCare requests, viewing historical requests, and interacting with active requests. | Operational | Component | Not recorded |
Virginia | Operational | Component | Not recorded |
app.iz1.sharpen.cx Front end application for isolation zone 1 | Operational | Component | Not recorded |
app.sharpencx.com | Operational | Component | Not recorded |
API | Operational | Component | Not recorded |
API | Operational | Component | Not recorded |
Email Requests Channel for submitting requests via email to support@sharpencx.com | Operational | Component | Not recorded |
Ireland | Operational | Component | Not recorded |
CX | Operational | Component | Not recorded |
CX | Operational | Component | Not recorded |
Notifications Email notifications sent from the SharpenCare service desk to the primary contact and request participants' email address. | Operational | Component | Not recorded |
Sharpen Q | Operational | Component | Not recorded |
Sharpen Q | Operational | Component | Not recorded |
Singapore | Operational | Component | Not recorded |
Dashboards | Operational | Component | Not recorded |
Dashboards | Operational | Component | Not recorded |
Sydney | Operational | Component | Not recorded |
Insights | Operational | Component | Not recorded |
Insights Sharpen reporting engine and dashboards | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Sharpencx is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.