UCaaS Status Page - Notice history

Major Incident Report: https://voipdocs.io/announcements/-20260610-native-fax-inbound-and-outbound-failures-resolved

What Occurred: At approximately 12:00 PM ET on June 11th, 2026, we received new reports of Inbound and Outbound faxes failing for Native fax users.

What Was Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on June 10th, 2026.

• New reports at 12:00 PM ET on June 11th, 2026.

Current Status:

• 48 hours of monitoring showed no additional failures.

• This incident is considered resolved.

Next Steps:

• A Major Incident Report will be released within 24 business hours.

What Occurred: At approximately 12:00 PM ET on June 11th, 2026, we received new reports of Inbound and Outbound faxes failing for Native Fax users.

What Was Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on June 10th, 2026.

• New reports at 12:00 PM ET on June 11th, 2026.

Current Status:

• After identifying the root source of the blocked calls, a patch was successfully applied at 11:35 PM ET on June 11th, 2026.

• 12 hours of monitoring showed no additional failures.

Next Steps:

• We will continue to monitor for the next 24 hours.

• A Major Incident Report will be released within 72 business hours.

What is Affected: Native Fax

Current Status: Monitoring

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status: Monitoring

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine cause and resolution

• Several patches and configuration changes have been made

• Vendor found the source of the blocked calls and are working to resolve it

• Root cause has been determined, and we are seeing successful faxes in and out. The MI is not marked as resolved yet because more patches still need to be applied. Until that's done, inbound/outbound faxes will only work intermittently.

• We continue to work with the vendor to establish service

• Several version updates have failed. We are attempting alternate solutions.

• We are standing up a separate server for the failing services. Building now.

• We applied a successful patch to the port server at 7:55 PM ET

• All testing was successful

• Inbound and outbound faxes are now working

• Any fax forwarding that was previously requested will be removed and returned to their previous configurations

Next Steps:

• We will continue to monitor for the next 48 hours before declaring resolved

• Updates will be sent every 24 hours

Next Update

• 11:00 AM ET

Offline Services:

• None

Degraded Services:

• None

Operational Services:

• All systems

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine cause and resolution

• Several patches and configuration changes have been made

• Vendor found source of the blocked calls and are working to resolve it

• Root cause has been determined and we are seeing successful faxes in and out. The MI is not marked as resolved yet because there are still more patches to be applied. Until that's done inbound/outbound faxes will only work intermittently.

• Several version updates have failed. We are attempting alternate solutions.

• We continue to work with the vendor to establish service

• We are standing up a separate server for the failing services. Building now

Next Steps:

• Monitor for updates

• We can forward most inbound calls to your fax number to an alternate destination. We do not currently have any workarounds for Outbound. If you wish to forward your fax number, please submit a case with your fax number and the number you want it forwarded to.

Next Update

• 8:30 PM ET

Offline Services:

• NativeFax

Degraded Services:

• None

Operational Services:

• All other systems

What Occurred: Inbound and outbound faxes failing (Working on Resolution)

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine cause and resolution

• Several patches and configuration changes have been made

• Vendor found source of the blocked calls and are working to resolve it

• Root cause has been determined and we are seeing successful faxes in and out. The MI is not marked as resolved yet because there are still more patches to be applied. Until that's done inbound/outbound faxes will only work intermittently.

Next Steps:

• Monitor for updates

• We can forward most inbound calls to your fax number to an alternate destination. We do not currently have any workarounds for Outbound. If you wish to forward your fax number, please submit a case with your fax number and the number you want it forwarded to.

• Several version updates have failed. We are attempting alternate solutions.

• We continue to work with the vendor to establish service

Next Update

• 7:30 PM ET

Offline Services:

• NativeFax

Degraded Services:

• None

Operational Services:

• All other systems

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine cause and resolution

• Several patches and configuration changes have been made

• Vendor found the source of the blocked calls and are working to resolve it

