UCaaS Status Page - Notice history

All systems operational

100% - uptime

Ashburn (IAD) Voice - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Atlanta (ATL) Voice - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Grand Rapids (GRR) Voice - Operational

100% - uptime
Jun 2025 · 99.968%Jul · 99.987%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Las Vegas (LAS) Voice - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Phoenix (PHX) Voice - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Messaging (SMS/MMS) - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Native Fax - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025
100% - uptime

API - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Call Recording (IAD) - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Call Recording (PHX) - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Call Recording (ATL) - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Device Provisioning (NDP) - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Manager Portal - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Manager Portal Pro - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

SNAPmobile - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

SNAPmobile Web - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

VoIPMonitor (QoS) - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

CloudieConnect - Operational

100% - uptime
Jun 2025 · 100.00%Jul · 100.00%Aug · 100.00%
Jun 2025
Jul 2025
Aug 2025

Notice history

Jul 2025

CloudieConnect Server Maintenance
  • Completed
    July 19, 2025 at 4:30 AM
    Completed
    July 19, 2025 at 4:30 AM
    Maintenance has completed successfully
  • In progress
    July 19, 2025 at 3:30 AM
    In progress
    July 19, 2025 at 3:30 AM
    Maintenance is now in progress
  • Planned
    July 19, 2025 at 3:30 AM
    Planned
    July 19, 2025 at 3:30 AM

    On Friday, July 18, 2025, at 11:30 PM ET, we’ll be performing routine maintenance on the CloudieConnect system to help ensure continued performance and reliability.

     

    During this time, CloudieConnect users may experience a brief service interruption (up to 5 minutes) during which login access and the ability to make or receive calls may be temporarily unavailable.

     

    All other services will remain fully operational and unaffected.

    We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co.

GRR Inbound Call Failures
  • Postmortem
    Postmortem
  • Resolved
    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.
  • Update
    Update
    We implemented a fix and are currently monitoring the result.
  • Monitoring
    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

Jun 2025

Registration Failure on GRR
  • Resolved
    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:

  • Update
    Update

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

Loss of Communication to GRR
  • Update
    Update

    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: 

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

  • Update
    Update

    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

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

  • Investigating
    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 2025 to Aug 2025

Next