UCaaS Status Page - Notice history

All systems operational

100% - uptime

Ashburn (IAD) Voice - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Atlanta (ATL) Voice - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Phoenix (PHX) Voice - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Messaging (SMS/MMS) - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Native Fax - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025
100% - uptime

API - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Call Recording (IAD) - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Call Recording (PHX) - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Call Recording (ATL) - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Device Provisioning (NDP) - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Manager Portal - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Manager Portal Pro - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

SNAPmobile - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

SNAPmobile Web - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

VoIPMonitor (QoS) - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

CloudieConnect - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

CloudieAI - Operational

98% - uptime
Sep 2025 · 100.00%Oct · 94.500%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

Notice history

Nov 2025

No notices reported this month

Oct 2025

Avanan/AWS Outage
  • Resolved
    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, success@oit.co, porting@oit.co, billing@oit.co, sales@oit.co, and 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

  • Identified
    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, success@oit.co, porting@oit.co, billing@oit.co, sales@oit.co, and 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.

CloudieAI – Call Transcription and Sentiment not populating after enablement
  • Resolved
    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

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

Sep 2025

Inbound CNAM Lookup Intermittently Not Returning Correct CID
  • Resolved
    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 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

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

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

Sep 2025 to Nov 2025

Next