Duration: 2 hours

Affected Components: Manager Portal, SNAPmobile Web, API

Mar 27, 06:00:00 GMT+0
Identified - We will be performing urgent security updates on Core1-ATL on **March 27th, 2026 at 2:00 am ET**. There is no expected interruption of service during this time, but users may be logged out of the Manager Portal and SNAPmobile Web during the maintenance window. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Mar 27, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 27, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 4 hours

Affected Components: Native Fax

Mar 27, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 27, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Mar 27, 03:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server on **March 26th, 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](mailto:support@oit.co)..

Duration: 1 hour and 15 minutes

Affected Components: United States Outbound Calling Services, United States Inbound Calling Services

Mar 3, 15:27:33 GMT+0
Monitoring - At approximately 9:25am ET, we became aware of inbound and outbound call quality concerns through our carrier Bandwidth, causing choppiness on call audio. **When it began: 9:25am ET** **Current Status:** While gathering details and examples from partners, Bandwidth updated their status page at 9:39am ET acknowledging call failures. At 9:58am ET, Bandwidth updated that they are observing expected inbound and outbound calls and are monitoring. **Next Steps:** We have temporarily rerouted outbound calls through another carrier to preserve outbound call quality. Outbound calls should be functioning as expected. Inbound calls through Bandwidth may continue to have degraded quality until the incident is resolved by them. **Next Update:** 11:20am ET.

Mar 3, 16:23:27 GMT+0
Monitoring - **What is affected:** At approximately 9:25am ET, we became aware of inbound and outbound call quality concerns through our carrier Bandwidth causing choppiness on call audio. **When it began: 9:25am ET** **Current Status:** While gathering details and examples from partners, Bandwidth updated their status page at 9:39am ET acknowledging call failures. At 9:58am ET, Bandwidth updated that they are observing expected inbound and outbound calls and monitoring. We have temporarily rerouted outbound calls through another carrier to preserve outbound call quality. Outbound calls should be functioning as expected. Inbound calls through Bandwidth may continue to have degraded quality until the incident is resolved by them. **Next Steps:** At this time, we are continuing to monitor inbound call quality, however, no further reports of choppiness or degraded quality have been made. **Next Update:** 12:20pm ET.

Mar 3, 16:42:56 GMT+0
Resolved - At approximately 9:25am ET, we became aware of inbound and outbound call quality concerns through our carrier Bandwidth causing choppiness on call audio. **When it began: 9:25am ET** **Current Status:** At this time, Bandwidth has declared the incident resolved. We have removed the reroute impacting outbound calls and tested to confirm inbound and outbound calls are successful. **Next Steps:** A major incident report will be released within 48 business hours..

Duration: 4 hours

Affected Components: Native Fax

Feb 26, 04:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server on **February 25th, 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](mailto:support@oit.co)..

Feb 26, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Feb 26, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 23 hours and 20 minutes

Affected Components: United States Outbound Calling Services

Jan 22, 15:14:31 GMT+0
Resolved - **What Occurred**: On 1/21/26, at 10:20 AM ET, we were made aware of outbound calls failing for several clients. After further investigation, we determined that one of our underlying carriers was experiencing degraded services, resulting in outbound call failures. **What was Affected:** Outbound Calling for DFW Region **When it Began**: 01/21/2026, 10:20 AM ET **Current Status**: Bandwidth declared the incident resolved yesterday at 7:22 PM ET. After 24 hours of monitoring and testing, we successfully routed all traffic back through Bandwidth and have confirmed all outbound calls are continuing to process as expected. **Next Steps:** * This incident is now considered resolved. * The major incident report will be available within 48 business hours. **Next Update:** N/A.

Jan 26, 16:16:12 GMT+0
Resolved - The major incident report is now available: <https://voipdocs.io/en%5FUS/announcements/2026-01-21-connection-failures-on-outbound-calls>.