• Root cause has been determined, and we are seeing successful faxes in and out. The MI is not marked as resolved yet because more patches still need to be applied. Until that's done, inbound/outbound faxes will only work intermittently.

Next Steps:

• Monitor for updates

• We can forward most inbound calls to your fax number to an alternate destination. We do not currently have any workarounds for Outbound. If you wish to forward your fax number, please submit a case with your fax number and the number you want it forwarded to.

• Several version updates have failed. We are attempting alternate solutions.

Next Update

• 6:30 PM ET

What Occurred: Inbound and Outbound Fax Failures

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine the cause and resolution

• Several patches and configuration changes have been made

• Vendor found the source of the blocked calls and are working to resolve it

• Root cause has been determined, and we are seeing successful faxes in and out. The MI is not marked as resolved yet because there are more patches to be applied. Until that is completed, inbound/outbound faxes will only work intermittently.

Next Steps:

• Monitor for updates

• We can forward inbound calls to your fax number to an alternate destination. We do not currently have any workarounds for Outbound. If you wish to forward your fax number, please submit a case with your fax number and the number you want it forwarded to.

Next Update

• 5:30 PM ET

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine the cause and resolution

• Several patches and configuration changes have been made

• Vendor found the source of the blocked calls and are working to resolve it

Next Steps:

• Monitor for updates

• We can forward inbound calls to your fax number to an alternate destination. We do not currently have any workarounds for Outbound. If you wish to forward your fax number, please submit a case with your fax number and the number you want it forwarded to.

Next Update

• 4:30 PM ET

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine cause and resolution

Next Steps:

• Monitor for updates

• We can forward inbound calls to your fax number to an alternate destination. We do not currently have any workarounds for Outbound. If you wish to forward your fax number, please submit a case with your fax number and the number you want it forwarded to.

Next Update

• 3:30 PM ET

What Occurred: Inbound and outbound faxes failing (Investigation)

What is Affected: Native Fax

When It Began:

• Initial reports at 5:37 PM ET on 6/10/2026

• New reports at 12 PM ET on 6/11/2026

Current Status:

• Successful patch applied last night at 11:35 PM ET

• New reports of failing began around 12:00 PM ET

• We are engaged with the vendor again to determine cause and resolution

Next Steps:

• Monitor for updates

• We are investigating potential workarounds

Next Update: 2:30 PM ET

Offline Services:

• NativeFax

What Occurred: Inbound and outbound faxes failing

What Is Affected: Native Fax

When It Began: Initial reports on June 10th, 2026 at 5:37 PM ET*

Current Status:

• Update was successfully applied and all services restored as of June 10th, 2026, at 11:29 PM ET.

• 24 hours of monitoring showed no additional failures.

Next Steps:

• We will continue to monitor for the next 24 hours.

• A Major Incident Report will be released within 72 hours.

What Occurred: Inbound and outbound faxes failing

What Is Affected: Native Fax

When It Began: Initial reports at 5:37 PM ET*

Current Status:

• We are working directly with the fax vendor's engineers and are currently applying a potential fix.

• Faxes attempted to be sent or received since 5:37 PM ET will not be processed by the fax server and will not be  recoverable

• We have identified the source of the outage. The software the manages our fax connections crashed. We will continue to identify the RCA

• Initial patch was unsuccessful. We are working with the vendor on alternate solutions

• Engineering has cleared the blockers that were preventing the update from running.

• Update installation has resumed

• Update has been applied successfully

• This Incident is considered RESOLVED: All services restored as of 11:29 PM ET

Next Steps:

• We will continue to monitor for the next 48 hours.

• Updates to be provided every 24 hours at most

• A Major Incident Report will be released within 72 hours

Next Update: 11:00 AM ET

What Is Affected: Native Fax

When It Began: Initial reports at 5:37 PM ET*

Current Status:

• We are working directly with the fax vendor's engineers and are currently applying a potential fix.

