Ten incydent został rozwiązany.
Incydent został spowodowany brakującą konfiguracją aplikacji używanej do wprowadzenia zmian kodu do aplikacji Circle. Po śledztwie, natychmiast zastosowaliśmy tymczasową łatę, aby przywrócić dostępność. Następnie zidentyfikowaliśmy przyczynę i wdrożyliśmy stałe rozwiązanie.
Wszystkie usługi działają normalnie.
postmortem
Podsumowanie
Program Circle doświadczył incydentu między 5: 44 a 5: 57 AM EST
Przepraszamy za zakłócenia.
Co się stało?
Incydent został spowodowany brakującą konfiguracją aplikacji używanej do wprowadzenia nowych zmian kodu do aplikacji Circle
- Łagodzenie i natychmiastowe poprawki
Po zbadaniu problemu, natychmiast naprawiliśmy tę aplikację tymczasową zmianą, która przywróciła dostępność aplikacji.
Później dziś zidentyfikowaliśmy przyczynę i zastosowaliśmy ostateczne rozwiązanie.
Status
Wszystkie usługi funkcjonują obecnie normalnie.
Dziś doświadczyliśmy krótkiego zakłócenia służby od 9: 59- 10: 50 ET podczas planowanej aktualizacji bezpieczeństwa. Usługa została w pełni przywrócona, i wprowadziliśmy zabezpieczenia, aby zapobiec temu ponownie. Przepraszamy za wszelkie niedogodności.
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
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.
postmortem
## 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.
app.circle.so is down
Początek 22 maja 2026 13:26 UTC · 2m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
app.circle.so is down
Początek 20 maja 2026 16:12 UTC · 1m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
app.circle.so is down
Początek 9 maja 2026 03:12 UTC · 1m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
app.circle.so is down
Początek 30 kwietnia 2026 18:00 UTC · 1h 43m
Pending
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
postmortem
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.
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.
postmortem
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.
app.circle.so is down
Początek 14 kwietnia 2026 04:17 UTC · 4m
IssuesDrobny incydent
investigating
We are currently investigating this issue.
resolved
This incident has been resolved.
postmortem
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.