Jan 21, 15:54:20 GMT+0
Monitoring - **What Occurred**: At 10:20 AM ET, we were made aware of outbound calls failing for several clients. After further investigation, we determined that one of our underlying carriers was experiencing degraded services leading to outbound call failures. **What is Affected:** All Outbound Calling **When it Began:** 01/21/2026, 10:20 AM ET **Current Status:** As of 10:34 AM ET, outbound calls have been rerouted through a different carrier and are now going through successfully. **Next Steps:** The major incident report will be available within 48 business hours. **Next Update:** 01/22/2026, 10:30 AM ET 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)..

Duration: 4 hours

Affected Components: Native Fax

Jan 15, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 15, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jan 15, 04:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server and firewall on **January 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](mailto:support@oit.co)..

Duration: 4 hours

Affected Components: Manager Portal Pro

Jan 10, 15:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 10, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jan 10, 15:00:00 GMT+0
Identified - To improve platform performance and reliability, we will be upgrading Manager Portal Pro (MPP) to version 4.0.0 on **January 10th, 2026, at 10:00 am ET**. No service downtime is expected during this maintenance window. However, you may need to log out of the Manager Portal and log back in once the upgrade is complete. **Please Note:** Following this upgrade, webhook integrations (URL Call Pop) and Manager Portal Pro (MPP) features will use a new static IP address: **52.20.230.43** If you filter inbound traffic by source IP (such as via firewall or WAF rules), please ensure this new IP address is added to your allowlist prior to the maintenance window. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Duration: 23 hours and 15 minutes

Affected Components: Atlanta (ATL) Voice

Dec 22, 20:45:26 GMT+0
Monitoring - **What Occurred**: At 2:50 pm ET, the SiPbx service, which controls voice and registration on the core1-atl server, crashed, causing inbound and outbound calls to redirect to alternate servers, as well as device registration. **What is Affected:** Atlanta (ATL) Voice **When it Began:** 12/22/2025, 2:50 PM ET **Current Status:** At 2:53p ET, the SiPbx service automatically recovered, and device registrations and inbound/outbound calls began returning to the core1-atl server successfully. **Next Steps:** We are monitoring and investigating the root cause of the service failure. **Next Update:** 12/23/2025, 3:00 PM ET.

Dec 23, 20:00:46 GMT+0
Resolved - **What Occurred:** At 2:50 PM ET, the SiPbx service that controls voice and registration on the Core1-ATL server crashed, causing inbound and outbound calls to redirect to alternate servers, as well as device registration. **What is Affected:** Atlanta (ATL) Voice **When it Began:** December 22nd, 2025, 2:50 PM ET **Current Status:** As of 9:30 AM ET, Core1-ATL remains stable. Working with the vendor we were able to identify the root cause of the service crash. It was ultimately due to a subprocess not closing cleanly and a fix is implemented in the next system update which is scheduled for Q1 of 2026. **Next Steps:** This incident is now considered resolved. The major incident report will be available in 48 hours. .

Duration: 1 hour and 30 minutes

Affected Components: CloudieConnect

Dec 16, 06:00:00 GMT+0
Identified - During the December 12th implementation of the CloudieConnect High Availability (HA) infrastructure, our engineering team identified additional configuration requirements that will strengthen the overall HA deployment. To ensure that the infrastructure is implemented to the highest standard, we have scheduled a follow-up maintenance window. On **Tuesday, December 16th, 2025 at 1:00 AM ET**, our team will finalize the High Availability server activation and integration for your CloudieConnect mobile and desktop apps. This maintenance will complete the infrastructure upgrades, delivering the enhanced reliability and seamless failover protection your operations depend on. During this 90-minute upgrade window, you may experience temporary service degradation as we bring the HA system fully online. Device registration, inbound/outbound calling, and messaging functions may be briefly affected. All other voice and portal services will continue to operate normally. Thank you for your patience as we complete this critical infrastructure upgrade. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Dec 16, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Dec 16, 07:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 1 hour and 30 minutes

Affected Components: CloudieConnect

