UCaaS Status Page Status - Incident history

Urgent Update: ATL Server Maintenance - September 22, 2026

Wed, 23 Sep 2026 14:40:00 +0000

Type: Maintenance

Duration: 6 hours and 48 minutes

Affected Components:

Sep 22, 14:36:30 GMT+0
Identified - Last night's maintenance revealed additional errors in MySQL on our ATL cores. Calling, registration and all other critical services are functioning normally on all other cores. For devices and DIDs registered to ATL there are instances of class 5 features (call queues, auto attendants, music on hold) not functioning properly. Additionally, devices and calls going through ATL are not displaying properly in the portal. We will be proactively removing ATL from service in order to diagnose and resolve the MySQL errors. Provisioned devices, and those manually configured with our SRV records will failover gracefully to alternate cores. Calls and other services will also failover gracefully. Shutting down ATL will allow the portals to display correctly for all active cores. Upon completion of the maintenance devices and calls will revert to their original core. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Sep 22, 21:24:24 GMT+0
Completed - **Notice/Update:** ATL MySQL databases were repaired and are functioning properly and have remained stable. We are going to return Atlanta (ATL) Voice back to service within 10 minutes. Devices and calls will failover on their own. If your devices haven't reverted after 12 hours, you can restart the device, and it should register to its original core again. There will be no loss of service for phone calls. The maintenance window will also be closed..

Urgent ATL Server Maintenance - September 22nd, 2026

Tue, 22 Sep 2026 04:00:00 +0000

Type: Maintenance

Duration: 3 hours

Affected Components:

Sep 21, 21:44:20 GMT+0
Identified - **Notice/Update:** During the maintenance window below, we will be restarting services on our ATL cores to address a memory leak issue. Provisioned devices, and those manually configured with our SRV records, will failover gracefully to alternate cores. Calls and other services will also failover gracefully. Upon completion of the maintenance, devices and calls will revert to their original core. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Sep 22, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 22, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Inbound and Outbound Fax Failures on NativeFax

Fri, 11 Sep 2026 14:38:39 +0000

Type: Incident

Duration: 1 day, 1 hour and 21 minutes

Affected Components:

Sep 16, 16:53:47 GMT+0
Postmortem - 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):** .

Sep 11, 14:38:39 GMT+0
Identified - **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.

Sep 11, 15:00:05 GMT+0
Identified - **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.

Sep 11, 15:47:22 GMT+0
Identified - **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.

Sep 11, 16:33:28 GMT+0
Identified - **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.

Sep 11, 17:44:17 GMT+0
Monitoring - **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.

Sep 12, 15:59:58 GMT+0
Resolved - **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..

Fax Server Maintenance - 9/10/26

Fri, 11 Sep 2026 03:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Sep 2, 20:22:25 GMT+0
Identified - We will be performing security maintenance on our fax server on **September 10th, 2026, at 11:00 PM ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Sep 11, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 11, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

PHX Server Maintenance - 9/10/26

Thu, 10 Sep 2026 04:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components: , , ,

Sep 3, 16:29:11 GMT+0
Identified - **Notice/Update:** Routine maintenance is scheduled for the PHX servers on **September 10th, 12:00 AM ET**. Inbound and outbound calls, the PHX portal, and the NDP server will all fail over to alternate servers automatically during the maintenance window. Recordings normally stored on the PHX recording server will also be captured on the alternate servers. QoS data will be unavailable for the duration. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Sep 10, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 10, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

PHX Server Maintenance - 9/3/26

Fri, 4 Sep 2026 02:00:00 +0000

Type: Maintenance

Duration: 2 hours

Affected Components: , , ,

Aug 31, 17:08:17 GMT+0
Identified - **Notice/Update:** Routine maintenance is scheduled for the PHX servers on **September 3rd, 10:00 PM ET**. Inbound and outbound calls, the PHX portal, and the NDP server will all fail over to alternate servers automatically during the maintenance window. Recordings normally stored on the PHX recording server will also be captured on the alternate servers. QoS data will be unavailable for the duration. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Sep 4, 02:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 4, 04:00:00 GMT+0
Completed - Maintenance has completed successfully.

IAD Server Maintenance - 9/3/26

Thu, 3 Sep 2026 04:30:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components: , , ,

Aug 27, 15:36:10 GMT+0
Identified - **Notice/Update:** Routine maintenance is scheduled for the IAD servers on **September 3rd, 12:30 AM ET**. Inbound and outbound calls, the IAD portal, and the NDP server will all fail over to alternate servers automatically during the maintenance window. Recordings normally stored on the IAD recording server will also be captured on the alternate servers. QoS data will be unavailable for the duration. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Sep 3, 04:30:01 GMT+0
Identified - Maintenance is now in progress.

Sep 3, 08:30:00 GMT+0
Completed - Maintenance has completed successfully.

CloudieConnect Maintenance - 9/2/26

Wed, 2 Sep 2026 04:00:00 +0000

Type: Maintenance

Duration: 1 hour

Affected Components:

Sep 2, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 2, 05:00:00 GMT+0
Completed - Maintenance has completed successfully.

Aug 26, 17:00:42 GMT+0
Identified - We will be performing maintenance on the underlying infrastructure that hosts CloudieConnect on **September 2nd, 2026 at 12:00 AM ET**. CloudieConnect will be unavailable for a brief period while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Fax Server Maintenance - 8/20/26

Fri, 21 Aug 2026 03:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Aug 14, 17:13:44 GMT+0
Identified - We will be performing security maintenance on our fax server on **August 20th, 2026, at 11:00 PM ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Aug 21, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 21, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Inbound and Outbound NativeFax Failures

Wed, 19 Aug 2026 21:14:22 +0000

Type: Incident

Duration: 1 day, 23 hours and 57 minutes

Affected Components:

Aug 19, 21:14:22 GMT+0
Identified - **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.

Aug 20, 23:49:32 GMT+0
Identified - **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.

Aug 21, 01:32:03 GMT+0
Identified - **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.

Aug 19, 21:57:08 GMT+0
Monitoring - **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.

Aug 20, 20:21:01 GMT+0
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. * 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.

Aug 20, 21:01:24 GMT+0
Monitoring - 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.

Aug 21, 02:15:40 GMT+0
Monitoring - **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.

Aug 21, 21:11:07 GMT+0
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..

Aug 25, 16:57:44 GMT+0
Postmortem - 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):** .

CloudieConnect Maintenance - 7/24/26

Fri, 24 Jul 2026 04:00:00 +0000

Type: Maintenance

Affected Components:

Jul 20, 17:11:25 GMT+0
Completed - We will be performing maintenance on the underlying infrastructure that hosts CloudieConnect on **July 24th at 12:00 AM ET**. CloudieConnect will be unavailable for a brief period while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Inbound and Outbound Calling through the Teammate Teams Connector Intermittently Failing

