Istoricul incidentelor Clearlyip

1. 2 septembrie 2026 la 15:15 UTCinvestigating

   Investigăm în prezent o problemă în care apelurile către un procent mic de centre de rate cedează pentru clienţi. Rețineți că acest lucru afectează doar clienții care se conectează direct prin intermediul platformei noastre XCast.

2. 2 septembrie 2026 la 15:17 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 2 septembrie 2026 la 17:45 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 3 septembrie 2026 la 11:54 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 25 august 2026 la 20:51 UTCinvestigating

   Vedem o creştere a întârzierilor de livrare prin poştă pentru mesajele provenite de pe platformele noastre către serviciile de poştă Microsoft.

2. 25 august 2026 la 20:55 UTCmonitoring

   Procesarea coadă continuă cu succes, deși lent, deoarece Microsoft acceptă mail de pe platforma noastră (s). Ne aşteptăm ca şi ratele de acceptare să crească în timp. Ingineria continuă să monitorizeze activitățile și îmbunătățirile de livrare.

3. 26 august 2026 la 02:24 UTCmonitoring

   Continuăm să monitorizăm ratele îmbunătăţite de livrare a corespondenţei către serviciile poştale Microsoft.

4. 26 august 2026 la 14:07 UTCmonitoring

   În timp ce încă vedem întârzieri în furnizarea de e-mail la serviciile de mail Microsoft, ratele de acceptare sunt în continuă îmbunătățire și actualul backlog a fost aproape complet procesat. Continuăm să monitorizăm performanţele şi vom încheia acest proces odată ce suntem mulţumiţi de ratele de livrare coerente.

5. 27 august 2026 la 14:18 UTCresolved

   Mail continuă să curgă în mod normal și la ratele de livrare preconizate fără întârzieri.

Traducere automată din actualizarea oficială a incidentului.

1. 21 august 2026 la 13:46 UTCinvestigating

   Investigăm în prezent probleme de calitate intermitentă a apelurilor cu transportatorii noştri din amonte

2. 21 august 2026 la 15:07 UTCresolved

   Transportatorul în amonte a rezolvat problemele la aproximativ 9:13am CST

Traducere automată din actualizarea oficială a incidentului.

1. 22 iunie 2026 la 16:59 UTCinvestigating

   Investigăm în prezent probleme cu serverele noastre US East trunchiare care cauzează probleme de finalizare și probleme audio.

2. 22 iunie 2026 la 18:59 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 22 iunie 2026 la 19:38 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 15 iunie 2026 la 12:53 UTCidentified

   În prezent investigăm o problemă cu trunchiurile noastre CA-Est şi le-am dezactivat în acest moment.

2. 15 iunie 2026 la 16:32 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 15 iunie 2026 la 17:48 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 9 iunie 2026 la 19:22 UTCinvestigating

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

2. 9 iunie 2026 la 20:44 UTCinvestigating

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

3. 9 iunie 2026 la 21:04 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. 10 iunie 2026 la 01:16 UTCresolved

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

1. 9 iunie 2026 la 14:27 UTCinvestigating

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

2. 9 iunie 2026 la 14:50 UTCmonitoring

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

3. 9 iunie 2026 la 17:24 UTCresolved

   This incident has been resolved.

1. 1 iunie 2026 la 13:54 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. 1 iunie 2026 la 20:13 UTCresolved

   This incident has been resolved.

1. 31 mai 2026 la 18:03 UTCinvestigating

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

2. 31 mai 2026 la 18:22 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. 31 mai 2026 la 19:48 UTCidentified

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

4. 31 mai 2026 la 21:31 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. 1 iunie 2026 la 00:40 UTCmonitoring

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

6. 1 iunie 2026 la 01:06 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. 1 iunie 2026 la 01:57 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. 1 iunie 2026 la 03:35 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. 1 iunie 2026 la 11:54 UTCresolved

   Connectivity has remained stable.

10. 10 iunie 2026 la 20:52 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. 28 mai 2026 la 17:16 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. 28 mai 2026 la 18:00 UTCmonitoring

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

3. 28 mai 2026 la 18:50 UTCresolved

   This incident has been resolved.

1. 27 aprilie 2026 la 18:26 UTCinvestigating

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

2. 27 aprilie 2026 la 18:51 UTCresolved

   This incident has been resolved.

1. 3 aprilie 2026 la 20:32 UTCinvestigating

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

2. 5 aprilie 2026 la 00:01 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. 8 mai 2026 la 19:22 UTCresolved

   This incident has been resolved.

1. 19 martie 2026 la 14:55 UTCidentified

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

2. 19 martie 2026 la 15:38 UTCresolved

   This incident has been resolved.

1. 13 martie 2026 la 23:52 UTCinvestigating

   We are currently investigating this issue.

2. 14 martie 2026 la 00:41 UTCidentified

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

3. 14 martie 2026 la 01:19 UTCresolved

   This incident has been resolved.

1. 19 februarie 2026 la 14:54 UTCinvestigating

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

2. 19 februarie 2026 la 16:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 februarie 2026 la 16:04 UTCmonitoring

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

4. 19 februarie 2026 la 17:03 UTCresolved

   This incident has been resolved.

1. 15 decembrie 2025 la 18:41 UTCinvestigating

   The team is currently investigating an issue with Clearly Cloud USA

2. 15 decembrie 2025 la 18:42 UTCidentified

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

3. 15 decembrie 2025 la 18:43 UTCmonitoring

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

4. 15 decembrie 2025 la 19:00 UTCresolved

   This incident has been resolved.

1. 4 decembrie 2025 la 18:57 UTCinvestigating

   We are currently investigating this issue.

2. 4 decembrie 2025 la 19:03 UTCmonitoring

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

3. 4 decembrie 2025 la 19:24 UTCresolved

   This incident has been resolved.

1. 2 decembrie 2025 la 16:45 UTCinvestigating

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

2. 2 decembrie 2025 la 17:09 UTCidentified

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

3. 2 decembrie 2025 la 17:30 UTCmonitoring

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

4. 2 decembrie 2025 la 19:46 UTCresolved

   This incident has been resolved.

1. 11 noiembrie 2025 la 19:04 UTCresolved

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

1. 3 noiembrie 2025 la 16:49 UTCinvestigating

   We are currently investigating this issue.

2. 3 noiembrie 2025 la 16:57 UTCidentified

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

3. 3 noiembrie 2025 la 17:29 UTCmonitoring

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

4. 3 noiembrie 2025 la 18:10 UTCresolved

   This incident has been resolved.

5. 4 noiembrie 2025 la 17:13 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.