Dec 10, 16:50:44 GMT+0
Identified - On **December 12th, 2025, starting at 12:30 AM ET**, OIT will be upgrading the resiliency of the servers that power our CloudieConnect mobile and desktop apps. This upgrade finalizes our High Availability (HA) infrastructure, providing a solid foundation for enhanced reliability and seamless failover protection. During the upgrade, CloudieConnect users may experience a brief service degradation lasting approximately 30 minutes as the HA server is activated and integrated. Device registration, inbound/outbound calling, and messaging may be temporarily impacted during this time. All other voice and portal services will continue to operate normally..

Dec 12, 05:30:01 GMT+0
Identified - Maintenance is now in progress.

Dec 12, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Dec 12, 05:30:00 GMT+0
Identified - On **December 12th, 2025, starting at 12:30 AM ET**, we will be performing system updates on the CloudieConnect servers to finalize High Availability (HA) services, ensuring failover redundancy is fully operational. A brief service degradation lasting approximately 30 minutes may occur as the HA server is activated and integrated with the existing infrastructure. During this time, device registration and inbound/outbound calling may be impacted. All other voice and portal services will continue to operate normally. We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Duration: 1 hour

Affected Components: API

Dec 12, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

Dec 12, 02:00:00 GMT+0
Completed - Maintenance has completed successfully.

Dec 12, 01:00:00 GMT+0
Identified - DNS updates for **api.ucaasnetwork.com** will be applied on **December 11th, 2025 at 8:00 PM ET**. The changes are to improve redundancy and speed of call responses for the API services. There is no expected downtime from this DNS change. There will also be no downtime for voice or portal services. As a reminder, please review your scripts for any IP filtering and ensure you are allowing traffic to and from all of our IPs. The full list can be found here: [https://voipdocs.io/faqs/ip-addresses-ports](https://voipdocs.io/faqs/ip-addresses-ports#ip-addresses-for-additional-services-2) We appreciate your patience throughout this process. If you need additional support, please contact [support@oit.co](mailto:support@oit.co)..

Duration: 4 hours

Affected Components: Native Fax

Nov 26, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Nov 26, 08:00:00 GMT+0
Completed - Maintenance has completed successfully.

Nov 26, 04:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server and firewall on **November 25th, 2025, at 11:00 pm ET**. There will be an interruption in the delivery and sending of faxes while maintenance is performed..

Duration: 2 hours

Affected Components: Manager Portal Pro

Nov 13, 15:30:01 GMT+0
Identified - Maintenance is now in progress.

Nov 13, 17:30:00 GMT+0
Completed - Maintenance has completed successfully.

Nov 13, 15:30:00 GMT+0
Identified - OITVOIP will be performing unscheduled platform maintenance to deploy system improvements and enhancements for Manager Portal Pro (MPP) on **November 13th, 2025 at 10:30 AM ET**. This is **not for core services**, and includes things like TCR, call pop, and other integrations. This release delivers multiple feature updates, security hardening, and performance improvements. _All changes are backward compatible and require no action from existing integrations or API consumers_. **HIGHLIGHTS** * CloudieAI billing integration for sentiment and transcription usage * Major security hardening across API and database access * Faster API responses for integrations, reporting, and analytics * Improved stability of nightly reporting and billing jobs **FEATURES & ENHANCEMENTS** **Advanced Call Recording Controls** * Added UI-configurable controls to enable or disable advanced call recording features. * Centralized recording configuration management for easier administration. **CloudieAI Billing Integration** * New billing endpoints for sentiment analysis and call transcription usage. * Usage metrics are now included in nightly count operations. * Automatic usage data collection for CloudieAI-related services. * Improved database connection management when communicating with the external CloudieAI billing database. **React Upgrades** * Completed migration of key frontend components **SECURITY IMPROVEMENTS** **Hardened Security** * Completed a security review across the backend API. * Hardened high-risk areas including authentication, reporting, integrations, CSP registry, user management, and webhooks. * No changes to expected API behavior; existing integrations continue to work as before. **API Authentication & Access Control** * Implemented a dual-token authentication model supporting both JWT and OAuth-based tokens. * Added token caching strategies to reduce authentication overhead. **PERFORMANCE & STABILITY** **API Response Time Optimization** * Parallelized independent asynchronous operations across multiple controllers (integrations, reporting, analytics, call handlers, phone numbers). * Refactored legacy promise chains to modern async/await patterns. * Improved integrations response time by roughly 25–30%. * Similar performance improvements are expected on call history, phone number management, and analytics endpoints. * Tuned database connection pooling and query execution for more consistent performance. **Nightly Processing & Reporting** * Resolved an issue that could cause nightly processing jobs to fail under certain configuration conditions. * Added additional safeguards to prevent failures caused by incomplete or inconsistent configuration data. **Configuration & Runtime Stability** * Updated service endpoint configuration handling to ensure more consistent authentication behavior. * Refined connection management and database usage patterns to reduce runtime errors and improve overall system stability. **We do not anticipate any service interruptions during this maintenance window.** All systems are expected to remain fully operational throughout the deployment. If you need additional support, please contact [**support@oit.co**](mailto:support@oit.co)..

Duration: 7 hours and 10 minutes

Oct 20, 18:10:59 GMT+0
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](mailto:support@oit.co), [success@oit.co](mailto:success@oit.co), [porting@oit.co](mailto:porting@oit.co), [billing@oit.co](mailto:billing@oit.co), [sales@oit.co](mailto:sales@oit.co), and [compliance@oit.co](mailto: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](mailto:support@oit.co)..

