Loss Of Registration and Dropped Calls PHX
Affected
Operational from 7:29 PM to 7:31 PM
Operational from 7:29 PM to 7:31 PM
- Resolved · UTC
What Occurred: On April 15th, 2026 at 1:26 PM ET, our monitoring tools notified us of failed HTTPS and SIP health on our core2-phx.ucaas.network core. This resulted in devices re-registering to other cores and all active calls on PHX dropping.
What Is Affected: Inbound/Outbound calling, and device registration on PHX.
When It began: April 15th, 2026 at 1:26 PM ET
Current Status: After working with upstream vendor support, we've determined that this was caused by a component of PHX's underlying infrastructure experiencing a failure, causing the hypervisor that hosts PHX to enter an unhealthy state. To mitigate the impact, a reboot migration was performed to move PHX onto healthy infrastructure. PHX has remained stable since this reboot.
Next Steps: This incident is now considered resolved. The major incident report will be available within the next 3 business days.
We appreciate your patience throughout this process. If you need support, please contact support@oit.co. For more real time status updates as well as discussion please join our Discord (Not official support).
- Monitoring · UTC
What Occurred: At 1:26 PM ET, our monitoring tools notified us of failed HTTPS and SIP health on our core2-phx.ucaas.network core. This resulted in devices re-registering to other cores and all active calls on PHX dropping.
What Is Affected: Inbound/Outbound calling, and device registration on PHX.
When It began: April 15th, 2026 at 1:26 PM ET
Current Status: As of 1:29 PM ET, systems have stabilized, and have since remained operational.
Next Steps: We're currently investigating the root cause with upstream vendor support.
Next Update: April 16th, 2026 at 3:30 PM ET
We appreciate your patience throughout this process. If you need support, please contact support@oit.co. For more real time status updates as well as discussion please join our Discord (Not official support).