Aqua driftsforstyrrelser

1. 31. august 2026 kl. 17.18 UTCinvestigating

   Siden ca. 09: 00 UTC den 31. august 2025, vores Supply Chain sårbarhedsscanning service har oplevet en nedbrydning. Dette er i øjeblikket årsag CI / CD pipeline timeouts og timeouts på Supply Chain side. Vores team er aktivt efterforsker og har engageret de relevante interne hold til at arbejde hen imod løsning. Vi vil dele opdateringer, når de bliver tilgængelige. Vi undskylder for alt det besvær, det medfører.

2. 31. august 2026 kl. 19.18 UTCidentified

   Aqua Supply Chain sårbarhedsscanning Service Disruption Notice - Update: Emne Identified Siden omkring 09: 00 UTC den August 31, 2025, vores Supply Chain sårbarhed Scanning service har oplevet en nedbrydning, forårsager CI / CD pipeline timeouts og timeouts på Supply Chain side. Opdatering: Vores team har identificeret roden årsag som forhøjet belastning på scanningen motor, som påvirkede database ydeevne. En rettelse er i øjeblikket anvendes og rullet ud. Vi vil fortsætte med at levere opdateringer som oprensning skrider frem. Vi undskylder for ulejligheden.

3. 31. august 2026 kl. 19.24 UTCmonitoring

   Aqua Supply Chain Vulnerability Scanning Service Disruption Notice - Update: Fix Anvendt Siden omkring 09: 00 UTC den August 31, 2025, vores Supply Chain sårbarhed Scanning service oplevede en nedbrydning, forårsager CI / CD pipeline timeouts og timeouts på Supply Chain side. Opdatering: Rodårsagen - forhøjet belastning på scanningen backend påvirker databasens ydeevne er blevet behandlet. En rettelse er blevet anvendt, og tjenesten er i øjeblikket under aktiv overvågning for at bekræfte fuld inddrivelse. Vi vil give en yderligere opdatering, når hændelsen er helt løst. Vi undskylder for den ulejlighed, det har forårsaget.

4. 31. august 2026 kl. 19.30 UTCresolved

   Aqua Supply Chain sårbarhedsscanning Service Disruption Notice - Løs Siden omkring 09: 00 UTC den August 31, 2025, vores Supply Chain sårbarhed Scanning service oplevede en nedbrydning, forårsager CI / CD pipeline timeouts og timeouts på Supply Chain side. Opdatering: Den anvendte fix er blevet bekræftet effektiv efter en periode med aktiv overvågning, og tjenesten er vendt tilbage til normal drift. Forsyningskædens sårbarhedsscanning-komponentstatus er blevet opdateret til operativ. Vi undskylder for ulejligheden denne hændelse kan have forårsaget og tak for din tålmodighed.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 31. august 2026 kl. 17.15 UTCresolved

   Siden ca. 09: 00 UTC den 31. august 2025, vores Supply Chain sårbarhedsscanning service har oplevet en nedbrydning. Dette er i øjeblikket årsag CI / CD pipeline timeouts og timeouts på Supply Chain side. Vores team er aktivt efterforsker og har engageret de relevante interne hold til at arbejde hen imod løsning. Vi vil dele opdateringer, når de bliver tilgængelige. Vi undskylder for alt det besvær, det medfører.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. oktober 2025 kl. 15.01 UTCmonitoring

   We are currently experiencing issues with some internal systems due to an ongoing incident with our cloud provider. As a result, certain services or operations may be temporarily unavailable or perform slower than usual. Our public cloud provider is actively working to mitigate this issue on priority. We will continue to provide updates as more information becomes available. Thank you for your understanding.

2. 20. oktober 2025 kl. 23.49 UTCmonitoring

   We are continuing to monitor residual effects from the earlier cloud provider incident. Some users may experience occasional slow logins or degraded performance in certain areas of the product. Our team is actively investigating this behavior to confirm whether it is related to the prior outage or an internal issue. We will share further updates as soon as we have more information. Thank you for your patience and understanding.

3. 21. oktober 2025 kl. 01.52 UTCresolved

   The issues affecting login performance have been mitigated, and services are now operating normally. We continue to monitor the situation to ensure stability. Thank you for your patience and understanding.