Thu, 23 Jul 2026 16:43:13 +0000

Type: Incident

Duration: 2 hours and 55 minutes

Affected Components:

Jul 23, 17:29:26 GMT+0
Identified - 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.

Jul 23, 18:21:17 GMT+0
Identified - 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.

Jul 23, 19:38:26 GMT+0
Resolved - 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](mailto: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..

Jul 23, 16:43:13 GMT+0
Identified - 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.

Fax Server Maintenance - 7/2/26

Fri, 3 Jul 2026 03:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Jul 3, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jun 25, 16:06:10 GMT+0
Identified - We will be performing security maintenance on our fax server on **July 2nd, 2026, at 11:00 PM ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Jul 3, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Urgent Fax Server Maintenance - 6/19/26

Fri, 19 Jun 2026 05:00:00 +0000

Type: Maintenance

Duration: 1 hour

Affected Components:

Jun 18, 20:14:20 GMT+0
Identified - We will be performing urgent maintenance on our fax servers tonight, **June 19th, 2026, at 1:00 AM ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Jun 19, 05:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 19, 06:00:00 GMT+0
Completed - Maintenance has completed successfully.

NativeFax Inbound and Outbound Fax Failures

Wed, 10 Jun 2026 22:00:00 +0000

Type: Incident

Duration: 5 days, 18 hours and 16 minutes

Affected Components:

Jun 10, 23:28:21 GMT+0
Identified - 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.

Jun 11, 00:32:50 GMT+0
Monitoring - 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.

Jun 11, 00:29:19 GMT+0
Monitoring - 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.

Jun 11, 02:22:16 GMT+0
Monitoring - 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.

Jun 10, 22:00:00 GMT+0
Identified - 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. .

Jun 11, 01:30:37 GMT+0
Monitoring - 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.

Jun 11, 19:29:35 GMT+0
Identified - 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.

Jun 11, 20:22:36 GMT+0
Identified - 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.

Jun 11, 21:24:10 GMT+0
Investigating - 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.

Jun 11, 22:30:32 GMT+0
Identified - 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.

Jun 11, 23:33:18 GMT+0
Identified - 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.

Jun 11, 03:37:51 GMT+0
Resolved - 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.

Jun 11, 15:12:24 GMT+0
Resolved - 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..

Jun 12, 00:15:47 GMT+0
Monitoring - **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.

Jun 11, 17:32:59 GMT+0
Investigating - 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.

Jun 11, 18:20:35 GMT+0
Investigating - 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.

Jun 12, 15:06:01 GMT+0
Monitoring - **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..

Jun 16, 16:15:40 GMT+0
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..

Jun 17, 22:01:34 GMT+0
Postmortem - Major Incident Report: .

CloudieConnect Server Maintenance - 6/10/26

Wed, 10 Jun 2026 04:30:00 +0000

Type: Maintenance

Duration: 2 hours

Affected Components:

Jun 10, 04:30:01 GMT+0
Identified - Maintenance is now in progress.

Jun 10, 04:30:00 GMT+0
Identified - We will be performing general maintenance and updates to our CloudieConnect backend servers on **June 10th, 2026, at 12:30 AM ET**. During this time, calls and device registrations will be rerouted to alternate servers. No service interruption is expected during the maintenance window, though devices may experience a brief re-registration period as they transition to the alternate servers. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Jun 10, 06:30:00 GMT+0
Completed - Maintenance has completed successfully.

ATL Server General Maintenance – 6/4/26

Thu, 4 Jun 2026 06:00:00 +0000

Type: Maintenance

Duration: 36 minutes

Affected Components:

Jun 4, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 4, 06:35:59 GMT+0
Completed - Maintenance has completed successfully. .

Jun 4, 06:00:00 GMT+0
Identified - We will be performing general maintenance on our ATL server on **June 4th, 2026, at 2:00 AM EST**. During this time, calls and device registrations will be rerouted to alternate servers, with no expected interruption of services during the maintenance window. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

CloudieConnect Servers Failing to Register

Wed, 3 Jun 2026 13:16:21 +0000

Type: Incident

Duration: 1 hour and 4 minutes

Affected Components:

Jun 3, 13:16:21 GMT+0
Investigating - **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.

Jun 5, 15:38:20 GMT+0
Postmortem - This incident is considered resolved, and the Major Incident Report (MIR) is now available. * **Major Incident Report (MIR):** .

Jun 3, 14:20:21 GMT+0
Resolved - **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.

Jun 4, 18:26:21 GMT+0
Resolved - **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..

Fax Server Maintenance - 5/14/26

Fri, 15 May 2026 03:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

May 15, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

May 15, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

May 15, 03:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server on **May 14th, 2026, at 11:00 PM ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Urgent IAD Maintenance 4/30/26

Thu, 30 Apr 2026 11:30:00 +0000

Type: Maintenance

Duration: 2 hours

Affected Components:

Apr 30, 11:30:00 GMT+0
Identified - On **April 30th, 2026 at 7:30 AM ET**, Oracle will be performing emergency maintenance on the underlying infrastructure that hosts our IAD core. During maintenance, devices and portal servers on IAD will move to other cores, so no interruption of service is expected. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Apr 30, 11:30:01 GMT+0
Identified - Maintenance is now in progress.

Apr 30, 13:30:00 GMT+0
Completed - Maintenance has completed successfully.

Loss Of Registration and Dropped Calls PHX

Wed, 15 Apr 2026 19:29:27 +0000

Type: Incident

Duration: 1 day and 2 minutes

Affected Components:

Apr 15, 19:29:27 GMT+0
Monitoring - **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](mailto:support@oit.co). For more real time status updates as well as discussion please join our Discord (Not official support)..

Apr 16, 19:31:29 GMT+0
Resolved - **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](mailto:support@oit.co). For more real time status updates as well as discussion please join our Discord (Not official support)..

Urgent PHX Maintenance 4/8/26

Thu, 9 Apr 2026 00:30:00 +0000

Type: Maintenance

Duration: 2 hours and 34 minutes

Affected Components:

Apr 9, 00:30:00 GMT+0
Identified - On **April 8th, 2026, at 8:30 PM ET**, Oracle will be performing emergency maintenance on the underlying infrastructure that hosts our PHX core. During maintenance, devices and portal servers on PHX will move to other cores, so no interruption of service is expected. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Apr 9, 00:30:01 GMT+0
Identified - Maintenance is now in progress.

Apr 9, 03:04:00 GMT+0
Completed - Maintenance has completed successfully.

Urgent Core1-ATL Security Updates 3/27/26

Fri, 27 Mar 2026 06:00:00 +0000

Type: Maintenance

Duration: 2 hours

Affected Components: , ,

