UCaaS Status Page - Notice history

All systems operational

100% - uptime

Ashburn (IAD) Voice - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Atlanta (ATL) Voice - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Phoenix (PHX) Voice - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Messaging (SMS/MMS) - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Native Fax - Operational

99% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 98.414%
Apr 2026
May 2026
Jun 2026
100% - uptime

API - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Call Recording (IAD) - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Call Recording (PHX) - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Call Recording (ATL) - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Device Provisioning (NDP) - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Manager Portal - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Manager Portal Pro - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

SNAPmobile - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

SNAPmobile Web - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

VoIPMonitor (QoS) - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

CloudieConnect - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 99.850%
Apr 2026
May 2026
Jun 2026

CloudieAI - Operational

100% - uptime
Apr 2026 · 100.00%May · 100.00%Jun · 100.00%
Apr 2026
May 2026
Jun 2026

Notice history

Jun 2026

NativeFax Inbound and Outbound Fax Failures
  • Update
    Update

    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.

  • Monitoring
    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

  • Update
    Update

    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

  • Identified
    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

  • Investigating
    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

  • Update
    Update

    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

  • Identified
    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

  • Update
    Update

    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

  • Investigating
    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

  • Update
    Update

    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.

  • Resolved
    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

  • Update
    Update

    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

  • Update
    Update

    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

  • Update
    Update

    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

  • Monitoring
    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

  • Update
    Update

    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

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

CloudieConnect Server Maintenance - 6/10/26
  • Completed
    June 10, 2026 at 6:30 AM
    Completed
    June 10, 2026 at 6:30 AM
    Maintenance has completed successfully
  • In progress
    June 10, 2026 at 4:30 AM
    In progress
    June 10, 2026 at 4:30 AM
    Maintenance is now in progress
  • Planned
    June 10, 2026 at 4:30 AM
    Planned
    June 10, 2026 at 4:30 AM

    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.

ATL Server General Maintenance – 6/4/26
  • Completed
    June 04, 2026 at 6:35 AM
    Completed
    June 04, 2026 at 6:35 AM

    Maintenance has completed successfully.

  • In progress
    June 04, 2026 at 6:00 AM
    In progress
    June 04, 2026 at 6:00 AM
    Maintenance is now in progress
  • Planned
    June 04, 2026 at 6:00 AM
    Planned
    June 04, 2026 at 6:00 AM

    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.

CloudieConnect Servers Failing to Register
  • Postmortem
    Postmortem

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

  • Update
    Update

    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.

  • Resolved
    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

  • Investigating
    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

May 2026

Fax Server Maintenance - 5/14/26
  • Completed
    May 15, 2026 at 7:00 AM
    Completed
    May 15, 2026 at 7:00 AM
    Maintenance has completed successfully
  • In progress
    May 15, 2026 at 3:00 AM
    In progress
    May 15, 2026 at 3:00 AM
    Maintenance is now in progress
  • Planned
    May 15, 2026 at 3:00 AM
    Planned
    May 15, 2026 at 3:00 AM

    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.

Apr 2026

Urgent IAD Maintenance 4/30/26
  • Completed
    April 30, 2026 at 1:30 PM
    Completed
    April 30, 2026 at 1:30 PM
    Maintenance has completed successfully
  • In progress
    April 30, 2026 at 11:30 AM
    In progress
    April 30, 2026 at 11:30 AM
    Maintenance is now in progress
  • Planned
    April 30, 2026 at 11:30 AM
    Planned
    April 30, 2026 at 11:30 AM

    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.

Loss Of Registration and Dropped Calls PHX
  • Resolved
    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. For more real time status updates as well as discussion please join our Discord (Not official support).

  • Monitoring
    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. For more real time status updates as well as discussion please join our Discord (Not official support).

Urgent PHX Maintenance 4/8/26
  • Completed
    April 09, 2026 at 3:04 AM
    Completed
    April 09, 2026 at 3:04 AM
    Maintenance has completed successfully
  • In progress
    April 09, 2026 at 12:30 AM
    In progress
    April 09, 2026 at 12:30 AM
    Maintenance is now in progress
  • Planned
    April 09, 2026 at 12:30 AM
    Planned
    April 09, 2026 at 12:30 AM

    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.

Apr 2026 to Jun 2026

Next