Historial de interrupciones de Clearlyip

1. September 2, 2026 at 3:15 PM UTCinvestigating

   Estamos investigando un problema en el que las llamadas salientes a un pequeño porcentaje de centros de tarifas están fallando para los clientes. Tenga en cuenta que esto sólo afecta a los clientes directamente conectados a través de nuestra plataforma XCast.

2. September 2, 2026 at 3:17 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. September 2, 2026 at 5:45 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. September 3, 2026 at 11:54 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 25, 2026 at 8:51 PM UTCinvestigating

   Estamos viendo un aumento en los retrasos de envío de correo para mensajes provenientes de nuestras plataformas hacia los servicios de correo de Microsoft.

2. August 25, 2026 at 8:55 PM UTCmonitoring

   El procesamiento de cola continúa con éxito, aunque lentamente como Microsoft acepta correo de nuestra plataforma(s). También esperamos que las tasas de aceptación aumenten con el tiempo. La ingeniería sigue monitoreando las mejoras de actividad y entrega.

3. August 26, 2026 at 2:24 AM UTCmonitoring

   Seguimos monitoreando para mejorar las tarifas de envío de correo a los servicios de correo de Microsoft.

4. August 26, 2026 at 2:07 PM UTCmonitoring

   Aunque todavía estamos viendo retrasos en la entrega de correo a los servicios de correo de Microsoft, las tasas de aceptación están mejorando continuamente y el atraso actual ha sido casi completamente procesado. Seguimos monitoreando para el rendimiento y cerraremos esto una vez que estemos satisfechos con las tasas de entrega constantes.

5. August 27, 2026 at 2:18 PM UTCresolved

   El correo sigue fluyendo normalmente y a las tasas de entrega previstas sin demoras.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 21, 2026 at 1:46 PM UTCinvestigating

   Estamos investigando problemas de calidad de llamada intermitente con llamadas inbound con nuestros transportistas de arriba

2. August 21, 2026 at 3:07 PM UTCresolved

   El transportista ha resuelto las cuestiones a aproximadamente 9:13am CST

Traducido automáticamente desde la actualización oficial del incidente.

1. June 22, 2026 at 4:59 PM UTCinvestigating

   Actualmente estamos investigando problemas con nuestros servidores de conexión Este de EE.UU. que están causando problemas de terminación y problemas de audio.

2. June 22, 2026 at 6:59 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. June 22, 2026 at 7:38 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 15, 2026 at 12:53 PM UTCidentified

   We are currently investigating an issue with our CA-East trunks and have taken them offline at this time.

2. June 15, 2026 at 4:32 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. June 15, 2026 at 5:48 PM UTCresolved

   This incident has been resolved.

1. June 9, 2026 at 7:22 PM UTCinvestigating

   IS NOC is reviewing reports of connectivity issues for some Pulsar360 hosted PBXs in the Toronto region.

2. June 9, 2026 at 8:44 PM UTCinvestigating

   Work continues to isolate and find the root cause for connectivity interruptions in the Toronto region.

3. June 9, 2026 at 9:04 PM UTCmonitoring

   IS NOC has identified and resolved the issue(s) responsible for connectivity interruption. We are seeing alarms clearing at this time and will continue to monitor.

4. June 10, 2026 at 1:16 AM UTCresolved

   All services remain stable and operational, free from the previously experienced issues.

1. June 9, 2026 at 2:27 PM UTCinvestigating

   We are currently investigating an issue which is affecting chat/sms on Clearly Cloud USA - w

2. June 9, 2026 at 2:50 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. June 9, 2026 at 5:24 PM UTCresolved

   This incident has been resolved.

1. June 1, 2026 at 1:54 PM UTCmonitoring

   We are seeing some isolated connectivity issues in our US-Central region facilities. They seem to be transient in nature and quick to assert/resolve. We are working with our upstream provider(s) and monitoring closely.

2. June 1, 2026 at 8:13 PM UTCresolved

   This incident has been resolved.

1. May 31, 2026 at 6:03 PM UTCinvestigating

   Our US-Central datacenter is experiencing routing issues at this time. Intermittent problems are resulting from this.

2. May 31, 2026 at 6:22 PM UTCidentified

   Our upstream connectivity provider(s) are experiencing degraded network performance which is affecting ClearlyIP/14IP services. They are working diligently to resolve this issue.

3. May 31, 2026 at 7:48 PM UTCidentified

   Work continues by our upstream provider(s) to isolate and resolve the root connectivity issues.

4. May 31, 2026 at 9:31 PM UTCidentified

   Work continues by our upstream provider(s) to isolate and resolve an apparent DDoS attack affecting multiple customers at the US-Central facilities.

5. June 1, 2026 at 12:40 AM UTCmonitoring

   We are seeing recovery but are continuing to monitor the situation while our upstream provider(s) work towards a full resolution.

6. June 1, 2026 at 1:06 AM UTCidentified

   We are seeing degraded connectivity once again, affecting services in US-Central. We are awaiting updates and progress reports from our upstream provider(s).

7. June 1, 2026 at 1:57 AM UTCmonitoring

   We are once again seeing recovery and are continuing to monitor the situation. Our upstream provider(s) have confirmed positive progress towards resolution of this ongoing DDoS event.

8. June 1, 2026 at 3:35 AM UTCmonitoring

   Latest updates from our upstream provider(s) indicate a full restoration of all services and connectivity. We are confirming the same and continue to see clean network operation at this time. We will continue to monitor.

9. June 1, 2026 at 11:54 AM UTCresolved

   Connectivity has remained stable.

