Circleapp driftsforstyrrelser

1. 5. oktober 2026 kl. 09.44 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 5. oktober 2026 kl. 10.21 UTCresolved

   Denne hændelse er blevet løst. Hændelsen skyldtes en manglende konfiguration i det program vi bruger til at implementere kodeændringer til Circle programmet. Efter undersøgelse, vi straks anvendt en midlertidig patch for at genoprette tilgængeligheden. Derefter identificerede vi årsagen og implementerede et permanent fix. Alle tjenester fungerer normalt.

3. 5. oktober 2026 kl. 15.46 UTCpostmortem

   # # # # Oversigt Circle applikation oplevede en hændelse mellem 5: 44 og 5: 57 AM EST Vi beklager forstyrrelsen. Hvad skete der? Hændelsen skyldtes en manglende konfiguration i programmet vi bruger til at implementere nye kodeændringer til Circle programmet Mitigation og øjeblikkelige rettelser Når vi undersøger problemet, vi straks lappet denne ansøgning med en midlertidig ændring, der gendannede ansøgning tilgængelighed. Senere i dag identificerede vi årsagen og anvendte en definitiv løsning. Status Alle tjenester fungerer i øjeblikket normalt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. oktober 2026 kl. 08.13 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 3. oktober 2026 kl. 08.18 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. september 2026 kl. 13.59 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 1. september 2026 kl. 15.43 UTCresolved

   Tidligere i dag, oplevede vi en kort service afbrydelse fra 9: 59- 10: 50 AM ET under en planlagt sikkerhedsopdatering. Tjenesten er blevet genoprettet, og vi har sat sikkerhedsforanstaltninger på plads for at forhindre dette i at ske igen. Vi undskylder for ulejligheden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 22.25 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 27. august 2026 kl. 22.30 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. august 2026 kl. 17.51 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 20. august 2026 kl. 17.54 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. august 2026 kl. 13.04 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. august 2026 kl. 08.52 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 19. august 2026 kl. 09.15 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 28. maj 2026 kl. 16.44 UTCinvestigating

   We are currently investigating this issue.

2. 28. maj 2026 kl. 17.12 UTCidentified

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

3. 28. maj 2026 kl. 18.46 UTCmonitoring

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

4. 28. maj 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 13.26 UTCinvestigating

   We are currently investigating this issue.

2. 22. maj 2026 kl. 19.20 UTCresolved

   This incident has been resolved.

1. 20. maj 2026 kl. 16.12 UTCinvestigating

   We are currently investigating this issue.

2. 20. maj 2026 kl. 16.15 UTCresolved

   This incident has been resolved.

1. 9. maj 2026 kl. 03.12 UTCinvestigating

   We are currently investigating this issue.

2. 9. maj 2026 kl. 03.43 UTCresolved

   This incident has been resolved.

1. 30. april 2026 kl. 18.00 UTCinvestigating

   We are currently investigating this issue.

2. 30. april 2026 kl. 19.43 UTCresolved

   This incident has been resolved.

3. 30. april 2026 kl. 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. april 2026 kl. 14.35 UTCinvestigating

   We are currently investigating this issue.

2. 30. april 2026 kl. 15.39 UTCresolved

   This incident has been resolved.

1. 30. april 2026 kl. 11.36 UTCinvestigating

   We are currently investigating this issue.

2. 30. april 2026 kl. 12.19 UTCresolved

   This incident has been resolved.

1. 30. april 2026 kl. 10.45 UTCinvestigating

   We are currently investigating this issue.

2. 30. april 2026 kl. 11.03 UTCresolved

   This incident has been resolved.

1. 19. april 2026 kl. 16.50 UTCinvestigating

   We are currently investigating this issue.

2. 19. april 2026 kl. 18.32 UTCresolved

   This incident has been resolved.

1. 19. april 2026 kl. 01.01 UTCinvestigating

   We are currently investigating this issue.

2. 19. april 2026 kl. 05.23 UTCresolved

   This incident has been resolved.

1. 17. april 2026 kl. 18.53 UTCinvestigating

   We are currently investigating this issue.

2. 17. april 2026 kl. 19.01 UTCresolved

   This incident has been resolved.

1. 15. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 04.17 UTCinvestigating

   We are currently investigating this issue.

2. 14. april 2026 kl. 04.36 UTCresolved

   This incident has been resolved.

3. 15. april 2026 kl. 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.