Istoricul incidentelor Circleapp

1. 5 octombrie 2026 la 09:44 UTCinvestigating

   În prezent investigăm această problemă.

2. 5 octombrie 2026 la 10:21 UTCresolved

   Acest incident a fost rezolvat. Incidentul a fost cauzat de o configurare lipsă în aplicația pe care o folosim pentru a implementa modificări de cod în aplicația Cercul. După investigaţii, am aplicat imediat un plasture temporar pentru a restabili disponibilitatea. Apoi am identificat cauza principală și am implementat o fixare permanentă. Toate serviciile funcţionează normal.

3. 5 octombrie 2026 la 15:46 UTCpostmortem

   ##### Rezumat Aplicație cerc experimentat un incident între 5:44 și 5:57 AM EST Ne cerem scuze pentru întrerupere. Ce s-a întâmplat? Incidentul a fost cauzat de o configurare lipsă în aplicația pe care o folosim pentru a implementa noi modificări de cod în aplicația Cercul #### Metuation and imediat fixs La investigarea problemei, am rezolvat imediat această cerere cu o modificare temporară care a restabilit disponibilitatea aplicației. Mai târziu, am identificat cauza principală și am aplicat o fixare definitivă. Status Toate serviciile funcționează în mod normal.

Traducere automată din actualizarea oficială a incidentului.

1. 3 octombrie 2026 la 08:13 UTCinvestigating

   În prezent investigăm această problemă.

2. 3 octombrie 2026 la 08:18 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 1 septembrie 2026 la 13:59 UTCinvestigating

   În prezent investigăm această problemă.

2. 1 septembrie 2026 la 15:43 UTCresolved

   Mai devreme astăzi, am avut parte de o scurtă întrerupere a serviciului de la ora 9:59:10:50 ET în timpul unei actualizări de securitate programate. Serviciul a fost restaurat complet, şi am pus garanţii pentru a preveni acest lucru din nou. Ne cerem scuze pentru neplăceri.

Traducere automată din actualizarea oficială a incidentului.

1. 27 august 2026 la 22:25 UTCinvestigating

   În prezent investigăm această problemă.

2. 27 august 2026 la 22:30 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 17:51 UTCinvestigating

   În prezent investigăm această problemă.

2. 20 august 2026 la 17:54 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 13:04 UTCinvestigating

   În prezent investigăm această problemă.

Traducere automată din actualizarea oficială a incidentului.

1. 19 august 2026 la 08:52 UTCinvestigating

   În prezent investigăm această problemă.

2. 19 august 2026 la 09:15 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 28 mai 2026 la 16:44 UTCinvestigating

   We are currently investigating this issue.

2. 28 mai 2026 la 17:12 UTCidentified

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

3. 28 mai 2026 la 18:46 UTCmonitoring

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

4. 28 mai 2026 la 20:12 UTCresolved

   The issue has been fully resolved and all systems are operating normally. A detailed post-mortem report will be published here shortly. Thank you for your patience and cooperation.

5. 1 iunie 2026 la 15:06 UTCpostmortem

   ## Delays in Asynchronous Actions and Workflows ‌ **Issue Summary** On May 28, 2026, we experienced an incident that caused delays in asynchronous actions and automated workflows. **Timeline \(UTC\)** * **11:29** – The issue began, causing delays in newly scheduled automated workflows. * **15:51** – Our engineering team identified the root cause of the scheduling interruption. * **16:42** – A fix was deployed, restoring normal operations to the background processing framework. * **18:45** – The resulting backlog of delayed tasks was completely cleared and normal service was confirmed. **Root Cause** A routine system update included a software dependency upgrade that unexpectedly conflicted with our background processing framework. This conflict prevented scheduled background jobs from moving into the active processing queue. As a result, automated workflows and other asynchronous actions were delayed, though no underlying data was lost or corrupted during this time. **Resolution** Upon investigating the anomaly in the scheduling queue, our engineering team determined that the recent dependency upgrade was responsible. We immediately reverted the update, which restored the flow of scheduled tasks. To resolve the issue as swiftly as possible, we temporarily scaled up our infrastructure's processing capacity to rapidly clear the backlog of delayed actions. **Preventative Measures** To prevent this type of issue from occurring in the future, we are planning on implementing the following improvements: * **Enhanced Alerting:** We are deploying strict, automated alerts specifically designed to detect anomalies in scheduled task queues, drastically reducing our time to detection. * **Upgraded Telemetry:** We are adding granular, time-series visualizations to our monitoring systems to better track the exact states of background jobs \(scheduled, enqueued, and processed\) in real time. We sincerely apologize for any disruption this may have caused to your operations. The issue was fully mitigated, and all backlogged tasks have been successfully processed.