Oct 21, 01:21:09 GMT+0
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](mailto:support@oit.co), [success@oit.co](mailto:success@oit.co), [porting@oit.co](mailto:porting@oit.co), [billing@oit.co](mailto:billing@oit.co), [sales@oit.co](mailto:sales@oit.co), and [compliance@oit.co](mailto: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.

Duration: 1 day, 16 hours and 54 minutes

Affected Components: CloudieAI

Oct 6, 21:39:22 GMT+0
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..

Oct 8, 14:33:08 GMT+0
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.

Duration: 21 days and 45 minutes

Affected Components: United States Inbound Calling Services

Sep 29, 15:56:11 GMT+0
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](mailto: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](mailto:support@oit.co)..

Oct 7, 14:59:56 GMT+0
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](mailto: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.

Sep 16, 14:14:58 GMT+0
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](mailto:support@oit.co)..

Duration: 2 hours and 14 minutes

Affected Components: Native Fax

Aug 22, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 22, 03:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server and firewall on August 21st, 2025, at 11:00 pm ET. There will be an interruption in the delivery and sending of faxes while maintenance is performed..

Aug 22, 05:13:37 GMT+0
Completed - Maintenance has completed successfully..

Duration: 3 hours and 17 minutes

Affected Components: TCR - The Campaign Registry

Aug 21, 18:30:32 GMT+0
Resolved - This incident is now considered **resolved**. We will continue to monitor for the next 24 hours. We appreciate your patience throughout this process. If you need additional support, please contact [**support@oit.co**](mailto:support@oit.co). .

