UCaaS Status Page - Notice history

All systems operational

100% - uptime

Ashburn (IAD) Voice - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Atlanta (ATL) Voice - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Grand Rapids (GRR) Voice - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Las Vegas (LAS) Voice - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Phoenix (PHX) Voice - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Messaging (SMS/MMS) - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Native Fax - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025
100% - uptime

API - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Call Recording (IAD) - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 99.047%
Feb 2025
Mar 2025
Apr 2025

Call Recording (PHX) - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 99.047%
Feb 2025
Mar 2025
Apr 2025

Call Recording (ATL) - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 99.999%
Feb 2025
Mar 2025
Apr 2025

Device Provisioning (NDP) - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Manager Portal - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Manager Portal Pro - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

SNAPmobile - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

SNAPmobile Web - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 99.720%
Feb 2025
Mar 2025
Apr 2025

VoIPMonitor (QoS) - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

CloudieConnect - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

CloudieAI - Operational

100% - uptime
Feb 2025 · 100.00%Mar · 100.00%Apr · 100.00%
Feb 2025
Mar 2025
Apr 2025

Notice history

Apr 2025

Websocket Connection Failure on ATL, GRR and LAS
  • Resolved
    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 & LASWhen It Began: 6:19PM ETCurrent 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

  • Update
    Update

    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

  • Update
    Update

    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

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

Websocket Connection Failure on GRR and LAS
  • Resolved
    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

  • Update
    Update

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

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

4/14/2025 Call Recording Failure
  • Resolved
    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
  • Monitoring
    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)
  • Update
    Update

    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.

  • Update
    Update

    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

  • Update
    Update

    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

  • Update
    Update

    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


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

  • Update
    Update

    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

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

Mar 2025

No notices reported this month

Feb 2025 to Apr 2025

Next