1. 22 mai 2026 la 13:26 UTCinvestigating

   We are currently investigating this issue.

2. 22 mai 2026 la 19:20 UTCresolved

   This incident has been resolved.

1. 20 mai 2026 la 16:12 UTCinvestigating

   We are currently investigating this issue.

2. 20 mai 2026 la 16:15 UTCresolved

   This incident has been resolved.

1. 9 mai 2026 la 03:12 UTCinvestigating

   We are currently investigating this issue.

2. 9 mai 2026 la 03:43 UTCresolved

   This incident has been resolved.

1. 30 aprilie 2026 la 18:00 UTCinvestigating

   We are currently investigating this issue.

2. 30 aprilie 2026 la 19:43 UTCresolved

   This incident has been resolved.

3. 30 aprilie 2026 la 19:43 UTCpostmortem

   Some users experienced an issue where app.circle.so was unavailable. This was caused by the Redis cluster reaching 100% CPU due to a large volume of workflow jobs being re-enqueued. We identified the root cause, scaled down the background deployment pods to relieve the load, and restored service within approximately 3 minutes. We are continuing to investigate and address the underlying issue.

1. 30 aprilie 2026 la 14:35 UTCinvestigating

   We are currently investigating this issue.

2. 30 aprilie 2026 la 15:39 UTCresolved

   This incident has been resolved.

1. 30 aprilie 2026 la 11:36 UTCinvestigating

   We are currently investigating this issue.

2. 30 aprilie 2026 la 12:19 UTCresolved

   This incident has been resolved.

1. 30 aprilie 2026 la 10:45 UTCinvestigating

   We are currently investigating this issue.

2. 30 aprilie 2026 la 11:03 UTCresolved

   This incident has been resolved.

1. 19 aprilie 2026 la 16:50 UTCinvestigating

   We are currently investigating this issue.

2. 19 aprilie 2026 la 18:32 UTCresolved

   This incident has been resolved.

1. 19 aprilie 2026 la 01:01 UTCinvestigating

   We are currently investigating this issue.

2. 19 aprilie 2026 la 05:23 UTCresolved

   This incident has been resolved.

1. 17 aprilie 2026 la 18:53 UTCinvestigating

   We are currently investigating this issue.

2. 17 aprilie 2026 la 19:01 UTCresolved

   This incident has been resolved.

1. 15 aprilie 2026 la 20:01 UTCresolved

   Search functionality was degraded starting at approximately 6:52 PM EDT on April 14. The issue was caused by Elasticsearch cluster degradation. An incident report was filed internally. This issue should have had a status page entry since customers reported broken search. Customers checking [status.circle.so](http://status.circle.so) saw 'All Systems Operational' during this period.

2. 15 aprilie 2026 la 20:01 UTCpostmortem

   Search functionality was degraded starting at approximately 6:52 PM EDT on April 14. The issue was caused by Elasticsearch cluster degradation. An incident report was filed internally. This issue should have had a status page entry since customers reported broken search. Customers checking [status.circle.so](http://status.circle.so/) saw 'All Systems Operational' during this period.

1. 14 aprilie 2026 la 04:17 UTCinvestigating

   We are currently investigating this issue.

2. 14 aprilie 2026 la 04:36 UTCresolved

   This incident has been resolved.

3. 15 aprilie 2026 la 19:50 UTCpostmortem

   Communities experienced approximately 19 minutes of downtime starting at 12:17 AM EDT. The database crashed due to an out-of-memory error at the infrastructure level, a known AWS RDS bug. Our team raised a second escalation to AWS \(case 177616832700336\), and both cases have been escalated to AWS's highest priority tier. We are actively working with AWS to resolve the underlying infrastructure issue and have additional safeguards in place.