Ashburn (IAD) Voice - Operational
Ashburn (IAD) Voice
Atlanta (ATL) Voice - Operational
Atlanta (ATL) Voice
Grand Rapids (GRR) Voice - Operational
Grand Rapids (GRR) Voice
Las Vegas (LAS) Voice - Operational
Las Vegas (LAS) Voice
Phoenix (PHX) Voice - Operational
Phoenix (PHX) Voice
Messaging (SMS/MMS) - Operational
Messaging (SMS/MMS)
Native Fax - Operational
Native Fax
API - Operational
API
Call Recording (IAD) - Operational
Call Recording (IAD)
Call Recording (PHX) - Operational
Call Recording (PHX)
Call Recording (ATL) - Operational
Call Recording (ATL)
Device Provisioning (NDP) - Operational
Device Provisioning (NDP)
Manager Portal - Operational
Manager Portal
Manager Portal Pro - Operational
Manager Portal Pro
SNAPmobile - Operational
SNAPmobile
SNAPmobile Web - Operational
SNAPmobile Web
VoIPMonitor (QoS) - Operational
VoIPMonitor (QoS)
CloudieConnect - Operational
CloudieConnect
Notice history
May 2025
- UpdateUpdate**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:
- UpdateUpdate
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
- ResolvedResolvedThis incident has been resolved.
- MonitoringMonitoring
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
- UpdateUpdate
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
Next Update: 2:06 PM ET
- IdentifiedIdentifiedAt 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
Apr 2025
- ResolvedResolved
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
- UpdateUpdate
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
- InvestigatingInvestigating
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
- ResolvedResolved**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
- MonitoringMonitoring**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)
- UpdateUpdate
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.
- UpdateUpdate
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
- UpdateUpdate
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
- UpdateUpdate
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
- IdentifiedIdentified
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
- UpdateUpdate
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
- InvestigatingInvestigatingAt 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