Aug 21, 16:19:18 GMT+0
Identified - \*\*What Occurred:\*\* We are currently experiencing a service disruption affecting The Campaign Registry (TCR) platform. This impacts the ability to create new 10DLC campaigns, register new brands, or edit existing campaigns. \*\*Who is Affected:\*\* All partners and clients who need to create new TCR/10DLC campaigns, register new brands, or modify existing campaign configurations. \*\*When It Began:\*\* 9:31 AM ET, 8-21-25 \*\*Current Status:\*\* \* TCR has confirmed a platform-wide issue affecting campaign management functions \* OIT is actively working with TCR support to monitor the situation \* No updates have been provided by TCR at this time \* You can follow along for live updates from TCR at \[Campaign Registry Status\](https://status.campaignregistry.com/#) \*\*Workarounds:\*\* There are no workarounds available for campaign creation or editing at this time. Please plan accordingly for any urgent campaign needs. \*\*Next Steps:\*\* \* We recommend postponing any planned campaign creation or modifications until service is restored \* OIT will continue monitoring the situation and provide updates as information becomes available \*\*Next Update:\*\* 3:15 PM ET, 8-21-25.

Aug 21, 15:13:08 GMT+0
Identified - **What Occurred:** We are currently experiencing a service disruption affecting The Campaign Registry (TCR) platform. This impacts the ability to create new 10DLC campaigns, register new brands, or edit existing campaigns. **Who is Affected:** All partners and clients who need to create new TCR/10DLC campaigns, register new brands, or modify existing campaign configurations. **When It Began:** 9:31 AM ET, 8-21-25 **Current Status:** * TCR has confirmed a platform-wide issue affecting campaign management functions * OIT is actively working with TCR support to monitor the situation * No estimated time of resolution has been provided at this time **Workarounds:** There are no workarounds available for campaign creation or editing at this time. Please plan accordingly for any urgent campaign needs. **Next Steps:** * We recommend postponing any planned campaign creation or modifications until service is restored * OIT will continue monitoring the situation and provide updates as information becomes available **Next Update:** We will provide an update within 1 hour or when new information becomes available **Offline Services:** * TCR Campaign Creation * TCR Brand Registration * TCR Campaign Editing/Modifications **Degraded Services:** * None **Operational Services:** * SMS/MMS message sending and receiving (all existing campaigns continue to function normally) * All other messaging services * All voice services * All portal services **Important Note:** This outage does NOT affect your ability to send or receive messages. All existing registered campaigns continue to operate normally. 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..

Duration: 1 hour

Affected Components: CloudieConnect

Jul 19, 04:30:00 GMT+0
Completed - Maintenance has completed successfully.

Jul 19, 03:30:01 GMT+0
Identified - Maintenance is now in progress.

Jul 19, 03:30:00 GMT+0
Identified - 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](mailto:support@oit.co)..

Duration: 1 hour

Affected Components: Phoenix (PHX) Voice, Ashburn (IAD) Voice

Jul 16, 01:30:01 GMT+0
Identified - Maintenance is now in progress.

Jul 16, 02:30:00 GMT+0
Completed - Maintenance has completed successfully.

Jul 16, 01:30:00 GMT+0
Identified - As part of our ongoing preparations for the migration to the new IAD and PHX core servers, we will be performing some maintenance on the IAD and PHX core servers tonight, July 15, at 9:30 PM ET. There will be no interruption of service for the ATL, GRR, or LAS servers. We appreciate your patience throughout this process. If you need additional support, please contact support@oit.co..

Duration: 1 day, 1 hour and 5 minutes

Affected Components: United States Inbound Calling Services, mFax, Messaging (SMS/MMS), United States Outbound Calling Services, Manager Portal Pro, Device Provisioning (NDP), Native Fax, Commio, Nuso, Voice, SNAPmobile, TCR - The Campaign Registry, Phoenix (PHX) Voice, Canada Outbound Calling Services, Teammate, Call Recording (PHX), MobileX, Ashburn (IAD) Voice, Call Recording (IAD), United States Inbound Calling Services, Canada Inbound Calling Services, Call Recording (ATL), Atlanta (ATL) Voice, United States Outbound Calling Services, Grand Rapids (GRR) Voice, API, Las Vegas (LAS) Voice, Manager Portal, SNAPmobile Web, VoIPMonitor (QoS)

Jul 14, 16:38:38 GMT+0
Investigating - At 11:45 AM ET, the mFax vendor reported a subset of inbound numbers failing with a "no fax tone detected" error. This is due to one of the vendor's upstream telecom providers experiencing intermittent failures. What Is Affected: mFax When It Began: 11:45 AM ET June 14, 2025 Current Status: The vendor is currently investigating. Next Steps: No action required. Next Update: 1:35 PM ET June 14, 2025.