Mar 27, 06:00:00 GMT+0
Identified - We will be performing urgent security updates on Core1-ATL on **March 27th, 2026 at 2:00 am ET**. There is no expected interruption of service during this time, but users may be logged out of the Manager Portal and SNAPmobile Web during the maintenance window. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Mar 27, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 27, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Fax Server Maintenance 3/26/26

Fri, 27 Mar 2026 03:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Mar 27, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 27, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Mar 27, 03:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server on **March 26th, 2026, at 11:00 pm ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Call Quality Degradation for Inbound and Outbound calls through Bandwidth

Tue, 3 Mar 2026 15:27:33 +0000

Type: Incident

Duration: 1 hour and 15 minutes

Affected Components: ,

Mar 3, 15:27:33 GMT+0
Monitoring - 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.

Mar 3, 16:23:27 GMT+0
Monitoring - **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.

Mar 3, 16:42:56 GMT+0
Resolved - 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..

Fax Server Maintenance 2/25/26

Thu, 26 Feb 2026 04:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Feb 26, 04:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server on **February 25th, 2026, at 11:00 pm ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Feb 26, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 26, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Significant Connection Delays on Outbound Calls

Wed, 21 Jan 2026 15:54:20 +0000

Type: Incident

Duration: 23 hours and 20 minutes

Affected Components:

Jan 22, 15:14:31 GMT+0
Resolved - **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.

Jan 26, 16:16:12 GMT+0
Resolved - The major incident report is now available: .

Jan 21, 15:54:20 GMT+0
Monitoring - **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 [support@oit.co](mailto:support@oit.co). For more real time status updates as well as discussion, please join our Discord (Not official support)..

Fax Server Maintenance 1/14/26

Thu, 15 Jan 2026 04:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Jan 15, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 15, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jan 15, 04:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server and firewall on **January 14th, 2026, at 11:00 pm ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Manager Portal Pro V4.0.0 Upgrade 01/10/26

Sat, 10 Jan 2026 15:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Jan 10, 15:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 10, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jan 10, 15:00:00 GMT+0
Identified - To improve platform performance and reliability, we will be upgrading Manager Portal Pro (MPP) to version 4.0.0 on **January 10th, 2026, at 10:00 am ET**. No service downtime is expected during this maintenance window. However, you may need to log out of the Manager Portal and log back in once the upgrade is complete. **Please Note:** Following this upgrade, webhook integrations (URL Call Pop) and Manager Portal Pro (MPP) features will use a new static IP address: **52.20.230.43** If you filter inbound traffic by source IP (such as via firewall or WAF rules), please ensure this new IP address is added to your allowlist prior to the maintenance window. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Service Controlling Voice Calls and Device Registration Crash on Core1-ATL

Mon, 22 Dec 2025 20:45:26 +0000

Type: Incident

Duration: 23 hours and 15 minutes

Affected Components:

Dec 22, 20:45:26 GMT+0
Monitoring - **What Occurred**: At 2:50 pm ET, the SiPbx service, which controls voice and registration on the core1-atl server, crashed, causing inbound and outbound calls to redirect to alternate servers, as well as device registration. **What is Affected:** Atlanta (ATL) Voice **When it Began:** 12/22/2025, 2:50 PM ET **Current Status:** At 2:53p ET, the SiPbx service automatically recovered, and device registrations and inbound/outbound calls began returning to the core1-atl server successfully. **Next Steps:** We are monitoring and investigating the root cause of the service failure. **Next Update:** 12/23/2025, 3:00 PM ET.

Dec 23, 20:00:46 GMT+0
Resolved - **What Occurred:** At 2:50 PM ET, the SiPbx service that controls voice and registration on the Core1-ATL server crashed, causing inbound and outbound calls to redirect to alternate servers, as well as device registration. **What is Affected:** Atlanta (ATL) Voice **When it Began:** December 22nd, 2025, 2:50 PM ET **Current Status:** As of 9:30 AM ET, Core1-ATL remains stable. Working with the vendor we were able to identify the root cause of the service crash. It was ultimately due to a subprocess not closing cleanly and a fix is implemented in the next system update which is scheduled for Q1 of 2026. **Next Steps:** This incident is now considered resolved. The major incident report will be available in 48 hours. .

CloudieConnect Unscheduled Maintenance 12/16/25

Tue, 16 Dec 2025 06:00:00 +0000

Type: Maintenance

Duration: 1 hour and 30 minutes

Affected Components:

Dec 16, 06:00:00 GMT+0
Identified - During the December 12th implementation of the CloudieConnect High Availability (HA) infrastructure, our engineering team identified additional configuration requirements that will strengthen the overall HA deployment. To ensure that the infrastructure is implemented to the highest standard, we have scheduled a follow-up maintenance window. On **Tuesday, December 16th, 2025 at 1:00 AM ET**, our team will finalize the High Availability server activation and integration for your CloudieConnect mobile and desktop apps. This maintenance will complete the infrastructure upgrades, delivering the enhanced reliability and seamless failover protection your operations depend on. During this 90-minute upgrade window, you may experience temporary service degradation as we bring the HA system fully online. Device registration, inbound/outbound calling, and messaging functions may be briefly affected. All other voice and portal services will continue to operate normally. Thank you for your patience as we complete this critical infrastructure upgrade. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Dec 16, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Dec 16, 07:30:00 GMT+0
Completed - Maintenance has completed successfully.

CloudieConnect HA Server Implementation

Fri, 12 Dec 2025 05:30:00 +0000

Type: Maintenance

Duration: 1 hour and 30 minutes

Affected Components:

Dec 10, 16:50:44 GMT+0
Identified - On **December 12th, 2025, starting at 12:30 AM ET**, OIT will be upgrading the resiliency of the servers that power our CloudieConnect mobile and desktop apps. This upgrade finalizes our High Availability (HA) infrastructure, providing a solid foundation for enhanced reliability and seamless failover protection. During the upgrade, CloudieConnect users may experience a brief service degradation lasting approximately 30 minutes as the HA server is activated and integrated. Device registration, inbound/outbound calling, and messaging may be temporarily impacted during this time. All other voice and portal services will continue to operate normally..

Dec 12, 05:30:01 GMT+0
Identified - Maintenance is now in progress.

Dec 12, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Dec 12, 05:30:00 GMT+0
Identified - On **December 12th, 2025, starting at 12:30 AM ET**, we will be performing system updates on the CloudieConnect servers to finalize High Availability (HA) services, ensuring failover redundancy is fully operational. A brief service degradation lasting approximately 30 minutes may occur as the HA server is activated and integrated with the existing infrastructure. During this time, device registration and inbound/outbound calling may be impacted. All other voice and portal services will continue to operate normally. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

DNS Updates for api.ucaasnetwork.com

Fri, 12 Dec 2025 01:00:00 +0000

Type: Maintenance