• Faxes attempted to be sent or received since 5:37 PM ET will not be processed by the fax server and will not be  recoverable

• We have identified the source of the outage. The software the manages our fax connections crashed. We will continue to identify the RCA

• Initial patch was unsuccessful. We are working with the vendor on alternate solutions

• Engineering has cleared the blockers that were preventing the update from running.

• Update installation has resumed

Next Steps:

• Hold while we work with the vendor

Next Update: 11:30 PM ET

What Occurred: Inbound and Outbound faxes Failing

What Is Affected: Native Fax

When It Began: Initial reports at 5:37 PM ET*

Current Status:

• We are working directly with the fax vendor's engineers and are currently applying a potential fix.

• Faxes attempted to be sent or received since 5:37 PM ET will not be processed by the fax server and will not be recoverable

• We have identified the source of the outage. The software that manages our fax connections crashed. We will continue to identify the RCA

• The initial patch was unsuccessful. We are working with the vendor on alternate solutions

Next Steps:

• Hold while we work with the vendor

Next Update: 10:30 PM ET

What Is Affected: Native Fax

When It Began: Initial reports at 5:37 PM ET*

Current Status:

• We are working directly with the fax vendor's engineers and are currently applying a potential fix.

• Faxes attempted to be sent or received since 5:37 PM ET will not be processed by the fax server and will not be recoverable

• We have identified the source of the outage. The software that manages our fax connections crashed. We will continue to identify the RCA

• The vendor patch is still being applied

Next Steps:

• Hold while we work with the vendor

Next Update: 9:30 PM ET

What Is Affected: Native Fax

When It Began: Initial reports at 5:37 PM ET*

Current Status:

• We are working directly with the fax vendor's engineers and are currently applying a potential fix.

• Faxes attempted to be sent or received since 5:37 PM ET will not be processed by the fax server and will not be recoverable

• We have identified the source of the outage. The software that manages our fax connections crashed. We will continue to identify the RCA

• The vendor patch is still being applied

Next Steps:

• Hold while we work with the vendor

Next Update: 9:30 PM ET

What Occurred: At approximately 6:00 PM ET on June 10, 2026, we became aware that inbound and outbound faxes are failing. 

What Is Affected: Inbound and Outbound faxes on the NativeFax platform are failing. 

When It began: June 10th, 2026, at 6:00 PM ET

Current Status: We have identified the root cause as a failure of the fax port server. We continue to work with the vendor to properly establish sessions. 

Next Update: 8:30 PM ET

This incident is considered resolved, and the Major Incident Report (MIR) is now available.

• Major Incident Report (MIR): https://voipdocs.io/announcements/-2026-06-03-cloudieconnect-failing-to-register

What Occurred: At approximately 8:30 AM ET on June 3, 2025, we became aware that the IPs associated with the CloudieConnect services became unassociated with the registration servers.

What Was Affected: CloudieConnect desktop and mobile apps were unable to register for both branded and unbranded apps.

When It began: June 3rd, 2026, at 8:30 AM ET

Current Status: Following 24 hours of monitoring, the issue has been fully resolved with no further concerns identified.

A Major Incident Report (MIR) will be issued within 24 business hours.

What was Affected: CloudieConnect desktop and mobile apps were unable to register for both branded and unbranded apps.

When It began: June 3rd, 2026, at 8:30 AM ET

Current Status: At this time, the IP addresses have been successfully reassociated, and we have confirmed both the mobile and desktop apps are working as expected.

Next Steps:

• If CloudieConnect continues to show unregistered, or if users are unable to answer calls or experience one-way/no audio, please log out and log back in. If the issue persists after logging back in, please submit a support ticket so our team may assist further.

• We will continue monitoring for the next 24 hours.

• A Major Incident Report (MIR) will be issued within 48 business hours.

Next Update: June 4th, 2026, at 10:00 AM ET

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).