OIT Outage History

Started Sep 11, 2026, 02:38 PM UTC· resolved Sep 12, 2026, 03:59 PM UTC

1. identified Sep 11, 2026, 02:38 PM UTC

   **What Occurred**: At 10:21 AM ET on September 11th, 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**: September 11th, 2026 at 10:21 AM ET **Current Status:** We identified the root cause as a failure of the fax port server and working to restore service. **Next Update:** September 11th, 2026 at 11:30 AM ET.

2. identified Sep 11, 2026, 03:00 PM UTC

   **What Occurred:** At approximately 10:21 AM ET on September 11th, 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:** September 11th, 2026, at 10:21 AM 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:** September 11th, 2026, at 12:00 PM ET.

3. identified Sep 11, 2026, 03:47 PM UTC

   **What Occurred:** At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing. **What is Affected:** Inbound and Outbound faxes on the Native Fax platform are failing. **When it began:** September 11th, 2026, at 10:21 AM ET **Current Status:** Inbound and outbound faxes began failing again at 11:39 AM ET. We are working to resolve this issue as quickly as possible. **Next Update:** September 11th, 2026, at 12:45 PM ET.

4. identified Sep 11, 2026, 04:33 PM UTC

   **What Occurred:** At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing. **What is Affected:** Inbound and Outbound faxes on the Native Fax platform are failing. **When it began:** September 11th, 2026, at 10:21 AM ET **Current Status:** We are working with our vendor to restore fax, isolate the root cause, and restore services as quickly as possible. **Next Update:** September 11th, 2026, at 1:45 PM ET.

5. monitoring Sep 11, 2026, 05:44 PM UTC

   **What Occurred:** At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes were failing. **What was Affected**: Inbound and Outbound faxes on the Native Fax platform are failing. **When it began:** September 11th, 2026, at 10:21 AM ET **Current Status:** * We have successfully identified and addressed the root cause for the fax failures. * At this time, we have restored service to the port server and are seeing both inbound and outbound faxes completing successfully. * We will continue to monitor and observe server stability for the next 24 hours. **Next Update:** September 12th, 2026, at 1:45 PM ET.

6. resolved Sep 12, 2026, 03:59 PM UTC

   **What Occurred:** At approximately 10:21 AM ET on September 11th, 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:** September 11th, 2026, at 10:21 AM ET **Current Status:** * 24 hours of monitoring showed no additional failures. * **This incident is considered resolved.** **Next Steps:** * A Major Incident Report will be released within 72 business hours..

7. monitoring Sep 16, 2026, 04:53 PM UTC

   This incident was resolved on September 12th at 12:00 PM ET, and the Major Incident Report (MIR) is now available. * **Major Incident Report (MIR):** .

Read the full incident report →

Started Aug 19, 2026, 09:14 PM UTC· resolved Aug 21, 2026, 09:11 PM UTC

1. identified Aug 19, 2026, 09:14 PM UTC

   **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 identified the root cause, a failure of the fax port server, and are currently working to restore service. **Next Update:** August 19th, 2026 at 6:00pm ET.

2. monitoring Aug 19, 2026, 09:57 PM UTC

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

3. identified Aug 20, 2026, 08:21 PM UTC

   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.

4. monitoring Aug 20, 2026, 09:01 PM UTC

   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.

5. identified Aug 20, 2026, 11:49 PM UTC

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

6. identified Aug 21, 2026, 01:32 AM UTC

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

7. monitoring Aug 21, 2026, 02:15 AM UTC

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

8. resolved Aug 21, 2026, 09:11 PM UTC

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

9. monitoring Aug 25, 2026, 04:57 PM UTC

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

Read the full incident report →

Started Jul 23, 2026, 04:43 PM UTC· resolved Jul 23, 2026, 07:38 PM UTC