Duration: 1 hour

Affected Components:

Dec 12, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

Dec 12, 02:00:00 GMT+0
Completed - Maintenance has completed successfully.

Dec 12, 01:00:00 GMT+0
Identified - DNS updates for **api.ucaasnetwork.com** will be applied on **December 11th, 2025 at 8:00 PM ET**. The changes are to improve redundancy and speed of call responses for the API services. There is no expected downtime from this DNS change. There will also be no downtime for voice or portal services. As a reminder, please review your scripts for any IP filtering and ensure you are allowing traffic to and from all of our IPs. The full list can be found here: [https://voipdocs.io/faqs/ip-addresses-ports](https://voipdocs.io/faqs/ip-addresses-ports#ip-addresses-for-additional-services-2) We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Fax Server Maintenance 11/25/25

Wed, 26 Nov 2025 04:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

Nov 26, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Nov 26, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Nov 26, 04:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server and firewall on **November 25th, 2025, at 11:00 pm ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed..

Avanan/AWS Outage

Mon, 20 Oct 2025 18:10:59 +0000

Type: Incident

Duration: 7 hours and 10 minutes

Oct 20, 18:10:59 GMT+0
Identified - **What Occurred:** At 8:30 AM ET, our email filtering service began experiencing significant delays and delivery failures to our client-facing support mailboxes as a result of the widespread AWS US-East-1 outage this morning. This includes [support@oit.co](mailto:support@oit.co), [success@oit.co](mailto:success@oit.co), [porting@oit.co](mailto:porting@oit.co), [billing@oit.co](mailto:billing@oit.co), [sales@oit.co](mailto:sales@oit.co), and [compliance@oit.co](mailto:compliance@oit.co). **Who is Affected:** All partners and clients attempting to contact OIT support. **When It Began:** 8:30 AM ET, 10/20/2025 **Current Status:** We have disabled the email filtering service and restored deliverability to the affected mailboxes as of 12:30 PM ET. We are currently working with our email filtering service's support to complete the delivery of all emails sent to the affected mailboxes during this window. **Workarounds:** For urgent requests that were sent during this window that cannot wait until the emails are restored, please re-send the email or call our support at 305-967-6756. **Next Steps:** Continuing to work with vendor support to ensure all emails are delivered. **Next Update:** We will provide an update when all emails during the affected period are restored. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Oct 21, 01:21:09 GMT+0
Resolved - Resolved What Occurred: At 8:30 AM ET on October 10th, 2025, our email filtering service began experiencing significant delays and delivery failures to our client-facing support mailboxes as a result of the widespread AWS US-East-1 outage that morning. This includes [support@oit.co](mailto:support@oit.co), [success@oit.co](mailto:success@oit.co), [porting@oit.co](mailto:porting@oit.co), [billing@oit.co](mailto:billing@oit.co), [sales@oit.co](mailto:sales@oit.co), and [compliance@oit.co](mailto:compliance@oit.co). Who is Affected: All partners and clients attempting to contact OIT support When It Began: 8:30 AM ET, 10/20/2025 Current Status: This is considered Resolved. AWS and our email filtering service have confirmed full functionality has been restored. We've re-enabled our email filtering service and confirmed inbound emails are being received. Next Steps: If you submitted a support request via email between 8:30 AM ET and 12:30 PM ET and never received a case confirmation email response, please re-send your email to confirm it was received on our end. Next Update: N/A.

CloudieAI – Call Transcription and Sentiment not populating after enablement

Mon, 6 Oct 2025 21:39:22 +0000

Type: Incident

Duration: 1 day, 16 hours and 54 minutes

Affected Components:

Oct 6, 21:39:22 GMT+0
Investigating - We’re receiving reports that once CloudieAI is enabled, transcription and sentiment are not displaying in Call History across affected tenants. **Identified:** Oct 6, 2025, at 8:46 AM ET **Impact:** All partners/end users with CloudieAI enabled (previously or newly enabled) may not see transcription or sentiment appear in Call History. **Current status:** OIT is actively engaged with the vendor and investigating the root cause. **Workaround:** None confirmed at this time. **Next update:** We will provide an update when new information becomes available..

Oct 8, 14:33:08 GMT+0
Resolved - We identified an issue where Call Transcription and Sentiment data were not populating in Call History for users with CloudieAI enabled. **Issue Identified:** October 6, 2025, at 8:46 AM ET **Impact:** All partners and end users with CloudieAI enabled (previously or newly enabled) **Status:** * Resolved * Our team immediately investigated and implemented a fix, and we’re now seeing data populate successfully across affected tenants. We will continue to monitor performance to ensure stability. We believe **CloudieAI will have a major impact for all users**, empowering them with enhanced visibility into customer interactions and actionable insights. We want to ensure everyone has the maximum opportunity to experience its full potential—**without any risk**. With that goal in mind, we are proud to announce that we are **extending the free beta period through November 30, 2025\.** CloudieAI billing will now begin on **December 1, 2025.** Thank you for your understanding and for being a valued OIT Partner. If you continue to experience issues or have questions, please contact our support team at **support@oit.co**, and one of our technicians will be happy to assist.

Inbound CNAM Lookup Intermittently Not Returning Correct CID

Tue, 16 Sep 2025 14:14:58 +0000

Type: Incident

Duration: 21 days and 45 minutes

Affected Components:

Sep 29, 15:56:11 GMT+0
Identified - What Occurred: We have identified that the upstream CNAM database provider is intermittently providing incorrect Caller ID Name information after performing a CNAM dip. Who is Affected: All partners and clients. When It Began: 9:30 AM ET, 9/15/2025 Current Status: Bandwidth has internally escalated this with their engineers as well as with their new upstream CNAM DB provider. Workarounds: There are no known workarounds at this time. Next Steps: Bandwidth has requested that any new incorrect inbound CNAM lookups be provided to them. If you have any examples, please email [support@oit.co](mailto:support@oit.co) and provide the caller number, called number, date and time, along with the caller ID that was displayed and what it should have been. Next Update: We will provide an update when new information becomes available. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Oct 7, 14:59:56 GMT+0
Resolved - **What Occurred**: We have identified that the upstream CNAM database provider is intermittently providing incorrect Caller ID Name information after performing a CNAM dip. Who is Affected: All partners and clients. **When It Began:** 9:30 AM ET, 9-15-25 **Current Status:** * This is considered **Resolved.** * Bandwidth has informed us that after working with their upstream CNAM database provider they were able to correct the inbound CNAM discrepancies. * We have confirmed we are seeing proper inbound CNAM at this time. **Next Steps:** * If you continue to experience incorrect inbound CNAM, Bandwidth has requested that any new incorrect inbound CNAM lookups be provided to them. * If you have any examples please email [support@oit.co](mailto:support@oit.co) and provide the caller number, called number, date and time along with the caller ID that was displayed and what it should have been. **Next Update:** N/A.

Sep 16, 14:14:58 GMT+0
Investigating - What Occurred: We have identified that the upstream CNAM database provider is intermittently providing incorrect Caller ID Name information after performing a CNAM dip. Who is Affected: All partners and clients. When It Began: 9:30 AM ET, 9/15/2025 Current Status: Bandwidth has confirmed that the upstream CNAM/LIDB database provider is having a broad issue, and they are investigating internally. Workarounds: There are no known workarounds at this time. Next Update: We will provide an update when new information becomes available. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

TCR Campaign Management Services Currently Unavailable

Thu, 21 Aug 2025 15:13:08 +0000

Type: Incident

Duration: 3 hours and 17 minutes

Affected Components:

Aug 21, 18:30:32 GMT+0
Resolved - This incident is now considered **resolved**. We will continue to monitor for the next 24 hours. We appreciate your patience throughout this process. If you need additional support, please contact [**support@oit.co**](mailto:support@oit.co). .

Aug 21, 16:19:18 GMT+0
Identified - \*\*What Occurred:\*\* We are currently experiencing a service disruption affecting The Campaign Registry (TCR) platform. This impacts the ability to create new 10DLC campaigns, register new brands, or edit existing campaigns. \*\*Who is Affected:\*\* All partners and clients who need to create new TCR/10DLC campaigns, register new brands, or modify existing campaign configurations. \*\*When It Began:\*\* 9:31 AM ET, 8-21-25 \*\*Current Status:\*\* \* TCR has confirmed a platform-wide issue affecting campaign management functions \* OIT is actively working with TCR support to monitor the situation \* No updates have been provided by TCR at this time \* You can follow along for live updates from TCR at \[Campaign Registry Status\](https://status.campaignregistry.com/#) \*\*Workarounds:\*\* There are no workarounds available for campaign creation or editing at this time. Please plan accordingly for any urgent campaign needs. \*\*Next Steps:\*\* \* We recommend postponing any planned campaign creation or modifications until service is restored \* OIT will continue monitoring the situation and provide updates as information becomes available \*\*Next Update:\*\* 3:15 PM ET, 8-21-25.

Aug 21, 15:13:08 GMT+0
Identified - **What Occurred:** We are currently experiencing a service disruption affecting The Campaign Registry (TCR) platform. This impacts the ability to create new 10DLC campaigns, register new brands, or edit existing campaigns. **Who is Affected:** All partners and clients who need to create new TCR/10DLC campaigns, register new brands, or modify existing campaign configurations. **When It Began:** 9:31 AM ET, 8-21-25 **Current Status:** * TCR has confirmed a platform-wide issue affecting campaign management functions * OIT is actively working with TCR support to monitor the situation * No estimated time of resolution has been provided at this time **Workarounds:** There are no workarounds available for campaign creation or editing at this time. Please plan accordingly for any urgent campaign needs. **Next Steps:** * We recommend postponing any planned campaign creation or modifications until service is restored * OIT will continue monitoring the situation and provide updates as information becomes available **Next Update:** We will provide an update within 1 hour or when new information becomes available **Offline Services:** * TCR Campaign Creation * TCR Brand Registration * TCR Campaign Editing/Modifications **Degraded Services:** * None **Operational Services:** * SMS/MMS message sending and receiving (all existing campaigns continue to function normally) * All other messaging services * All voice services * All portal services **Important Note:** This outage does NOT affect your ability to send or receive messages. All existing registered campaigns continue to operate normally. We appreciate your patience throughout this process. If you need support, please contact [support@oit.co](mailto:support@oit.co). For more real-time status updates as well as discussion please join our Discord..

mFax Intermittent Inbound Fax Failures

Mon, 14 Jul 2025 16:38:38 +0000

Type: Incident

Duration: 1 day, 1 hour and 5 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Jul 14, 16:38:38 GMT+0
Investigating - At 11:45 AM ET, the mFax vendor reported a subset of inbound numbers failing with a "no fax tone detected" error. This is due to one of the vendor's upstream telecom providers experiencing intermittent failures. What Is Affected: mFax When It Began: 11:45 AM ET June 14, 2025 Current Status: The vendor is currently investigating. Next Steps: No action required. Next Update: 1:35 PM ET June 14, 2025.

Jul 14, 17:30:30 GMT+0
Investigating - What Is Affected: mFax When It Began: 11:45 AM ET June 14, 2025 Current Status: The vendor is currently investigating. Next Steps: No action required. Next Update: 2:35 PM ET June 14, 2025.

Jul 14, 18:40:10 GMT+0
Monitoring - **Current Status:** A fix has been implemented with successful faxes received. **Next Steps:** We will continue to monitor for the next 24 hours. **Next Update:** 2:35 PM ET June 15, 2025.

Jul 15, 17:43:11 GMT+0
Resolved - As of 2:58am, July 15, 2025 mfax is showing the implemented fix performed by their telecom provider is successful and all inbound faxes are working as intended. After 24 hours of monitoring with no additional inbound fax failures, This incident is now considered resolved..

GRR Inbound Call Failures

Tue, 8 Jul 2025 20:05:24 +0000

Type: Incident

Duration: 23 hours and 34 minutes

Affected Components:

Jul 8, 20:05:24 GMT+0
Monitoring - \*\*What Occurred:\*\* At 2:37 PM ET, inbound and outbound calls to GRR began receiving a 503 error, causing them to fail. \*\*What Is Affected:\*\* Inbound and outbound calls to the GRR server \*\*When It Began:\*\* 2:37 PM ET on July 8, 2025 \*\*Next Update:\*\* July 9, 2025 at 4:00 PM ET \*\*Current Status:\*\* We have restarted the NMS service on the GRR server and are showing calls processing successfully again. \*\*Next Steps:\*\* \* We will continue to monitor to ensure that calls continue to process successfully. We will also continue investigating the root cause of the failure. \* Devices that were registered on GRR may need to be restarted after the NMS service restart took place. \*\*Next Update:\*\* July 9, 2025 at 4:00 PM ET.

Jul 9, 19:38:59 GMT+0
Resolved - \*\*What Occurred:\*\* At 2:37 PM ET, all calls on the GRR server began to fail. \*\*What was Affected:\*\* \* Inbound and Outbound Calls on GRR \*\*When It Began\*\*: 7/8/2025 2:37 PM ET \*\*Current Status\*\*: This incident is now Resolved. \*\*Next Steps:\*\* Major Incident Report will be available within 48 business hours..

Jul 8, 20:10:22 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jul 11, 20:13:58 GMT+0
Postmortem - Major Incident Report: [2025-07-08 Inbound and Outbound call failures on GRR](https://voipdocs.io/announcements/-2025-07-08-registration-failure-on-grr).

Cloudflare Outage

Thu, 12 Jun 2025 19:35:14 +0000

Type: Incident

Duration: 3 hours and 44 minutes

Affected Components:

Jun 12, 19:35:14 GMT+0
Monitoring - Cloudflare experienced a broad service outage that affected the mFax service. \*\*What Is Affected:\*\* MFax \*\*When It Began:\*\* 1:30 PM ET June 12, 2025 \*\*Current Status:\*\* As of 3:12 pm ET, Cloudflare is showing services are recovering, while mFax services may still experience intermittent "internal server" error messages until fully restored. \*\*Next Steps:\*\* N/A \*\*Next Update:\*\* 4:30PM ET June 13, 2025.

Jun 12, 23:18:59 GMT+0
Resolved - Notice: Cloudflare Outage What Is Affected: MFax When It Began: 1:30 PM ET June 12, 2025 Current Status: Resolved - Cloudflare identified the cause to be with one of their upstream vendors, who as of 4:00 PM ET has fully restored services on their end. mFax is showing all fax queues are clearing and services have been restored. This incident is now considered Resolved. Next Steps: \* Major Incident Report will be available within 48 hours. Next Update: 4:30PM ET June 13, 2025 Operational Services: All.

Registration Failure on GRR

Thu, 5 Jun 2025 19:16:02 +0000

Type: Incident

Duration: 22 hours and 36 minutes

Affected Components:

Jun 5, 19:16:19 GMT+0
Monitoring - .

Jun 5, 19:16:02 GMT+0
Monitoring - At 2:26 PM ET, we received a notification from our NOC monitoring that the NMS service which handles registration and call processing on GRR crashed. Active calls on this server did drop, and devices on GRR failed over to ATL successfully. **What Is Affected:** * Device Registration on GRR * Active Calls on GRR **When It Began:** 2:26 PM ET **Current Status:** The NMS service on GRR is back online as of 2:29 PM ET, and registration for all devices returned to GRR by 2:39 PM ET. At this time, all services on GRR are functioning as expected. **Next Steps:** We will be monitoring GRR for 24 hours per our major incident policy while we continue to investigate the root cause. If additional outages occur, we will manually redirect devices & calls on GRR to ATL until the problem is resolved. **Next Update:** 6/6/25 3:00 PM ET.

Jun 6, 17:51:33 GMT+0
Resolved - At 2:26 PM ET, we received a notification from our NOC monitoring that the NMS service, which handles registration and call processing on GRR crashed. Active calls on this server did drop, and devices on GRR failed over to ATL successfully. **What was Affected:** * Device Registration on GRR * Active Calls on GRR **When It Began:** 06/05/2025 2:26 PM ET **Current Status**: This incident is now **resolved.** **Next Steps:** * Major Incident Report is now available * MIR report: .

Loss of Communication to GRR

Wed, 4 Jun 2025 15:18:44 +0000

Type: Incident

Duration: 1 day, 1 hour and 36 minutes

Affected Components:

Jun 4, 15:18:44 GMT+0
Investigating - At 10:30am ET, our monitoring system alerted us to the GRR server being unreachable for two minutes, resulting in device registrations and inbound calls to failover to other servers. Shortly after, the same datacenter lost communication again. We are investigating quickly and will determine if we need to close GRR temporarily. Updates to follow What Is Affected: GRR Voice When It Began: 10:30 AM ET Current Status: We are investigating quickly and will determine if we need to close GRR temporarily. Next Steps: Updates to Follow Next Update: 12:15 PM ET.

Jun 4, 16:22:22 GMT+0
Monitoring - What Is Affected: GRR Server When It Began: 10:30 AM ET Current Status: We have determined that the loss of traffic was due to a degraded circuit. The offending circuit was removed from the routing profile. Traffic has remained stable since the change. Moving to the monitoring stage. Next Steps: Continue to monitor Next Update: 6/5/2025 1:15 PM ET Degraded Services: None Operational Services: All.

Jun 4, 21:18:33 GMT+0
Monitoring - **Current Status:** At this time we continue to see stability on GRR's connections. The datacenter will be performing maintenance and repair to the MPLS configuration tonight at 2AM and is expected to be completed before 8AM. No downtime or service interruptions are expected. Our NOC will be monitoring throughout the monitoring phase. **Next Steps:** * Continue to monitor * Maintenance: Tonight, 2:00 - 8:00 AM ET **Next Update**: 1:15 PM ET 6/25/2025 **Degraded Services**: None **Operational Services:** All.

Jun 5, 16:55:00 GMT+0
Resolved - At 10:30am ET, our monitoring system alerted us to the GRR server being unreachable for two minutes, resulting in device registrations and inbound calls to failover to other servers. Shortly after, the same datacenter lost communication again. **What was Affected:** GRR Server **When It Began:** 10:30 AM ET **Current Status:** * We continue to see stability on GRR's connections after 24 hours of monitoring. * This incident is now considered **Resolved**. **Next Steps:** * Major Incident Report will be available within 48 hours..

Jun 6, 16:17:09 GMT+0
Resolved - **MIR now available for Loss of Communication to GRR Server** At 10:30am ET, our monitoring system alerted us to the GRR server being unreachable for two minutes, resulting in device registrations and inbound calls to failover to other servers. Shortly after, the same datacenter lost communication again. **What Was Affected:** GRR Server **When It Began:** 6/04/2025 10:30 AM ET **Resolution:** * The degraded circuit was immediately removed from the routing profile to prevent further instability * Enhanced monitoring was implemented during the recovery period to ensure sustained stability * **The Major Incident Report is now available:** .

Websocket Connection Failure on GRR and LAS

Fri, 30 May 2025 16:04:44 +0000

Type: Incident

May 30, 16:04:44 GMT+0
Identified - At 11:06 AM ET, we were alerted by our monitoring tools that WSS connections on GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection. \*\*What Is Affected\*\*: All SNAPmobile Web Connections on GRR & LAS \*\*When It Began:\*\* 11:06AM ET \*\*Current Status:\*\* We have identified the cause and are awaiting vendor confirmation to implement a fix. \*\*Next Steps\*\*: No next steps for partners \*\*Next Update\*\*: 12:06PM ET.

Jun 3, 15:25:40 GMT+0
Resolved - \*\*MIR now available for Websocket Connection Failure on GRR and LAS\*\* At 11:06AM ET we were alerted by our monitoring tools that WSS connections on GRR, LAS, IAD, and PHX were failing. SNAPmobile Web uses WSS for the SIP connection. \*\*What was Affected:\*\* All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX \*\*When It Began\*\*: 11:06AM ET 05/06/2025 \*\*Resolution:\*\* \* \*\*Our vendor resolved an SSL issue with the affected FQDNs on 05/31/2025\*\* \* \*\*Major Incident Report\*\* is now available: .

May 30, 16:44:04 GMT+0
Identified - What Is Affected: All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX When It Began: 11:06 AM ET Current Status: * We have temporarily redirected all WSS traffic to ATL, which is confirmed to be working. In the meantime, our engineers will continue to work on a permanent resolution. Next Steps: * Users will need to completely close SNAPmobile Web and reopen it to ensure a new connection. If the problem persists, please clear your browser cache and test again. If, after clearing your cache, you still cannot connect, please submit a ticket to [support@oit.co](mailto:support@oit.co) Next Update: 2:06 PM ET.

May 31, 18:53:04 GMT+0
Resolved - This incident has been resolved..

May 30, 17:50:43 GMT+0
Monitoring - **What Is Affected:** All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX **When It Began:** 11:06AM ET **Current Status**: * After working with vendor support, we have successfully applied a fix to resolve WSS connections failing on LAS, GRR, IAD, & PHX. * Per our internal policy, we will keep all WSS traffic redirected to ATL while we continue to monitor for 24 hours. This will prevent further downtime if the problem reoccurs. **Next Steps:** * Users will need to completely close SNAPmobile Web and reopen it to ensure a new connection. If the problem persists, please clear your browser cache and test again. If after clearing your cache, you still cannot connect, please submit a ticket to support@oit.co * We understand that some users may experience poor call quality or dropped calls on ATL. If you experience any of these, please email support@oit.co with call examples or call traces so that we can investigate and potentially move affected clients back to their respective cores in advance. **Next Update:** 5/31/25 2:00 PM ET.

May 31, 18:56:52 GMT+0
Resolved - At 11:06AM ET we were alerted by our monitoring tools that WSS connections on GRR, LAS, IAD, and PHX were failing. SNAPmobile Web uses WSS for the SIP connection. **What Is Affected:** All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX **When It Began:** 11:06AM ET **Current Status**: * **This incident is considered Resolved.** * **Our vendor resolved an SSL issue with the affected FQDNs** **Next Steps**: * Major Incident Report will be available within 48 hours. **Next Update**: N/A **Offline Services: N/A** **Degraded Services:** N/A.

Websocket Connection Failure on ATL, GRR and LAS

Fri, 25 Apr 2025 22:53:35 +0000

Type: Incident

Duration: 2 hours and 30 minutes

Affected Components:

Apr 25, 22:53:35 GMT+0
Identified - At 6:19PM ET we were alerted by our monitoring tools that WSS connections on ATL, GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection. **What Is Affected**: All SNAPmobile Web Connections on ATL, GRR & LAS **When It Began**: 6:19PM ET **Current Status**: * We have identified a potential cause for and are awaiting vendor confirmation to implement a fix. **Next Steps**: * No next steps for partners **Next Update**: 7:45PM ET **Offline Services**: * SNAPmobile Web Connections on ATL, LAS & GRR **Degraded Services**: * None.

Apr 25, 23:35:00 GMT+0
Identified - At 6:19PM ET we were alerted by our monitoring tools that WSS connections on ATL, GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection. What Is Affected: All SNAPmobile Web Connections on ATL, GRR & LAS When It Began: 6:19PM ET Current Status: We actively engaged with our vendor and awaiting to confirm the issue and implement a fix. Next Steps: No next steps for partners. Next Update: 8:45PM ET Offline Services: SNAPmobile Web Connections on ATL, LAS & GRR Degraded Services: None.

Apr 26, 00:43:37 GMT+0
Identified - At 6:19PM ET we were alerted by our monitoring tools that WSS connections on ATL, GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection. **What Is Affected**: All SNAPmobile Web Connections on ATL, GRR & LAS **When It Began**: 6:19PM ET **Current Status**: * We have confirmed that SNAPmobile Web on GRR & LAS cores are registering successfully. * We are still working with our vendor to resolve an SSL issue relating to our ATL core. **Next Steps**: * If your SNAPmobile Web phones were previously offline on GRR or LAS, please refresh your browser, or relaunch the SNAPmobile Web app to regain registration. **Next Update**: 9:45PM ET **Offline Services**: * SNAPmobile Web Connections on ATL **Degraded Services**: * None.

Apr 26, 01:23:17 GMT+0
Resolved - At 6:19PM ET we were alerted by our monitoring tools that WSS connections on ATL, GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection.**What Is Affected**: All SNAPmobile Web Connections on ATL, GRR & LAS**When It Began**: 6:19PM ET**Current Status**: * We have confirmed that SNAPmobile Web Registrations have been resolved on all cores. **Next Steps**: * Major Incident Report will be available within 48 business hours. **Next Update**: N/A **Offline Services**: N/A **Degraded Services**: N/A.

Websocket Connection Failure on GRR and LAS

Wed, 23 Apr 2025 12:48:07 +0000

Type: Incident

Duration: 2 hours

Affected Components:

Apr 23, 12:48:07 GMT+0
Investigating - **What Occurred**: At 7:42AM ET we were alerted by our monitoring tools that WSS connections on GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection. We were able to confirm this within 15 minutes of the alert and identify a possible cause thereafter. **What Is Affected**: All SNAPmobile Web Connections on GRR & LAS **When It Began**: 7:42AM ET **Current Status**: * We have identified a potential cause for this, and are awaiting vendor confirmation to implement a fix. **Next Steps**: * No next steps for partners **Next Update**: 9:45AM ET **Offline Services**: * SNAPmobile Web Connections on LAS & GRR **Degraded Services**: * None.

Apr 23, 13:50:19 GMT+0
Investigating - **What Is Affected**: All SNAPmobile Web Connections on GRR & LAS **When It Began**: 7:42AM ET **Current Status**: * The attempted resolution did not resolve the connections. We are working with our vendor and investigating further. **Next Steps**: * If web phone connectivity is vital and it is not failing over, please input a support case by emailing [support@oit.co,](mailto:support@oit.co) and a technician can reroute your connections to ATL temporarily **Next Update**: 10:45AM ET **Offline Services**: * SNAPmobile Web Connections on LAS & GRR **Degraded Services**: * None.

Apr 23, 14:48:35 GMT+0
Resolved - **What was Affected**: All SNAPmobile Web Connections on GRR & LAS **When It Began**: 7:42AM ET **Current Status**: * **This incident is considered Resolved** * Our vendor resolved an SSL issue with the affected FQDNs **Next Steps**: * Major Incident Report will be available within 48 hours. **Next Update**: N/A **Offline Services:** N/A **Degraded Services:** N/A.

4/14/2025 Call Recording Failure

Mon, 14 Apr 2025 15:31:29 +0000

Type: Incident

Duration: 21 hours and 44 minutes

Affected Components: ,

Apr 15, 13:15:51 GMT+0
Resolved - \*\*Current Status:\*\* \* \*\*This incident is considered Resolved\*\* \* After testing and confirmation, all call recordings on GRR & LAS are now available, and call recordings on ATL are available \*\*except between 4/14 2 AM and 4/15 3:30 AM ET.\*\* \* If a specific call is needed from this time period, you can submit a ticket to \[support@oit.co\](mailto:support@oit.co) within the \*\*next 6 calendar days\*\* and we can pull that call recording from voipmonitor for you. \*\*Next Steps:\*\* \* Major Incident Report will be available within 48 hours. \*\*Next Update:\*\* N/A.

Apr 15, 07:25:29 GMT+0
Monitoring - \*\*Update: Monitoring: 4/14/25 Call Recording Failure\*\* \*\*What Is Affected\*\*: Call Recording availability across affected tenants \*\*When It Began\*\*: 2:00 AM, April 14, 2025, ET \*\*Current Status\*\*: \* As of 2:45 AM ET on April 15th, call recordings for calls on ATL placed after tonight's maintenance window are showing in the Manager Portal. \*\*Next Steps\*\*: \* Call recordings for calls on ATL placed throughout the duration of the incident (2 AM ET on April 14th through 1 AM ET on April 15th) can be retrieved by submitting a support ticket to \[support@oit.co\](mailto:support@oit.co). \* We will continue to monitor for the next 48 hours to ensure call recording functionality remains stable. \*\*Next Update\*\*: 9 AM ET, April 16th, 2025 \*\*Offline Services\*\*: \* None \*\*Degraded Services\*\*: \* None \*\*Operational Services\*\*: \* Inbound Calling – ATL \* Outbound Calling - ATL \* Inbound Calling – GRR \* Outbound Calling - GRR \* Inbound Calling – LAS \* Outbound Calling - LAS \* API \* Fax \* Messaging \* Teammate Connector \* Mobile X \* Mobile Apps \* Integrations We appreciate your patience throughout this process. If you need support, please contact \[support@oit.co\](mailto:support@oit.co). For more real time status updates as well as discussion please join our Discord (Not official support).

Apr 14, 15:31:29 GMT+0
Investigating - At approximately 2:00 AM ET on April 14th, 2025, we completed maintenance on our call recording servers to migrate them to the new data centers in IAD and PHX. At 10:20 AM ET, we identified an issue where call history is not displaying call recordings. Remote call recording storage may also be unavailable, but no other functionality appears to be impacted at this time. --- \*\*What Is Affected:\*\* \* \*\*Call Recording\*\* availability across affected tenants --- \*\*When It Began:\*\* 2:00 AM, April 14, 2025, ET --- \*\*Current Status:\*\* \* \*\*\\\[10:45 AM ET, April 14\\\]\*\* Issue was confirmed by support team; it is currently under investigation by engineering \* No known workarounds at this time \* Engineering has been engaged to review recording service logs and assess potential causes --- \*\*Next Steps:\*\* \* \*\*\\\[10:45 AM ET, April 14\\\]\*\* The Engineering team is reviewing logs and service dependencies \* Partners do not need to take action at this time \* We will provide an update once the root cause is identified, or a workaround is available --- \*\*Next Update:\*\* 12:30 PM, April 14, 2025, ET --- \*\*Offline Services:\*\* \* Call Recording --- \*\*Degraded Services:\*\* \* None.

Apr 14, 16:28:31 GMT+0
Investigating - **Current Status:** We've engaged vendor support to develop a short-term solution while we determine the root cause. --- **Next Steps:** * Partners do not need to take action at this time * We will provide an update for the next steps once the root cause is identified or a workaround is available --- **Next Update:** 1:30 PM, April 14, 2025, ET.

Apr 14, 17:46:40 GMT+0
Identified - **Current Status:** * Call recordings are now available for LAS and GRR. * This includes past, current and future call recordings, and recordings that took place during the incident timeline. --- **Next Steps:** * We are still investigating, as ATL call recordings are still unavailable at this time. Call recordings for ATL are not accessible, this includes active/future call recordings. * Partners do not need to take action at this time --- **Next Update:** 2:30 PM, April 14, 2025, ET.

Apr 14, 19:28:43 GMT+0
Identified - **Current Status:** \-Call recordings are available for LAS and GRR. \-This includes past, current, and future call recordings, including recordings that took place during the incident timeline. **Next Steps:** \-We continue to troubleshoot ATL with the help of our vendors. Call recordings are still unavailable for past, active, and future recordings on ATL at this time. \-Partners do not need to take action **Next Update:** 4:30 PM, April 14, 2025, ET.

Apr 14, 20:31:32 GMT+0
Identified - **Current Status:** \-Call recordings are available for LAS and GRR. \-This includes past, current, and future call recordings, including recordings that took place during the incident timeline. **Next Steps:** \-We continue to troubleshoot ATL with vendor support. Call recordings are still unavailable for past, active, and future recordings on ATL at this time. \-Partners do not need to take action **Next Update:** 5:30 PM, April 14, 2025, ET.

Apr 14, 18:29:38 GMT+0
Identified - **Current Status:** * Call recordings are available for LAS and GRR. * This includes past, current and future call recordings, and recordings that took place during the incident timeline. --- **Next Steps:** * We are still investigating ATL call recordings. ATL recordings are still unavailable at this time, including active/future call recordings. * Partners do not need to take action at this time --- **Next Update:** 3:30 PM, April 14, 2025, ET ---.

Apr 14, 21:30:29 GMT+0
Identified - We will be performing emergency maintenance on our ATL server on April 15th, at 1:00 AM ET, to resolve the call recording failures on ATL. During this time, there will be a brief window where calls and device registration will be rerouted to alternate servers. **Maintenance Start:** 1:00 AM ET, April 15th, 2025 **Estimated Time to Complete:** 4:00 AM ET, April 15th, 2025 (3 Hours) **Offline Services** Inbound Calling – ATL Outbound Calling -ATL **Degraded Services** None **Operational Services** Inbound Calling – GRR Outbound Calling -GRR Inbound Calling – LAS Outbound Calling - LAS API Fax Messaging Teammate Connector Mobile X Mobile Apps Integrations We appreciate your patience throughout this process. For additional support, please contact [support@oit.co](mailto:support@oit.co)..

API outage

Mon, 24 Feb 2025 21:26:40 +0000

Type: Incident

Duration: 3 minutes

Feb 24, 21:26:40 GMT+0
Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service..

Feb 24, 21:29:40 GMT+0
Resolved - API is now operational! This update was created by an automated monitoring service..

API outage

Mon, 24 Feb 2025 19:31:04 +0000

Type: Incident

Duration: 2 minutes

Feb 24, 19:31:04 GMT+0
Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service..

Feb 24, 19:32:39 GMT+0
Resolved - API is now operational! This update was created by an automated monitoring service..