Ashburn (IAD) Voice - Operational
Ashburn (IAD) Voice
Atlanta (ATL) Voice - Operational
Atlanta (ATL) Voice
Phoenix (PHX) Voice - Operational
Phoenix (PHX) Voice
Toronto (YYZ) Voice - Operational
Toronto (YYZ) Voice
Messaging (SMS/MMS) - Operational
Messaging (SMS/MMS)
Native Fax - Operational
Native Fax
E911 - Operational
E911
API - Operational
API
Call Recording (IAD) - Operational
Call Recording (IAD)
Call Recording (PHX) - Operational
Call Recording (PHX)
Call Recording (ATL) - Operational
Call Recording (ATL)
Call Recording (YYZ) - Operational
Call Recording (YYZ)
Device Provisioning (NDP) - Operational
Device Provisioning (NDP)
Manager Portal - Operational
Manager Portal
Manager Portal Pro - Operational
Manager Portal Pro
SNAPmobile - Operational
SNAPmobile
SNAPmobile Web - Operational
SNAPmobile Web
VoIPMonitor (QoS) - Operational
VoIPMonitor (QoS)
CloudieConnect - Operational
CloudieConnect
CloudieAI - Operational
Notice history
View current statusOct 2026
- Completed · October 22, 2026 at 12:15 AMUTCMaintenance has completed successfully.
- In progress · October 22, 2026 at 12:00 AMUTCMaintenance is now in progress
- Planned · October 21, 2026 at 11:48 PMUTC
Two critical PHP security vulnerabilities (CVE-2026-109618 and CVE-2026-109619) were published today. Tonight we are applying the PHP security update to our remaining Atlanta (ATL) servers, starting with our QoS monitoring server and then the ATL core server. The work updates PHP and restarts the web service. We tested this process on our test servers with no impact, and we do not expect calls, device registration, the Manager Portal or SNAPmobile Web to be affected. Call quality (QoS) data shown in the Manager Portal stays available. While the QoS server's web service restarts, the direct QoS pages and direct sign-in at qos.ucaasnetwork.com may be unavailable for a moment. No action is needed from partners.
Maintenance Starts: Wed Oct 21, 2026, 8:00 PM ET
Maintenance Ends: Wed Oct 21, 2026, 8:30 PM ET
Offline Services: None expected
Degraded Services: VoIPMonitor (QoS): direct QoS pages and direct sign-in at qos.ucaasnetwork.com may be briefly unavailable while the web server restarts. QoS data in the Manager Portal is not affected.
We appreciate your patience throughout this process.If you need additional support, please contact support@oit.co.
- Completed · October 15, 2026 at 4:21 AMUTC
Maintenance has completed successfully.
- In progress · October 15, 2026 at 3:00 AMUTCMaintenance is now in progress
- Planned · October 07, 2026 at 4:04 PMUTC
We will be performing scheduled maintenance on our Native Fax server on October 14th, 2026, at 11:00 PM ET. There will be an interruption in the delivery and sending of faxes while maintenance is performed.
What to Expect and Action Needed After Maintenance:
Inbound faxes: Senders will receive a busy signal during maintenance. They will need to resend after service is restored.
Outbound faxes from the portal or email: These won't go through during maintenance. Please resend them after service is restored.
Outbound faxes from a fax machine connected through a fax adapter (ATA): No action needed. Faxes will queue and send automatically once maintenance is complete.
We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.
Sep 2026
- Completed · September 22, 2026 at 9:24 PMUTC
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.
- Planned · September 22, 2026 at 2:36 PMUTC
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.
- Completed · September 22, 2026 at 7:00 AMUTCMaintenance has completed successfully
- In progress · September 22, 2026 at 4:00 AMUTCMaintenance is now in progress
- Planned · September 21, 2026 at 9:44 PMUTC
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.
- Postmortem · UTC
This incident was resolved on September 12th at 12:00 PM ET, and the Major Incident Report (MIR) is now available.
Major Incident Report (MIR): https://voipdocs.io/announcements/-2026-09-11-fax-port-server-failures-resolved
- Resolved · UTC
What Occurred: At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: September 11th, 2026, at 10:21 AM ET
Current Status:
24 hours of monitoring showed no additional failures.
This incident is considered resolved.
Next Steps:
A Major Incident Report will be released within 72 business hours.
- Monitoring · UTC
What Occurred: At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes were failing.
What was Affected: Inbound and Outbound faxes on the Native Fax platform are failing.
When it began: September 11th, 2026, at 10:21 AM ET
Current Status:
We have successfully identified and addressed the root cause for the fax failures.
At this time, we have restored service to the port server and are seeing both inbound and outbound faxes completing successfully.
We will continue to monitor and observe server stability for the next 24 hours.
Next Update: September 12th, 2026, at 1:45 PM ET
- Update · UTC
What Occurred: At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the Native Fax platform are failing.
When it began: September 11th, 2026, at 10:21 AM ET
Current Status: We are working with our vendor to restore fax, isolate the root cause, and restore services as quickly as possible.
Next Update: September 11th, 2026, at 1:45 PM ET
- Update · UTC
What Occurred: At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the Native Fax platform are failing.
When it began: September 11th, 2026, at 10:21 AM ET
Current Status: Inbound and outbound faxes began failing again at 11:39 AM ET. We are working to resolve this issue as quickly as possible.
Next Update: September 11th, 2026, at 12:45 PM ET
- Update · UTC
What Occurred: At approximately 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: September 11th, 2026, at 10:21 AM ET
Current Status: We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.
Next Update: September 11th, 2026, at 12:00 PM ET
- Identified · UTC
What Occurred: At 10:21 AM ET on September 11th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: September 11th, 2026 at 10:21 AM ET
Current Status: We identified the root cause as a failure of the fax port server and working to restore service.
Next Update: September 11th, 2026 at 11:30 AM ET
- Completed · September 11, 2026 at 7:00 AMUTCMaintenance has completed successfully
- In progress · September 11, 2026 at 3:00 AMUTCMaintenance is now in progress
- Planned · September 02, 2026 at 8:22 PMUTC
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.
- Completed · September 10, 2026 at 8:00 AMUTCMaintenance has completed successfully
- In progress · September 10, 2026 at 4:00 AMUTCMaintenance is now in progress
- Planned · September 03, 2026 at 4:29 PMUTC
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.
Aug 2026
- Completed · August 21, 2026 at 7:00 AMUTCMaintenance has completed successfully
- In progress · August 21, 2026 at 3:00 AMUTCMaintenance is now in progress
- Planned · August 14, 2026 at 5:13 PMUTC
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.
- Postmortem · UTC
This incident was resolved on August 21st at 5:15 PM ET, and the Major Incident Report (MIR) is now available.
Major Incident Report (MIR): https://voipdocs.io/announcements/2026-08-19-nativefax-inbound-and-outbound-faxing-failure-resolved
- Resolved · UTC
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.
What was Affected: Inbound and Outbound faxes on the NativeFax platform
When it began: August 19th, 2026, at 3:21 PM ET
Current Status:
After 24 hours of monitoring and observing server stability, we are considering this incident resolved.
The MIR will be provided within 48 business hours.
- Monitoring · UTC
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status: We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.
Next Update: August 21st, 2026, at 5 PM ET
- Update · UTC
Identified
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status:
We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.
At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.
At 4:46 PM ET, on August 20th, 2026, the port server service was restored.
At 6:56 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.
We're continuing to work on bringing the port server service back online, alongside the vendor's engineers. Further updates to follow as they're available.
Next Update: August 20th, 2026, at 10:30 pm ET
- Identified · UTC
Identified
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status:
We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.
At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.
At 4:46 PM ET, on August 20th, 2026, the port server service was restored.
At 6:56 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.
We are actively working to restore service and will provide further details as they become available.
Next Update: August 20th, 2026, at 8:45 pm ET
- Monitoring · UTC
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status:
We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.
At 3:51 PM ET, on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.
As of 4:35 PM ET, we have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.
Next Update: August 21st, 2026, at 4:15 pm ET
- Identified · UTC
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes were failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status:
We identified the root cause as a failure of the fax port server and restored service at 6:00 PM ET on August 19th, 2026.
At 3:51 PM ET on August 20th, 2026, the port server service crashed again, and inbound/outbound faxes began to fail.
We are actively working to restore service and will provide further details as they become available.
Next Update: August 20th, 2026, at 5:15 pm ET
- Monitoring · UTC
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status: We have successfully restored service to the port server and are seeing both inbound and outbound faxes completing successfully. We will continue to run tests and monitor to ensure stability.
Next Update: August 20th, 2026, at 3:30 pm ET
- Identified · UTC
What Occurred: At approximately 4:47 PM ET on August 19th, 2026, we became aware that inbound and outbound faxes are failing.
What is Affected: Inbound and Outbound faxes on the NativeFax platform are failing.
When it began: August 19th, 2026, at 3:21 PM ET
Current Status: We have identified the root cause, a failure of the fax port server, and are currently working to restore service.
Next Update: August 19th, 2026 at 6:00pm ET