10. June 10, 2026 at 8:52 PM UTCpostmortem

    **Summary / Impact** On the afternoon of May 31st, 2026, 14IP's network operations group began to observe connectivity issues with resources located at its US-Central \(MKE\) data center.  The team began working with their counterparts at the data center facility to understand the nature of the problem.  It was quickly determined that a distributed denial of service \(DDoS\) attack targeted upstream was affecting all tenants of the data center. Significant malicious traffic \(exceeding 450gbps\) was measured upstream during the peak of the attack which overwhelmed equipment as well as primary, secondary, and tertiary links.  This traffic was mitigated through coordinated, escalating filtering with upstream transit providers, as well as internal engineering to stabilize routing. During the incident, connectivity to systems and services primarily located in this data center were impacted significantly for periods of time between approximately 2 PM ET and 9:30 PM ET.  This included Clearly Cloud, ComXchange hosted, Xivea, Business Connect, EPlatform, and several other systems.  \(US-East trunking services continued to operate during the US-Central incident.\) **Follow-Up** Several facility-level network and system improvements have been implemented following the incident which should reduce the risk of future occurrences.  This includes the deployment of additional DDoS scrubbing capacity, improved granularity for detecting attacks, additional fiber capacity upstream, as well as core network enhancements. 14IP plans additional improvements to its systems and operations to improve platform resilience and flexibility when responding to future incidents.

1. May 28, 2026 at 5:16 PM UTCidentified

   An upstream Canadian carrier is currently having issues. This may affect incoming calls routed through that carrier, but is limited to ONLY Canadian DIDs through that carrier. Outbound should not be affected. At this time, we have no information from the carrier on ETA.

2. May 28, 2026 at 6:00 PM UTCmonitoring

   The upstream carrier is now routing properly. We are monitoring and waiting on more information related to the outage.

3. May 28, 2026 at 6:50 PM UTCresolved

   This incident has been resolved.

1. April 27, 2026 at 6:26 PM UTCinvestigating

   The team is investigating Call Panel on Clearly Cloud USA displaying a bad certificate.

2. April 27, 2026 at 6:51 PM UTCresolved

   This incident has been resolved.

1. April 3, 2026 at 8:32 PM UTCinvestigating

   We are seeing issues with provisioning and registration of some Grandstream devices. The team is actively reviewing the situation

2. April 5, 2026 at 12:01 AM UTCmonitoring

   We have implemented a fix. If you are still having issues with your devices, please contact us by emailing [email protected] and we can assist you further.

3. May 8, 2026 at 7:22 PM UTCresolved

   This incident has been resolved.

1. March 19, 2026 at 2:55 PM UTCidentified

   The team has identified the issue and is currently working on a fix.

2. March 19, 2026 at 3:38 PM UTCresolved

   This incident has been resolved.

1. March 13, 2026 at 11:52 PM UTCinvestigating

   We are currently investigating this issue.

2. March 14, 2026 at 12:41 AM UTCidentified

   The issue has been identified and a fix is being implemented.

3. March 14, 2026 at 1:19 AM UTCresolved

   This incident has been resolved.

1. February 19, 2026 at 2:54 PM UTCinvestigating

   We are currently investigating an issue with Call Panel on Clearly Cloud Canada.

2. February 19, 2026 at 4:03 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 19, 2026 at 4:04 PM UTCmonitoring

   A fix is being implemented. If you still are experiencing issues, please open a support ticket and the team will assist.

4. February 19, 2026 at 5:03 PM UTCresolved

   This incident has been resolved.

1. December 15, 2025 at 6:41 PM UTCinvestigating

   The team is currently investigating an issue with Clearly Cloud USA

2. December 15, 2025 at 6:42 PM UTCidentified

   The team has identified the issue and should be resolved quickly.

3. December 15, 2025 at 6:43 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. December 15, 2025 at 7:00 PM UTCresolved

   This incident has been resolved.

1. December 4, 2025 at 6:57 PM UTCinvestigating

   We are currently investigating this issue.

2. December 4, 2025 at 7:03 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. December 4, 2025 at 7:24 PM UTCresolved

   This incident has been resolved.

1. December 2, 2025 at 4:45 PM UTCinvestigating

   We are currently investigating inbound and outbound calling issues with Clearly Cloud US platform.

2. December 2, 2025 at 5:09 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. December 2, 2025 at 5:30 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. December 2, 2025 at 7:46 PM UTCresolved

   This incident has been resolved.

1. November 11, 2025 at 7:04 PM UTCresolved

   SIP2 and Proxy55 are not responding. Calls routing to failover trunks

1. November 3, 2025 at 4:49 PM UTCinvestigating

   We are currently investigating this issue.

2. November 3, 2025 at 4:57 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. November 3, 2025 at 5:29 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. November 3, 2025 at 6:10 PM UTCresolved

   This incident has been resolved.

5. November 4, 2025 at 5:13 PM UTCpostmortem

   At approximately 11:27AM ET on November 3, ClearlyIP's NOC team began to receive system alerts indicating excess session activity within its US-East trunking systems. The team's investigation identified unauthenticated INVITE messages being received from unknown IPs as the source of the excess traffic, as well as a customer generating unexpected levels of outbound calls. Steps were taken to mitigate the traffic's impact, including restarting affected services to clear sessions and restore normal status. By approximately 11:55AM ET, the US-East situation was stabilized and session traffic had returned to normal levels. The team has identified a number of improvements and traffic management strategies to help avoid similar incidents which will be implemented in future maintenance events.