Jul 14, 17:30:30 GMT+0
Investigating - What Is Affected: mFax When It Began: 11:45 AM ET June 14, 2025 Current Status: The vendor is currently investigating. Next Steps: No action required. Next Update: 2:35 PM ET June 14, 2025.

Jul 14, 18:40:10 GMT+0
Monitoring - **Current Status:** A fix has been implemented with successful faxes received. **Next Steps:** We will continue to monitor for the next 24 hours. **Next Update:** 2:35 PM ET June 15, 2025.

Jul 15, 17:43:11 GMT+0
Resolved - As of 2:58am, July 15, 2025 mfax is showing the implemented fix performed by their telecom provider is successful and all inbound faxes are working as intended. After 24 hours of monitoring with no additional inbound fax failures, This incident is now considered resolved..

Duration: 23 hours and 34 minutes

Affected Components: Grand Rapids (GRR) Voice

Jul 8, 20:05:24 GMT+0
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.

Jul 9, 19:38:59 GMT+0
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..

Jul 8, 20:10:22 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Jul 11, 20:13:58 GMT+0
Postmortem - Major Incident Report: [2025-07-08 Inbound and Outbound call failures on GRR](https://voipdocs.io/announcements/-2025-07-08-registration-failure-on-grr).

Duration: 1 hour and 58 minutes

Affected Components: Messaging (SMS/MMS), Device Provisioning (NDP), Native Fax, SNAPmobile, Phoenix (PHX) Voice, Call Recording (PHX), Ashburn (IAD) Voice, Call Recording (IAD), Call Recording (ATL), Atlanta (ATL) Voice, Grand Rapids (GRR) Voice, API, Las Vegas (LAS) Voice, Manager Portal, SNAPmobile Web, VoIPMonitor (QoS)

Jun 27, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 27, 05:58:10 GMT+0
Completed - Maintenance has completed successfully..

Jun 27, 04:00:00 GMT+0
Identified - We are upgrading all core servers to the V44.3 software, which includes bug fixes as well as upgrades to the manager portal. .

Duration: 4 hours

Affected Components: SNAPmobile Web, Atlanta (ATL) Voice

Jun 13, 10:00:00 GMT+0
Completed - Maintenance has completed successfully.

Jun 13, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 13, 06:00:00 GMT+0
Identified - We will be performing general system updates on our ATL core server in preparation for the upcoming migration to the IAD and PHX servers on June 13th, 2025, at 2:00am ET. During this time we will redirect the portal, device registrations, and calls to alternate servers. There is no expected interruption of service during this time..

Duration: 3 hours and 44 minutes

Affected Components: mFax

Jun 12, 19:35:14 GMT+0
Monitoring - Cloudflare experienced a broad service outage that affected the mFax service. \*\*What Is Affected:\*\* MFax \*\*When It Began:\*\* 1:30 PM ET June 12, 2025 \*\*Current Status:\*\* As of 3:12 pm ET, Cloudflare is showing services are recovering, while mFax services may still experience intermittent "internal server" error messages until fully restored. \*\*Next Steps:\*\* N/A \*\*Next Update:\*\* 4:30PM ET June 13, 2025.

Jun 12, 23:18:59 GMT+0
Resolved - Notice: Cloudflare Outage What Is Affected: MFax When It Began: 1:30 PM ET June 12, 2025 Current Status: Resolved - Cloudflare identified the cause to be with one of their upstream vendors, who as of 4:00 PM ET has fully restored services on their end. mFax is showing all fax queues are clearing and services have been restored. This incident is now considered Resolved. Next Steps: \* Major Incident Report will be available within 48 hours. Next Update: 4:30PM ET June 13, 2025 Operational Services: All.

Duration: 22 hours and 36 minutes

Affected Components: Grand Rapids (GRR) Voice

Jun 5, 19:16:19 GMT+0
Monitoring - .

Jun 5, 19:16:02 GMT+0
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.

Jun 6, 17:51:33 GMT+0
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:** * Major Incident Report is now available * MIR report: <https://voipdocs.io/announcements/-2025-06-05-registration-failure-on-grr->.

Duration: 1 day, 1 hour and 36 minutes

Affected Components: Grand Rapids (GRR) Voice

Jun 4, 15:18:44 GMT+0
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 4, 16:22:22 GMT+0
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.

Jun 4, 21:18:33 GMT+0
Monitoring - **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.

Jun 5, 16:55:00 GMT+0
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..

Jun 6, 16:17:09 GMT+0
Resolved - **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:** * The degraded circuit was immediately removed from the routing profile to prevent further instability * Enhanced monitoring was implemented during the recovery period to ensure sustained stability * **The Major Incident Report is now available:** <https://voipdocs.io/announcements/-2025-06-04-loss-of-communication-to-grr-server>.

May 30, 16:04:44 GMT+0
Identified - At 11:06 AM ET, we were alerted by our monitoring tools that WSS connections on GRR & LAS were failing. SNAPmobile Web uses WSS for the SIP connection. \*\*What Is Affected\*\*: All SNAPmobile Web Connections on GRR & LAS \*\*When It Began:\*\* 11:06AM ET \*\*Current Status:\*\* We have identified the cause and are awaiting vendor confirmation to implement a fix. \*\*Next Steps\*\*: No next steps for partners \*\*Next Update\*\*: 12:06PM ET.

Jun 3, 15:25:40 GMT+0
Resolved - \*\*MIR now available for Websocket Connection Failure on GRR and LAS\*\* At 11:06AM ET we were alerted by our monitoring tools that WSS connections on GRR, LAS, IAD, and PHX were failing. SNAPmobile Web uses WSS for the SIP connection. \*\*What was Affected:\*\* All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX \*\*When It Began\*\*: 11:06AM ET 05/06/2025 \*\*Resolution:\*\* \* \*\*Our vendor resolved an SSL issue with the affected FQDNs on 05/31/2025\*\* \* \*\*Major Incident Report\*\* is now available: <https://voipdocs.io/announcements/20250530-websocket-connections-for-grr-las-phx-and-iad-servers-failing-to-connect>.

May 30, 16:44:04 GMT+0
Identified - What Is Affected: All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX When It Began: 11:06 AM ET Current Status: * We have temporarily redirected all WSS traffic to ATL, which is confirmed to be working. In the meantime, our engineers will continue to work on a permanent resolution. Next Steps: * Users will need to completely close SNAPmobile Web and reopen it to ensure a new connection. If the problem persists, please clear your browser cache and test again. If, after clearing your cache, you still cannot connect, please submit a ticket to [support@oit.co](mailto:support@oit.co) Next Update: 2:06 PM ET.

May 31, 18:53:04 GMT+0
Resolved - This incident has been resolved..

May 30, 17:50:43 GMT+0
Monitoring - **What Is Affected:** All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX **When It Began:** 11:06AM ET **Current Status**: * After working with vendor support, we have successfully applied a fix to resolve WSS connections failing on LAS, GRR, IAD, & PHX. * Per our internal policy, we will keep all WSS traffic redirected to ATL while we continue to monitor for 24 hours. This will prevent further downtime if the problem reoccurs. **Next Steps:** * Users will need to completely close SNAPmobile Web and reopen it to ensure a new connection. If the problem persists, please clear your browser cache and test again. If after clearing your cache, you still cannot connect, please submit a ticket to support@oit.co * We understand that some users may experience poor call quality or dropped calls on ATL. If you experience any of these, please email support@oit.co with call examples or call traces so that we can investigate and potentially move affected clients back to their respective cores in advance. **Next Update:** 5/31/25 2:00 PM ET.

May 31, 18:56:52 GMT+0
Resolved - At 11:06AM ET we were alerted by our monitoring tools that WSS connections on GRR, LAS, IAD, and PHX were failing. SNAPmobile Web uses WSS for the SIP connection. **What Is Affected:** All SNAPmobile Web Connections on GRR, LAS, IAD, & PHX **When It Began:** 11:06AM 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.

Duration: 2 hours and 27 minutes

Affected Components: Atlanta (ATL) Voice, VoIPMonitor (QoS)

May 30, 06:00:00 GMT+0
Identified - We will be performing general system maintenance on our ATL Core and QoS servers on May 30th, 2025, at 2:00am ET. During this time, we will redirect device registrations, calls, and the portal to alternate servers. There is no expected interruption of service during this time..

May 30, 06:00:01 GMT+0
Identified - Maintenance is now in progress.

May 30, 08:26:53 GMT+0
Completed - Maintenance has completed successfully..

Duration: 4 hours

Affected Components: Native Fax

May 23, 03:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server and firewall on May 22nd, 2025, at 11:00pm ET. There will be an interruption in the delivery and sending of faxes while maintenance is performed..

May 23, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

May 23, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 2 hours and 30 minutes

Affected Components: SNAPmobile Web

Apr 25, 22:53:35 GMT+0
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.

Apr 25, 23:35:00 GMT+0
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 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.

Apr 26, 00:43:37 GMT+0
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 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.

Apr 26, 01:23:17 GMT+0
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 & LAS**When It Began**: 6:19PM ET**Current 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.

Duration: 2 hours

Affected Components: SNAPmobile Web

Apr 23, 12:48:07 GMT+0
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.

Apr 23, 13:50:19 GMT+0
Investigating - **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,](mailto: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.

Apr 23, 14:48:35 GMT+0
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.

Duration: 4 hours

Affected Components: mFax

Apr 23, 03:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 23, 07:00:00 GMT+0
Completed - Maintenance has completed successfully.

Apr 23, 03:00:00 GMT+0
Identified - We will be performing security maintenance on our fax server on April 22nd, 2025, at 11:00pm ET. There will be an interruption in the delivery and sending of faxes while maintenance is performed. Maintenance Start: 11:00pm, April 22nd, 2025, ET Estimated Time to Complete: 4 hours, 3:00am April 23rd, 2025, ET Offline Services • Fax.

Duration: 1 day and 6 hours

Affected Components: VoIPMonitor (QoS)

Apr 18, 05:00:00 GMT+0
Completed - Maintenance has completed successfully.

Apr 16, 23:00:00 GMT+0
Identified - We will be performing emergency security maintenance for Voipmonitor on April 16th at 7 PM EST. During this time, there may be a brief interruption to QoS scores showing in the portal, and any calls being conducted at that time may have reduced diagnostic data attached. There will not be any interruption to calls or device registration. **Maintenance Start:** 7:00 PM, April 16th, ET **Estimated Time to Complete:** 30 minutes, 7:30 PM, April 16th, ET **Offline Services:** Voipmonitor.

Apr 16, 23:00:01 GMT+0
Completed - Maintenance is now in progress.

Duration: 21 hours and 44 minutes

Affected Components: Call Recording (PHX), Call Recording (IAD)

Apr 15, 13:15:51 GMT+0
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.

Apr 15, 07:25:29 GMT+0
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).

Apr 14, 15:31:29 GMT+0
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.

Apr 14, 16:28:31 GMT+0
Investigating - **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.

Apr 14, 17:46:40 GMT+0
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.

Apr 14, 19:28:43 GMT+0
Identified - **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.

Apr 14, 20:31:32 GMT+0
Identified - **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.

Apr 14, 18:29:38 GMT+0
Identified - **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 ---.

Apr 14, 21:30:29 GMT+0
Identified - 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](mailto:support@oit.co)..

Duration: 3 minutes

Feb 24, 21:26:40 GMT+0
Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service..

Feb 24, 21:29:40 GMT+0
Resolved - API is now operational! This update was created by an automated monitoring service..

Duration: 2 minutes

Feb 24, 19:31:04 GMT+0
Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service..

Feb 24, 19:32:39 GMT+0
Resolved - API is now operational! This update was created by an automated monitoring service..