UCaaS Status Page - Notice history

This incident was resolved on August 21st at 5:15 PM ET, and the Major Incident Report (MIR) is now available.

• Major Incident Report (MIR): https://voipdocs.io/announcements/2026-08-19-nativefax-inbound-and-outbound-faxing-failure-resolved

What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.

What was Affected: Inbound and Outbound faxes on the NativeFax platform

When it began: August 19th, 2026, at 3:21 PM ET

Current Status:

• After 24 hours of monitoring and observing server stability, we are considering this incident resolved.

The MIR will be provided within 48 business hours.

What Occurred: At approximately 4:47 PM ET on August 19th, 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: August 19th, 2026, at 3:21 PM ET

Current Status: We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.

Next Update: August 21st, 2026, at 5 PM ET

Identified

What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.

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

When it began: August 19th, 2026, at 3:21 PM ET

Current Status:

• We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.

• At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.

• At 4:46 PM ET, on August 20th, 2026, the port server service was restored.

• At 6:56 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.

• We're continuing to work on bringing the port server service back online, alongside the vendor's engineers. Further updates to follow as they're available.

Next Update: August 20th, 2026, at 10:30 pm ET

Identified

What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.

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

When it began: August 19th, 2026, at 3:21 PM ET

Current Status:

• We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.

• At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.

• At 4:46 PM ET, on August 20th, 2026, the port server service was restored.

• At 6:56 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.

• We are actively working to restore service and will provide further details as they become available.

Next Update: August 20th, 2026, at 8:45 pm ET

What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.

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

When it began: August 19th, 2026, at 3:21 PM ET

Current Status:

• We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.

• At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.

• As of 4:35 PM ET, we have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.

Next Update: August 21st, 2026, at 4:15 pm ET

What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.

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

When it began: August 19th, 2026, at 3:21 PM ET

Current Status:

• We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.

• At 3:51 PM ET on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.

• We are actively working to restore service and will provide further details as they become available.

Next Update: August 20th, 2026, at 5:15 pm ET

What Occurred: At approximately 4:47 PM ET on August 19th, 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: August 19th, 2026, at 3:21 PM ET

Current Status: We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.

Next Update: August 20th, 2026, at 3:30 pm ET

What Occurred: Teams Calling intermittently failing with one-way or no-way audio.

What is Affected: Inbound and Outbound Calling through the Teammate Teams Connector

When it began: 11:00am ET, July 23, 2026

Current Status: At 2:36pm ET, Microsoft successfully reverted a network change, along with rerouting traffic, which has restored services on their end. After internal testing, we have confirmed inbound and outbound calling services have been restored.

Next Steps:

• If inbound or outbound calling does not immediately return, please restart the Teams app and reopen. If you continue experiencing call failures, please submit a support ticket to support@oit.co

• With Microsoft being the root cause of the underlying service outage, and not having visibility into the root cause, no major incident report will be provided.

What Occurred: Teams Calling intermittently failing with one-way or no-way audio.

What is Affected: Inbound and Outbound Calling through the Teammate Teams Connector.

When it began: 11:00am ET, July 23, 2026

Current Status: At 1:04pm ET, Microsoft continues to scale up rerouting efforts and are seeing indications of increasing restoration of services. They continue to implement additional mitigation measures alongside these actions.

Next Steps: To continue being able to make and receive phone calls, it is recommended to install the CloudieConnect app for Desktop/Mobile (iOS + Android) or utilize SNAPmobile web.

Next Update: July 23, 2026, 3:30pm ET

What Occurred: Teams Calling intermittently failing with one-way or no-way audio.

What is Affected: Inbound and Outbound Calling through the Teammate Teams Connector.

When it began: 11:00am ET, July 23, 2026

Current Status: At 12:47pm ET, Microsoft identified alternate network paths and performed traffic rerouting for some services, which contributed to partial recovery. They are scaling up rerouting efforts while continuing to evaluate additional mitigation actions.

Next Steps: To continue being able to make and receive phone calls, it is recommended to install the CloudieConnect app for Desktop/Mobile (iOS + Android) or utilize SNAPmobile web.

Next Update: July 23, 2026, 2:30pm ET