1. 1. oktober 2025 kl. 18.06 UTCresolved

   On October 1st, 2025, at approximately 08:10 AM UTC, our Container Image Scanning service experienced a performance degradation. This caused the resulting in partial impact on scanning requests. The Aqua team promptly identified the issue and engaged the India team for resolution. The incident was mitigated at 08:56 AM UTC on October 1st, 2025. We apologize for any inconvenience caused by this disruption. To prevent recurrence, we are enhancing our monitoring and alerting systems and implementing automated remediation measures where possible.

1. 8. september 2025 kl. 08.34 UTCinvestigating

   Login to the system is currently unavailable. Our team is investigating and working to restore access as quickly as possible.

2. 8. september 2025 kl. 09.14 UTCmonitoring

   The issue affecting logins has been identified and a fix has been implemented. We are currently monitoring the system to ensure stability.

3. 8. september 2025 kl. 10.55 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 8. september 2025 kl. 10.55 UTCresolved

   This incident has been resolved.

1. 30. juni 2025 kl. 09.03 UTCinvestigating

   We're currently experiencing login issues with our production platform in the us-east-1 region (https://cloud.aquasec.com/). Our team is actively investigating and working to resolve the issue as quickly as possible. This disruption is due to an Aqua CSPM outage in us-east-1, which is affecting Aqua SaaS UI sign-ins. Although the console may be temporarily inaccessible, please note that deployed enforcers remain operational and workload protection is not impacted.

2. 30. juni 2025 kl. 09.22 UTCresolved

   This incident has been resolved.

1. 28. november 2024 kl. 13.47 UTCinvestigating

   We are currently observing elevated scan queue activity in the Image Scanning feature within Workload Protection. As a result, you may experience slight delays in scan processing. Impact: While most scans are processing as expected, some may take longer than usual. All other Aqua platform functionalities remain unaffected. Next Steps: Our team is actively investigating the situation and working to ensure normal scan performance is restored as quickly as possible.

2. 28. november 2024 kl. 14.01 UTCidentified

   We have identified the root cause of elevated scan queue activity affecting the Image Scanning feature in Workload Protection. This may result in slight delays for some scan processes. Impact: While most scans are progressing as expected, some may experience minor delays. Other Aqua platform functionalities are operating normally. Current Status: Our team is actively working on implementing a fix to restore optimal scan performance.

3. 28. november 2024 kl. 14.33 UTCmonitoring

   We will be deploying a fix in the next 30 minutes to address the ongoing issue and we will closely monitor the system to ensure stability and performance.

4. 28. november 2024 kl. 17.06 UTCresolved

   The issue with the scan queue activity in the Image Scanning feature within Workload Protection has been resolved. The fix has been successfully deployed. All services are back to normal and fully operational.

1. 30. oktober 2024 kl. 20.28 UTCidentified

   We are currently experiencing partial interruptions with login capabilities on our production platform in the US-EAST-1 region. This is due to throttling issues affecting our CSPM database.Our engineering team is actively working to mitigate the throttling issue in the CSPM database and restore full login functionality. Some users may still experience intermittent login difficulties.We apologize for the inconvenience and appreciate your patience as we work to resolve this issue.

2. 30. oktober 2024 kl. 21.10 UTCresolved

   The login issues in the US-EAST-1 region have now been fully resolved. All services are back to normal and fully operational.

1. 25. oktober 2024 kl. 11.44 UTCidentified

   We've identified an issue impacting CSPM service performance in the EU region. Customers may experience increased latency or service interruptions. Our engineering team is actively working on a resolution.

2. 25. oktober 2024 kl. 12.17 UTCresolved

   The CSPM service performance latency issue in the EU region has been resolved. All services are now fully functional and operational.

1. 7. oktober 2024 kl. 15.55 UTCidentified

   CSPM scanning is currently experiencing intermittent disruptions in the US region due to a database issue. This is preventing scans from running as expected. Users in the US may encounter delays or interruptions in CSPM scan results. We are actively working to resolve the database issue and restore normal CSPM scanning operations

2. 7. oktober 2024 kl. 20.06 UTCresolved

   The CSPM scanning issue has been successfully resolved, and all scanning operations are now fully functional and operational