1. identified Jul 23, 2026, 04:43 PM UTC

   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 11:06am ET, Microsoft put out an Incident notification that they are aware of M365 Services being impacted and are investigating, but do not have a full scope of services impacted at this time. Next Steps: To continue being able to make and receive phone calls, we recommended installing the CloudieConnect app for [Desktop](https://voipdocs.io/cloudieconnect-desktop/cloudieconnect-desktop-overview)/Mobile ([iOS](https://apps.apple.com/us/app/cloudieconnect/id6747597037?platform=iphone) \+ [Android](https://play.google.com/store/apps/details?id=com.oitvoip.cloudieconnect&pcampaignid=web%5Fshare)) or utilize SNAPmobile web. Next Update: July 23 2026, 1:30pm ET.

2. identified Jul 23, 2026, 05:29 PM UTC

   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](https://voipdocs.io/cloudieconnect-desktop/cloudieconnect-desktop-overview)/Mobile ([iOS](https://apps.apple.com/us/app/cloudieconnect/id6747597037?platform=iphone) \+ [Android](https://play.google.com/store/apps/details?id=com.oitvoip.cloudieconnect&pcampaignid=web%5Fshare)) or utilize [SNAPmobile web](https://voipdocs.io/mobile-applications/how-to-use-snapmobile-web). Next Update: July 23, 2026, 2:30pm ET.

3. identified Jul 23, 2026, 06:21 PM UTC

   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](https://voipdocs.io/cloudieconnect-desktop/cloudieconnect-desktop-overview)/Mobile ([iOS](https://apps.apple.com/us/app/cloudieconnect/id6747597037?platform=iphone) \+ [Android](https://play.google.com/store/apps/details?id=com.oitvoip.cloudieconnect&pcampaignid=web%5Fshare)) or utilize [SNAPmobile web](https://voipdocs.io/mobile-applications/how-to-use-snapmobile-web). Next Update: July 23, 2026, 3:30pm ET.

4. resolved Jul 23, 2026, 07:38 PM UTC

   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 [[email protected]](mailto:[email protected]) * 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..

Read the full incident report →

Started Jun 10, 2026, 10:00 PM UTC· resolved Jun 16, 2026, 04:15 PM UTC

1. identified Jun 10, 2026, 10:00 PM UTC

   What Occurred: At approximately 6:00 PM ET on June 10, 2026, we became aware that inbound and outbound faxes are failing. What Was 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 identified the root cause as a failure of the fax port server and working to restore service. .

2. identified Jun 10, 2026, 11:28 PM UTC

   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.

3. monitoring Jun 11, 2026, 12:29 AM UTC

   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.

4. monitoring Jun 11, 2026, 12:32 AM UTC

   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.

5. monitoring Jun 11, 2026, 01:30 AM UTC

   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.

6. monitoring Jun 11, 2026, 02:22 AM UTC

   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.

7. resolved Jun 11, 2026, 03:37 AM UTC

   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.

8. resolved Jun 11, 2026, 03:12 PM UTC

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

9. investigating Jun 11, 2026, 05:32 PM UTC

   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.

10. investigating Jun 11, 2026, 06:20 PM UTC

    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.

11. identified Jun 11, 2026, 07:29 PM UTC

    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.

12. identified Jun 11, 2026, 08:22 PM UTC

    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.

13. investigating Jun 11, 2026, 09:24 PM UTC

    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.

14. identified Jun 11, 2026, 10:30 PM UTC

    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.

15. identified Jun 11, 2026, 11:33 PM UTC

    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.

16. monitoring Jun 12, 2026, 12:15 AM UTC

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

17. monitoring Jun 12, 2026, 03:06 PM UTC

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

18. resolved Jun 16, 2026, 04:15 PM UTC

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

19. monitoring Jun 17, 2026, 10:01 PM UTC

    Major Incident Report: .

Read the full incident report →

Started Jun 03, 2026, 01:16 PM UTC· resolved Jun 04, 2026, 06:26 PM UTC

1. investigating Jun 03, 2026, 01:16 PM UTC

   **What Occurred:** At approximately 8:30 AM, June 3, 2026, we became aware that the IPs associated with the CloudieConnect services became unassociated with the registration servers. **What is Affected:** CloudieConnect desktop and mobile apps are unable to register for both branded and unbranded apps. **When It began:** June 3rd, 2026, at 8:30 AM ET **Current Status**: We are working to reassociate the affected IPs as quickly as possible. **Next Steps**: Clients may use SNAPmobile or SNAPmobile Web as a temporary workaround until the problem is resolved. * * **Next Update**: June 3rd, 2026, at 10:30 AM ET.

2. resolved Jun 03, 2026, 02:20 PM UTC

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

3. resolved Jun 04, 2026, 06:26 PM UTC

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

4. monitoring Jun 05, 2026, 03:38 PM UTC

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

Read the full incident report →

Started Apr 15, 2026, 07:29 PM UTC· resolved Apr 16, 2026, 07:31 PM UTC

1. monitoring Apr 15, 2026, 07:29 PM 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 [[email protected]](mailto:[email protected]). For more real time status updates as well as discussion please join our Discord (Not official support)..

2. resolved Apr 16, 2026, 07:31 PM 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 [[email protected]](mailto:[email protected]). For more real time status updates as well as discussion please join our Discord (Not official support)..

Read the full incident report →

Started Mar 03, 2026, 03:27 PM UTC· resolved Mar 03, 2026, 04:42 PM UTC

1. monitoring Mar 03, 2026, 03:27 PM UTC

   At approximately 9:25am ET, we became aware of inbound and outbound call quality concerns through our carrier Bandwidth, causing choppiness on call audio. **When it began: 9:25am ET** **Current Status:** While gathering details and examples from partners, Bandwidth updated their status page at 9:39am ET acknowledging call failures. At 9:58am ET, Bandwidth updated that they are observing expected inbound and outbound calls and are monitoring. **Next Steps:** We have temporarily rerouted outbound calls through another carrier to preserve outbound call quality. Outbound calls should be functioning as expected. Inbound calls through Bandwidth may continue to have degraded quality until the incident is resolved by them. **Next Update:** 11:20am ET.

2. monitoring Mar 03, 2026, 04:23 PM UTC

   **What is affected:** At approximately 9:25am ET, we became aware of inbound and outbound call quality concerns through our carrier Bandwidth causing choppiness on call audio. **When it began: 9:25am ET** **Current Status:** While gathering details and examples from partners, Bandwidth updated their status page at 9:39am ET acknowledging call failures. At 9:58am ET, Bandwidth updated that they are observing expected inbound and outbound calls and monitoring. We have temporarily rerouted outbound calls through another carrier to preserve outbound call quality. Outbound calls should be functioning as expected. Inbound calls through Bandwidth may continue to have degraded quality until the incident is resolved by them. **Next Steps:** At this time, we are continuing to monitor inbound call quality, however, no further reports of choppiness or degraded quality have been made. **Next Update:** 12:20pm ET.

3. resolved Mar 03, 2026, 04:42 PM UTC

   At approximately 9:25am ET, we became aware of inbound and outbound call quality concerns through our carrier Bandwidth causing choppiness on call audio. **When it began: 9:25am ET** **Current Status:** At this time, Bandwidth has declared the incident resolved. We have removed the reroute impacting outbound calls and tested to confirm inbound and outbound calls are successful. **Next Steps:** A major incident report will be released within 48 business hours..

Read the full incident report →

Started Jan 21, 2026, 03:54 PM UTC· resolved Jan 26, 2026, 04:16 PM UTC

1. monitoring Jan 21, 2026, 03:54 PM UTC

   **What Occurred**: At 10:20 AM ET, we were made aware of outbound calls failing for several clients. After further investigation, we determined that one of our underlying carriers was experiencing degraded services leading to outbound call failures. **What is Affected:** All Outbound Calling **When it Began:** 01/21/2026, 10:20 AM ET **Current Status:** As of 10:34 AM ET, outbound calls have been rerouted through a different carrier and are now going through successfully. **Next Steps:** The major incident report will be available within 48 business hours. **Next Update:** 01/22/2026, 10:30 AM ET We appreciate your patience throughout this process. If you need support, please contact [[email protected]](mailto:[email protected]). For more real time status updates as well as discussion, please join our Discord (Not official support)..

2. resolved Jan 22, 2026, 03:14 PM UTC

   **What Occurred**: On 1/21/26, at 10:20 AM ET, we were made aware of outbound calls failing for several clients. After further investigation, we determined that one of our underlying carriers was experiencing degraded services, resulting in outbound call failures. **What was Affected:** Outbound Calling for DFW Region **When it Began**: 01/21/2026, 10:20 AM ET **Current Status**: Bandwidth declared the incident resolved yesterday at 7:22 PM ET. After 24 hours of monitoring and testing, we successfully routed all traffic back through Bandwidth and have confirmed all outbound calls are continuing to process as expected. **Next Steps:** * This incident is now considered resolved. * The major incident report will be available within 48 business hours. **Next Update:** N/A.

3. resolved Jan 26, 2026, 04:16 PM UTC

   The major incident report is now available: .

Read the full incident report →