UCaaS Status Page - Notice history

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

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

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

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

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

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.

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

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

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

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

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