1. 29. august 2024 kl. 10.13 UTCresolved

   We encountered UI login issues with our production platform in the Asia-1 region(https://asia-1.cloud.aquasec.com/). Our team worked diligently to address the problem and restore access. The platform team has swiftly resolved the issue, and the application is now fully operational and functional.

1. 27. august 2024 kl. 18.28 UTCresolved

   On August 21st, 2023, at approximately 8:30 PM UTC, our Container Image Scanning service experienced a major disruption due to a lambda function exceeding its ephemeral storage limit. The lambda, responsible for downloading and extracting a critical database for image scanning, was configured with 3GB of ephemeral storage. However, the extracted database size of 2.5GB, combined with the 500MB zip archive, exhausted the available storage, causing the lambda to enter a panic state. This resulted in a service outage, impacting container image scanning capabilities. Although monitoring was in place for various components, an alert specifically based on lambda panics was missing, delaying proactive identification and remediation. The Aqua Fields team promptly identified the issue and engaged the on-call channel. However, due to the unavailability of the US team and the late hour in India, response time was impacted. The India team resolved the incident at 10:52 PM UTC on August 21st by increasing the lambda's ephemeral storage. We apologize for any inconvenience caused by this disruption. We are taking steps to improve our monitoring and alerting capabilities, including implementing automated remediation where possible, to prevent similar incidents in the future.

1. 25. maj 2024 kl. 20.16 UTCidentified

   The Aqua Cloud Platform is using LaunchDarkly for Feature Flag toggles. LaunchDarkly experienced a problem with their platform, which is under investigation by LaunchDarkly team. https://status.launchdarkly.com/. Sorry for the inconvenient, we will update soon.

2. 25. maj 2024 kl. 20.35 UTCidentified

   Login to Aqua SaaS Platform back to normal in all regions. Unfortunetly you may experience some UI issues due to the LaunchDarkly incident.

3. 25. maj 2024 kl. 20.45 UTCmonitoring

   All users are now able to log in and access the Aqua SaaS Platform. We are continuing to monitor.

4. 25. maj 2024 kl. 21.01 UTCresolved

   This incident has been resolved.

1. 2. maj 2024 kl. 06.38 UTCinvestigating

   We are currently experiencing an outage affecting login capabilities on our production platform across geographies as a result of an ongoing issue with the jsDelivr CDN. Our team is tirelessly working to resolve the issue and restore access.

2. 2. maj 2024 kl. 07.34 UTCidentified

   We identified the issue and the fix will be implemented soon.

3. 2. maj 2024 kl. 07.56 UTCresolved

   We have restored the services, Application is now operational & fully functional.

1. 10. april 2024 kl. 08.36 UTCinvestigating

   Due to the outage of Aqua CSPM DB in us-east-1, we are experiencing service disruptions in our Aqua SaaS main service. Service impact: Due to the Aqua CSPM outage in us-east-1, Aqua SaaS Service including sign-in and scan reporting, as well as all other pages in the Aqua UI are experiencing high latency and error rates. While the console may not be accessible, deployed enforcers are still running, and workload protection is not impacted.

2. 10. april 2024 kl. 08.37 UTCinvestigating

   We are continuing investigating this issue , we found the root cause.

3. 10. april 2024 kl. 08.38 UTCidentified

   The issue has been identify and fix was implemented successfully.

4. 10. april 2024 kl. 08.39 UTCmonitoring

   A fix was implemented and now we are monitoring closely CSPM services

5. 10. april 2024 kl. 11.11 UTCresolved

   This incident has been resolved.

1. 13. juni 2023 kl. 19.41 UTCinvestigating

   Due to the outage of AWS us-east-1, we are experiencing service disruptions in our Aqua SaaS main service. AWS Health Status page: https://health.aws.amazon.com/health/status Service impact: Due to the AWS outage in us-east-1, Aqua SaaS Service including sign-in and scan reporting, as well as all other pages in the Aqua UI are experiencing high latency and error rates. While the console may not be accessible, deployed enforcers are still running, and workload protection is not impacted.

2. 13. juni 2023 kl. 21.07 UTCinvestigating

   We are continuing to investigate this issue.

3. 13. juni 2023 kl. 21.08 UTCresolved

   We are pleased to inform you that our services have been restored and Aqua Console is now available. We apologize for any inconvenience caused by the AWS US-EASR-1 Outage disruption AWS Health Status page: https://health.aws.amazon.com/health/status All systems are now functioning as expected. If you continue to experience any issues or have any concerns, please don't hesitate to contact our support team at support.aquasec.com. We are here to assist you and ensure a smooth experience using our services. Thank you for your continued trust and support.

1. 22. maj 2023 kl. 12.42 UTCresolved

   This incident has been resolved.

1. 7. december 2021 kl. 20.48 UTCinvestigating

   Due to AWS outage on us-east-1 we are experiencing service disruptions: https://status.aws.amazon.com

2. 7. december 2021 kl. 20.51 UTCmonitoring

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

3. 8. december 2021 kl. 08.55 UTCresolved

   This incident has been resolved.

1. 15. marts 2021 kl. 20.54 UTCinvestigating

   Microsoft AD appears to be experiencing a global outage, which is impacting Aqua's ability to obtain credentials needed to perform CSPM scans. During this time, scan reports may be delayed or incomplete.

2. 15. marts 2021 kl. 21.51 UTCresolved

   The Azure AD incident appears to be largely resolved and CSPM scans are completing as scheduled at this point. Please note that you may continue to see "New Risk" alerts if the scan checks have toggled between "unknown" and failing states.

1. 25. november 2020 kl. 15.02 UTCmonitoring

   Aqua Wave is currently monitoring elevated error rates from some AWS APIs. These errors are preventing Aqua Wave from running complete scans, so we have temporarily disabled scheduled scans.

2. 25. november 2020 kl. 15.22 UTCmonitoring

   The AWS outage is also impacting Cognito, which may affect the ability to sign in using SSO. If you require a break-glass user and do not currently have one, please contact our support.

3. 25. november 2020 kl. 15.40 UTCmonitoring

   We are continuing to monitor elevated AWS error rates affecting CloudWatch, Cognito, Kinesis, and other services (see the AWS status page for more information: https://status.aws.amazon.com/). This is currently impacting Aqua Wave in the following ways: - Sign in via SAML/SSO may be degraded. Standard sign in is not impacted. - Scheduled background scans may be delayed - Scans may produce "new risk" or "unknown" results for impacted services

4. 25. november 2020 kl. 15.49 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 25. november 2020 kl. 17.08 UTCmonitoring

   We are continuing to monitor increased error rates from AWS in us-east-1. At this time, Aqua Wave's core APIs are not impacted, but background scanning continues to remain affected due to the use of AWS CloudWatch APIs.

6. 25. november 2020 kl. 18.47 UTCmonitoring

   We are continuing to monitor elevated AWS error rates across numerous AWS services. All Aqua Wave APIs are currently functioning as expected. CSPM background scans continue to run at a reduced interval. Technical details: CSPM background scans are normally triggered by CloudWatch Event rules, which are currently not operational due to an outage in AWS us-east-1. However, our failover workflow has been implemented which will continue to trigger these scans at reduced capacity until AWS CloudWatch is fully restored in us-east-1. During this time, you may find that scan reports are delayed. For example, if your scan is scheduled to run hourly, it may run 10-15 minutes after the hour at staggered intervals instead. CSPM Real-Time Events are typically triggered via CloudWatch Event rules deployed in the user environment. You may see delayed or missing events in us-east-1 during the outage window as these rules are unlikely to be triggered. The CSPM Real-Time Events service is still operational and available to receive the events that are sent. AWS CloudTrail is also experiencing a partial outage which may result in delayed or missing delivery of events from source AWS accounts to Aqua Wave.

7. 25. november 2020 kl. 20.06 UTCmonitoring

   Aqua Wave is continuing to monitor an ongoing incident in AWS. The impact is currently limited to CSPM background scan schedules and the triggering of real-time events from user accounts in us-east-1. We will continue to provide updates when we have new information to share, but at this point, will not publish any new updates unless we receive a status change from AWS or different issues are detected.

8. 25. november 2020 kl. 23.32 UTCresolved

   AWS services appear to be recovering and at this time, all core Aqua Wave functionality has returned to normal operation.