https://icy-pine-0a983bdf.cronitorstatus.com/historyStatus Page - Incident Feeden-usTue, 14 Jul 2026 09:16:32 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/28b277476d768e48[Unresolved] 2026-07-14 09:16 UTC - "Issue opened on monitor failure." [Resolved] 2026-07-14 09:19 UTC - "Issue resolved on monitor recovery."Tue, 14 Jul 2026 09:16:32 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/28b277476d768e48https://icy-pine-0a983bdf.cronitorstatus.com/history/8dd18dfe8c3f2f21[Investigating] 2026-07-14 09:02 UTC - "We are currently investigating a database performance issues on production related to a application update." [Resolved] 2026-07-14 09:29 UTC - "The relevant application version update has been rolled back resolving this issue."Tue, 14 Jul 2026 09:02:43 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/8dd18dfe8c3f2f21https://icy-pine-0a983bdf.cronitorstatus.com/history/7ecb8b1f9fec7cce[Unresolved] 2026-07-06 07:18 UTC - "Issue opened on monitor failure." [Resolved] 2026-07-06 07:21 UTC - "Issue resolved on monitor recovery."Mon, 06 Jul 2026 07:18:17 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/7ecb8b1f9fec7ccehttps://icy-pine-0a983bdf.cronitorstatus.com/history/35cc887707d88d5d[Identified] 2026-05-27 08:56 UTC - "We have identified an issue with our onboarding service that is preventing new customers from claiming free tier resources. Our engineering team has identified the root cause and is actively working on a fix." [Monitoring] 2026-05-28 15:15 UTC - "Fix has been applied and we are monitoring the creation of free tier resources." [Resolved] 2026-05-28 16:07 UTC - "The issue has been fully resolved. As a result, free tier resources have been granted to all previous requesters."Wed, 27 May 2026 08:56:35 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/35cc887707d88d5dhttps://icy-pine-0a983bdf.cronitorstatus.com/history/e71e3185e30608a5[Unresolved] 2026-05-20 14:19 UTC - "Issue opened on monitor failure." [Resolved] 2026-05-20 14:26 UTC - "Issue resolved on monitor recovery."Wed, 20 May 2026 14:19:57 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/e71e3185e30608a5https://icy-pine-0a983bdf.cronitorstatus.com/history/50dfe0f738e1d407[Investigating] 2026-05-14 22:45 UTC - "We are currently investigating increased error rates related to platform operations." [Monitoring] 2026-05-14 23:10 UTC - "Systems are back online and we're actively monitoring traffic." [Resolved] 2026-05-15 08:34 UTCThu, 14 May 2026 22:45:34 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/50dfe0f738e1d407https://icy-pine-0a983bdf.cronitorstatus.com/history/abb0b1c071f7bed1[Unresolved] 2026-05-14 21:51 UTC - "Issue opened on monitor failure." [Resolved] 2026-05-14 21:55 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-05-14 22:00 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-05-14 22:17 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-05-14 22:24 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-05-14 22:31 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-05-14 22:37 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-05-14 22:41 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-05-14 22:44 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-05-14 23:07 UTC - "Issue resolved on monitor recovery."Thu, 14 May 2026 21:51:27 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/abb0b1c071f7bed1https://icy-pine-0a983bdf.cronitorstatus.com/history/be070283eb431418[Unresolved] 2026-04-23 16:34 UTC - "Issue opened on monitor failure." [Resolved] 2026-04-23 16:36 UTC - "Issue resolved on monitor recovery."Thu, 23 Apr 2026 16:34:01 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/be070283eb431418https://icy-pine-0a983bdf.cronitorstatus.com/history/a5d06b2b2042a126[Unresolved] 2026-04-21 15:25 UTC - "Issue opened on monitor failure." [Resolved] 2026-04-21 15:27 UTC - "Issue resolved on monitor recovery."Tue, 21 Apr 2026 15:25:56 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/a5d06b2b2042a126https://icy-pine-0a983bdf.cronitorstatus.com/history/dab21995ff2dd99c[Unresolved] 2026-04-14 08:52 UTC - "Issue opened on monitor failure." [Resolved] 2026-04-14 08:52 UTC - "Issue resolved on monitor recovery."Tue, 14 Apr 2026 08:52:07 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/dab21995ff2dd99chttps://icy-pine-0a983bdf.cronitorstatus.com/history/b1cde34f9b435789[Unresolved] 2026-04-08 12:59 UTC - "Issue opened on monitor failure." [Resolved] 2026-04-08 13:02 UTC - "Issue resolved on monitor recovery."Wed, 08 Apr 2026 12:59:43 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/b1cde34f9b435789https://icy-pine-0a983bdf.cronitorstatus.com/history/305508a50a603984[Identified] 2026-03-31 11:01 UTC - "We have identified an issue with Google Cloud Bucket listing on data links and working towards a resolution. This impacts the listing and browsing of Google Cloud bucket via the web interface and mounting these to new studio instances." [Identified] 2026-03-31 11:41 UTC - "We have identified the root cause and a fix has been implemented - this is currently being tested and validated in pre-production environments. We expect a full resolution within the next 90 minutes." [Monitoring] 2026-03-31 12:47 UTC - "A fix has been rolled out and we are actively monitoring for errors." [Resolved] 2026-03-31 14:21 UTC - "This incident is being marked as resolved after a period of monitoring and completion of validation within the production environment."Tue, 31 Mar 2026 11:01:48 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/305508a50a603984https://icy-pine-0a983bdf.cronitorstatus.com/history/927cdcee52849564[Unresolved] 2026-03-24 15:36 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-24 15:38 UTC - "Issue resolved on monitor recovery."Tue, 24 Mar 2026 15:36:20 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/927cdcee52849564https://icy-pine-0a983bdf.cronitorstatus.com/history/84861cada889be3e[Unresolved] 2026-03-15 22:42 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-15 22:43 UTC - "Issue resolved on monitor recovery."Sun, 15 Mar 2026 22:42:44 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/84861cada889be3ehttps://icy-pine-0a983bdf.cronitorstatus.com/history/8bff26d11bc6d7cf[Unresolved] 2026-03-12 18:31 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-12 18:34 UTC - "Issue resolved on monitor recovery."Thu, 12 Mar 2026 18:31:18 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/8bff26d11bc6d7cfhttps://icy-pine-0a983bdf.cronitorstatus.com/history/85d9af72678f7141[Identified] 2026-02-20 13:38 UTC - "We have identified an issue with our CDN distributing new wave community artifacts impacting new wave builds and images." [Monitoring] 2026-02-20 14:27 UTC - "We updated our CDN and files are now served correctly. DNS propagation may take a few minutes." [Resolved] 2026-02-20 15:00 UTC - "DNS have correctly been propagated to the working CDN."Fri, 20 Feb 2026 13:38:52 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/85d9af72678f7141https://icy-pine-0a983bdf.cronitorstatus.com/history/96b5980f3aa56231[Unresolved] 2026-02-15 18:06 UTC - "Issue opened on monitor failure." [Resolved] 2026-02-15 18:11 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-02-15 18:14 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-02-15 18:34 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-02-15 18:37 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-02-15 18:41 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-02-15 18:45 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-02-15 19:38 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-02-15 19:41 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-02-15 19:56 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-02-15 19:57 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-02-15 20:24 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-02-15 20:32 UTC - "Issue re-opened on monitor failure." [Monitoring] 2026-02-15 20:51 UTC [Resolved] 2026-02-15 20:51 UTC - "Issue resolved on monitor recovery."Sun, 15 Feb 2026 20:51:31 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/96b5980f3aa56231https://icy-pine-0a983bdf.cronitorstatus.com/history/3511a1634256fc19[Identified] 2026-02-12 16:20 UTC - "We have identified an issue affecting the Fusion distribution endpoint point, which is currently unavailable. We have failed over to our backup distribution source however, full restoration of service is dependent on DNS replication." [Monitoring] 2026-02-12 16:30 UTC - "We have failed over to our backup distribution infrastructure. Full restoration of service is dependent on DNS propagation. We are monitoring traffic levels and will confirm once stable." [Resolved] 2026-02-12 16:55 UTC - "This incident has been resolved. The issue has been linked to an upstream provider failure in our CDN network. Full details can be found here: https://www.cloudflarestatus.com/incidents/79c2573c1n3r"Thu, 12 Feb 2026 16:20:04 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/3511a1634256fc19https://icy-pine-0a983bdf.cronitorstatus.com/history/789db347c11f0eeb[Resolved] 2026-02-10 07:00 UTC - "Wave experienced service disruptions where user authorizations were not properly maintained during an infrastructure update."Tue, 10 Feb 2026 07:00:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/789db347c11f0eebhttps://icy-pine-0a983bdf.cronitorstatus.com/history/1cab98df15c61958[Unresolved] 2026-02-03 23:08 UTC - "Issue opened on monitor failure." [Resolved] 2026-02-03 23:08 UTC - "Issue resolved on monitor recovery."Tue, 03 Feb 2026 23:08:21 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/1cab98df15c61958https://icy-pine-0a983bdf.cronitorstatus.com/history/520817a1dcea8e7c[Unresolved] 2026-01-16 17:40 UTC - "Issue opened on monitor failure." [Resolved] 2026-01-16 17:45 UTC - "Issue resolved on monitor recovery."Fri, 16 Jan 2026 17:40:13 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/520817a1dcea8e7chttps://icy-pine-0a983bdf.cronitorstatus.com/history/01ac2586edff0686[Investigating] 2026-01-05 11:24 UTC - "Issue: Azure Batch compute environment creation is failing for new environments. Azure Batch has deprecated the VM image used by the platform's default configuration, causing environments to remain stuck in "CREATING" state without error messaging. Impact: Affects new Azure Batch compute environment creation via Forge on all platform installations. Existing compute environments (created before ~December 20th) continue to function normally. Manually created compute environments can be created if needed. Status: Fix identified and deployment in progress." [Resolved] 2026-01-05 15:37 UTCMon, 05 Jan 2026 11:24:44 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/01ac2586edff0686https://icy-pine-0a983bdf.cronitorstatus.com/history/70d85645a3370f83[Investigating] 2025-12-16 03:00 UTC - "We are investigating issues with Seqera AI" [Resolved] 2025-12-16 09:39 UTC - "This issue is now resolved."Tue, 16 Dec 2025 03:00:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/70d85645a3370f83https://icy-pine-0a983bdf.cronitorstatus.com/history/c3cf13a2642c207b[Unresolved] 2025-12-11 17:01 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-11 17:11 UTC - "Issue resolved on monitor recovery."Thu, 11 Dec 2025 17:01:43 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/c3cf13a2642c207bhttps://icy-pine-0a983bdf.cronitorstatus.com/history/c65206c4f5b8a6ea[Unresolved] 2025-12-11 12:19 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-11 12:20 UTC - "Issue resolved on monitor recovery."Thu, 11 Dec 2025 12:19:20 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/c65206c4f5b8a6eahttps://icy-pine-0a983bdf.cronitorstatus.com/history/402d8714d749ca84[Identified] 2025-11-18 12:33 UTC - "We're currently tracking issues related to our CDN provider that are impacting our container registry infrastructure. This is resulting in increased error rates when pulling container images from: - community.cr.seqera.io - public.cr.seqera.io - private.cr.seqera.io" [Monitoring] 2025-11-18 14:56 UTC [Monitoring] 2025-11-18 14:56 UTC - "The upstream provider issue has been resolved and we are observing normal operations, we will continue to monitor for any further issues." [Resolved] 2025-11-18 23:15 UTCTue, 18 Nov 2025 12:33:58 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/402d8714d749ca84https://icy-pine-0a983bdf.cronitorstatus.com/history/bdfeac2a89211e45[Unresolved] 2025-11-14 11:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-14 11:29 UTC - "Issue resolved on monitor recovery."Fri, 14 Nov 2025 11:27:46 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/bdfeac2a89211e45https://icy-pine-0a983bdf.cronitorstatus.com/history/61ff0d26105079ab[Unresolved] 2025-11-05 12:02 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-05 12:03 UTC - "Issue resolved on monitor recovery."Wed, 05 Nov 2025 12:02:45 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/61ff0d26105079abhttps://icy-pine-0a983bdf.cronitorstatus.com/history/af7c042609cdce2b[Identified] 2025-10-20 09:00 UTC - "A general outage of DockerHub, Quay and ECR may cause disruption during wave builds. We are monitoring the situation and prepare our systems for when the issues with our service provider resolve." [Monitoring] 2025-10-20 09:42 UTC - "Seems like builds are going back to normal" [Resolved] 2025-10-20 10:08 UTC - "System builds are now restored and functional"Mon, 20 Oct 2025 09:00:26 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/af7c042609cdce2bhttps://icy-pine-0a983bdf.cronitorstatus.com/history/1d80c85b6baa8bea[Identified] 2025-10-20 08:04 UTC - "Due to major AWS outage the requests for Seqera Compute are failing: we are monitoring the general status and will update in 30 minutes" [Identified] 2025-10-20 08:59 UTC - "We are monitoring the situation and prepare our systems for when the issues with our service provider resolve." [Monitoring] 2025-10-20 09:46 UTC - "We confirmed that Seqera Compute executions are successfully submitted: we keep monitoring for errors or degradation of service" [Resolved] 2025-10-20 10:07 UTC - "The system is now restored"Mon, 20 Oct 2025 08:04:40 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/1d80c85b6baa8beahttps://icy-pine-0a983bdf.cronitorstatus.com/history/d7acddae3ce3fbc5[Unresolved] 2025-09-18 22:45 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-18 22:47 UTC - "Issue resolved on monitor recovery."Thu, 18 Sep 2025 22:45:01 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/d7acddae3ce3fbc5https://icy-pine-0a983bdf.cronitorstatus.com/history/92e88fabccd7fc2a[Unresolved] 2025-08-20 19:11 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-20 19:12 UTC - "Issue resolved on monitor recovery."Wed, 20 Aug 2025 19:11:40 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/92e88fabccd7fc2ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/5423495ff9d699da[Identified] 2025-08-14 11:00 UTC - "An issue has been identified that is preventing Seqera Compute CEs from being created or destroyed. The issue has been located and a fix is currently in progress. This only impacts Seqera Compute users and only CE creation and destruction." [Resolved] 2025-08-14 17:39 UTC - "A fix has been pushed that has corrected this issue and it has been confirmed that no impact should have been encountered by any users."Thu, 14 Aug 2025 11:00:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/5423495ff9d699dahttps://icy-pine-0a983bdf.cronitorstatus.com/history/e34a99796a971ab7[Investigating] 2025-07-10 14:00 UTC [Resolved] 2025-07-10 15:21 UTC - "An update to quota handling temporarily limited new active runs for a subset of customers. The issue was quickly reversed and resolved after testing and customer confirmation. Process improvements are underway to prevent recurrence."Thu, 10 Jul 2025 14:00:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/e34a99796a971ab7https://icy-pine-0a983bdf.cronitorstatus.com/history/77acf1e48df25940[Unresolved] 2025-06-03 06:03 UTC - "Issue opened on monitor failure." [Resolved] 2025-06-03 06:16 UTC - "Issue resolved on monitor recovery."Tue, 03 Jun 2025 06:03:27 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/77acf1e48df25940https://icy-pine-0a983bdf.cronitorstatus.com/history/409ec8104f7ec1c4[Unresolved] 2025-04-23 07:08 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-23 07:21 UTC - "Issue resolved on monitor recovery."Wed, 23 Apr 2025 07:08:24 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/409ec8104f7ec1c4https://icy-pine-0a983bdf.cronitorstatus.com/history/1698bc2635ae6dd4[Unresolved] 2025-04-23 07:07 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-23 07:21 UTC - "Issue resolved on monitor recovery."Wed, 23 Apr 2025 07:07:13 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/1698bc2635ae6dd4https://icy-pine-0a983bdf.cronitorstatus.com/history/13dd529dde69771a[Unresolved] 2025-04-08 10:04 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-08 10:19 UTC - "Issue resolved on monitor recovery."Tue, 08 Apr 2025 10:04:49 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/13dd529dde69771ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/189b7d361c8699ac[Unresolved] 2025-03-30 00:57 UTC - "Post-maintenance Redis issues have caused intermittent Wave availability for some users." [Resolved] 2025-03-30 20:00 UTC - "The related Redis issue has been identified and resolved. This issue has been confirmed to be corrected."Sun, 30 Mar 2025 00:57:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/189b7d361c8699achttps://icy-pine-0a983bdf.cronitorstatus.com/history/0e95437628bc14bb[Unresolved] 2025-03-20 07:54 UTC - "Issue opened on monitor failure." [Resolved] 2025-03-20 08:12 UTC - "Issue resolved on monitor recovery."Thu, 20 Mar 2025 07:54:54 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/0e95437628bc14bbhttps://icy-pine-0a983bdf.cronitorstatus.com/history/f4dcec8e6506fe4c[Unresolved] 2025-03-20 07:54 UTC - "Issue opened on monitor failure." [Resolved] 2025-03-20 08:12 UTC - "Issue resolved on monitor recovery."Thu, 20 Mar 2025 07:54:45 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/f4dcec8e6506fe4chttps://icy-pine-0a983bdf.cronitorstatus.com/history/7ef49c1d614b8675[Investigating] 2025-03-06 09:54 UTC - "We are investigating an issue affecting the workflows running on Google Batch compute environments: executions are not affected but log fetching is returning an error. Our team is working on a fix" [Identified] 2025-03-06 11:35 UTC - "Team is working on a fix that may have been caused by a dependency mismatch." [Monitoring] 2025-03-06 14:07 UTC - "Fix has been deployed to Production environment and it is currently under test" [Resolved] 2025-03-06 14:43 UTC - "Fix has been tested in production and confirmed pipelines' logs are now available again on Google based Compute environments"Thu, 06 Mar 2025 09:54:06 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/7ef49c1d614b8675https://icy-pine-0a983bdf.cronitorstatus.com/history/67d760a3781c4106[Unresolved] 2025-02-26 12:22 UTC - "Issue opened on monitor failure." [Identified] 2025-02-26 12:34 UTC - "During a production upgrade the database wasn't able to perform a migration: we are working to scale the database instance vertically" [Resolved] 2025-02-26 12:39 UTC - "Issue resolved on monitor recovery."Wed, 26 Feb 2025 12:22:53 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/67d760a3781c4106https://icy-pine-0a983bdf.cronitorstatus.com/history/f2c1269a412c28fb[Unresolved] 2025-02-26 12:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-26 12:25 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-02-26 12:26 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-02-26 12:41 UTC - "Issue resolved on monitor recovery."Wed, 26 Feb 2025 12:21:57 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/f2c1269a412c28fbhttps://icy-pine-0a983bdf.cronitorstatus.com/history/200ca91769ed5131[Unresolved] 2025-02-26 09:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-26 09:58 UTC - "Issue resolved on monitor recovery."Wed, 26 Feb 2025 09:46:58 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/200ca91769ed5131https://icy-pine-0a983bdf.cronitorstatus.com/history/b60f813a3e4c0b8a[Unresolved] 2025-02-26 09:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-26 09:57 UTC - "Issue resolved on monitor recovery."Wed, 26 Feb 2025 09:46:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/b60f813a3e4c0b8ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/abd56954d97784e8[Unresolved] 2025-02-13 17:19 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-13 17:20 UTC - "Issue resolved on monitor recovery."Thu, 13 Feb 2025 17:19:03 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/abd56954d97784e8https://icy-pine-0a983bdf.cronitorstatus.com/history/a3968afb35df6e15[Unresolved] 2025-01-22 11:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-22 11:51 UTC - "Issue resolved on monitor recovery."Wed, 22 Jan 2025 11:46:05 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/a3968afb35df6e15https://icy-pine-0a983bdf.cronitorstatus.com/history/40d58401005379df[Unresolved] 2025-01-22 11:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-22 11:50 UTC - "Issue resolved on monitor recovery."Wed, 22 Jan 2025 11:46:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/40d58401005379dfhttps://icy-pine-0a983bdf.cronitorstatus.com/history/3f54227ecc96bdf1[Unresolved] 2024-12-23 18:05 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-23 18:27 UTC - "Issue resolved on monitor recovery."Mon, 23 Dec 2024 18:05:07 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/3f54227ecc96bdf1https://icy-pine-0a983bdf.cronitorstatus.com/history/a6c6e8ef4166fe5f[Unresolved] 2024-12-23 18:04 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-23 18:26 UTC - "Issue resolved on monitor recovery."Mon, 23 Dec 2024 18:04:40 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/a6c6e8ef4166fe5fhttps://icy-pine-0a983bdf.cronitorstatus.com/history/69f0750f8c2144da[Unresolved] 2024-12-23 18:04 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-23 18:26 UTC - "Issue resolved on monitor recovery."Mon, 23 Dec 2024 18:04:37 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/69f0750f8c2144dahttps://icy-pine-0a983bdf.cronitorstatus.com/history/34e18abf73495af6[Unresolved] 2024-12-18 09:49 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-18 09:53 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-18 09:55 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-18 10:01 UTC - "Issue resolved on monitor recovery."Wed, 18 Dec 2024 09:49:27 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/34e18abf73495af6https://icy-pine-0a983bdf.cronitorstatus.com/history/d1e4e6022d975c38[Unresolved] 2024-12-18 09:46 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-18 09:58 UTC - "Issue resolved on monitor recovery."Wed, 18 Dec 2024 09:46:51 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/d1e4e6022d975c38https://icy-pine-0a983bdf.cronitorstatus.com/history/da649a2dc59b30d0[Unresolved] 2024-12-15 18:12 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-15 18:14 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-15 18:38 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-15 18:44 UTC - "Issue resolved on monitor recovery."Sun, 15 Dec 2024 18:12:18 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/da649a2dc59b30d0https://icy-pine-0a983bdf.cronitorstatus.com/history/f3fe3f565e645347[Unresolved] 2024-12-15 18:11 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-15 18:15 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-15 18:38 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-15 18:42 UTC - "Issue resolved on monitor recovery."Sun, 15 Dec 2024 18:11:28 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/f3fe3f565e645347https://icy-pine-0a983bdf.cronitorstatus.com/history/98e1aed1f2968fa7[Unresolved] 2024-12-15 17:43 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-15 17:44 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-15 18:18 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-15 18:37 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-15 19:22 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-15 19:26 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-15 19:39 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-15 19:42 UTC - "Issue resolved on monitor recovery."Sun, 15 Dec 2024 17:43:28 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/98e1aed1f2968fa7https://icy-pine-0a983bdf.cronitorstatus.com/history/95fa42c7e6ff5c2a[Identified] 2024-11-27 15:32 UTC - "Seqera AI (https://seqera.io/ask-ai/) has been reporting intermittent failures Engineering identified the issue with an upstream vendor" [Monitoring] 2024-11-27 16:06 UTC - "Our engineering team has not reported any new failure since 15:47 UTC" [Monitoring] 2024-11-27 16:22 UTC - "The upstream vendor reported pushing a fix to their system Engineering continues monitoring the status of Seqera AI" [Resolved] 2024-11-27 19:01 UTC - "Engineering reports the incident has been resolved"Wed, 27 Nov 2024 15:32:58 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/95fa42c7e6ff5c2ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/c717c2e31e45d108[Unresolved] 2024-11-05 08:41 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-05 08:45 UTC - "Issue resolved on monitor recovery."Tue, 05 Nov 2024 08:41:40 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/c717c2e31e45d108https://icy-pine-0a983bdf.cronitorstatus.com/history/04a1e413cf1e09c3[Unresolved] 2024-11-04 17:15 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-04 17:30 UTC - "Issue resolved on monitor recovery."Mon, 04 Nov 2024 17:15:48 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/04a1e413cf1e09c3https://icy-pine-0a983bdf.cronitorstatus.com/history/c57c30032f1389b2[Investigating] 2024-10-08 15:28 UTC - "We are currently investigating reports of performance issues related to data-studios in Seqera Cloud Platform & hosting environment" [Resolved] 2024-10-08 15:39 UTCTue, 08 Oct 2024 15:28:49 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/c57c30032f1389b2https://icy-pine-0a983bdf.cronitorstatus.com/history/473f7ba2b0779d90[Investigating] 2024-10-01 12:08 UTC - "We are aware of an issue impacting the wave-build service , our engineers are actively investigating this issue and will update with time to resolution shortly." [Monitoring] 2024-10-01 12:18 UTC - "We have identified the root cause of the outage and have remediated the issue." [Resolved] 2024-10-01 12:45 UTC - "Wave build is operating normally - utilization has returned to expected levels."Tue, 01 Oct 2024 12:08:16 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/473f7ba2b0779d90https://icy-pine-0a983bdf.cronitorstatus.com/history/77592c85e7c81a78[Unresolved] 2024-07-31 21:34 UTC - "Issue opened on monitor failure." [Resolved] 2024-07-31 21:37 UTC - "Issue resolved on monitor recovery."Wed, 31 Jul 2024 21:34:32 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/77592c85e7c81a78https://icy-pine-0a983bdf.cronitorstatus.com/history/a9408f07e4f2b54a[Identified] 2024-07-17 19:43 UTC - "It has been detected that the Seqera Platform Cloud is unavailable. The cause has been immediately determined and a fix is underway." [Resolved] 2024-07-17 19:53 UTC - "The issue has been identified and resolved."Wed, 17 Jul 2024 19:43:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/a9408f07e4f2b54ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/6544a701f9532de4[Monitoring] 2024-07-11 18:26 UTC - "We have identified an issue with Seqera Cloud that was preventing it from loading. We have potentially resolved the issue and are confirming the fix before marking this issue as closed." [Resolved] 2024-07-11 18:33 UTC - "The issue was identified to be an infrastructure problem that has been rectified. No further issues should remain."Thu, 11 Jul 2024 18:26:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/6544a701f9532de4https://icy-pine-0a983bdf.cronitorstatus.com/history/52ce1e9e0e621a4d[Unresolved] 2024-07-08 22:07 UTC - "Issue opened on monitor failure." [Resolved] 2024-07-08 22:35 UTC - "Issue resolved on monitor recovery."Mon, 08 Jul 2024 22:07:46 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/52ce1e9e0e621a4dhttps://icy-pine-0a983bdf.cronitorstatus.com/history/39d78dd3602bd061[Investigating] 2024-07-03 14:21 UTC - "An issue has been reporting in which some users are getting errors reporting "missing required parameters" on pipelines that were previously operating correctly. We are currently investigating the issue." [Resolved] 2024-07-03 15:44 UTC - "This issue has been identified and a workaround resolution has been discovered. Multiple customers reported 'Missing required parameter:' errors like: * Missing required parameter: --input * Missing required parameter: --outdir while executing pipelines that previously ran without incident. The error was replicated on Seqera Platform by leaving the 'pipeline parameters' field empty in the Launchpad pipeline configuration empty and supplying parameters via the schema-defined form only. The error is bypassed if any parameter is supplied via 'pipeline parameters' in the Launchpad configuration. Affected customers can use this as a workaround, adding to pipeline Launchpad configuration any parameter common to workflow executions."Wed, 03 Jul 2024 14:21:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/39d78dd3602bd061https://icy-pine-0a983bdf.cronitorstatus.com/history/2ec88b567afa7f8b[Identified] 2024-07-03 11:30 UTC - "We have identified a degraded service event affecting certain pipeline conditions for cloud users and those on enterprise version 24.1.0. The issue impacts users of nf-core pipelines or pipelines based on the nf-core template, specifically those relying on shared configs from https://nf-co.re/configs/ or those custom configs where an external includeConfig is utilized. Under these circumstances, new pipelines within these parameters cannot be created or launched. Our team is currently investigating the issue, and a fix will be released shortly." [Resolved] 2024-07-03 13:52 UTC - "A patch for Seqera Platform Cloud has been released and this should no longer be impacting Cloud users. A patch for enterprise is imminent and this incident will be closed for now as no existing enterprise users are affected by this."Wed, 03 Jul 2024 11:30:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/2ec88b567afa7f8bhttps://icy-pine-0a983bdf.cronitorstatus.com/history/099b4982bbe8383a[Identified] 2024-07-03 10:40 UTC - "An issue has been identified in which the execution of pipelines may have been affected due to a bug introduced by the upgrade of a library used by the platform to serialize/deserialize some data stored in our caching layer." [Resolved] 2024-07-03 14:00 UTC - "The problem has been solved and pipelines executions suffering from this issue should be working properly now."Wed, 03 Jul 2024 10:40:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/099b4982bbe8383ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/894a6815eb08b167[Investigating] 2024-05-11 12:48 UTC - "Wave is reporting errors causing it to be unavailable for a subset of nextflow/platform users." [Identified] 2024-05-11 15:15 UTC - "The issue was determined to be caused by a Redis cache problem, affecting only customers using the old platform endpoint https://api.tower.nf ." [Resolved] 2024-05-11 15:28 UTC - "No further issues should exist." [Resolved] 2024-05-11 15:28 UTCSat, 11 May 2024 12:48:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/894a6815eb08b167https://icy-pine-0a983bdf.cronitorstatus.com/history/c8d5ebdb9acbb1a8[Identified] 2024-04-30 14:00 UTC - "A recent update to Wave caused inconsistency in the composition of container names which may have resulted in some users being unable to run pipelines relying on Wave." [Resolved] 2024-04-30 20:00 UTC - "This change has been rolled back and should no longer cause issues." [Resolved] 2024-04-30 20:44 UTCTue, 30 Apr 2024 14:00:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/c8d5ebdb9acbb1a8https://icy-pine-0a983bdf.cronitorstatus.com/history/28d320de8a966888[Unresolved] 2024-04-25 08:23 UTC - "Issue opened on monitor failure." [Resolved] 2024-04-25 08:24 UTC - "Issue resolved on monitor recovery."Thu, 25 Apr 2024 08:23:49 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/28d320de8a966888https://icy-pine-0a983bdf.cronitorstatus.com/history/c38b0d84f0106872[Unresolved] 2024-04-25 08:20 UTC - "Issue opened on monitor failure." [Resolved] 2024-04-25 08:22 UTC - "Issue resolved on monitor recovery."Thu, 25 Apr 2024 08:20:35 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/c38b0d84f0106872https://icy-pine-0a983bdf.cronitorstatus.com/history/f9bbf4a3ca1488ab[Unresolved] 2024-03-22 23:20 UTC - "Start of Wave errors Retroactively, it was discovered that transient spikes in Wave container errors had occurred causing temporary degradation of service and impacting a limited number of customers." [Investigating] 2024-03-24 07:37 UTC - "A potential issue with the Wave service has been discovered impacting a limited number of clients." [Identified] 2024-03-24 11:56 UTC - "Wave issues have been confirmed and a potential cause has been pinpointed." [Resolved] 2024-03-24 18:30 UTC - "A change has been pushed to the Seqera platform that has remedied the problem. The initial issue was caused by a misconfiguration that was exhausting the available connection pool." [Resolved] 2024-03-24 23:20 UTC - "Retroactively, it was discovered that transient spikes in Wave container errors had occurred causing temporary degradation of service and impacting a limited number of customers." [Investigating] 2024-04-22 23:20 UTC - "Initial errors with wave service"Fri, 22 Mar 2024 23:20:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/f9bbf4a3ca1488abhttps://icy-pine-0a983bdf.cronitorstatus.com/history/fbbdd38aa87f2d81[Identified] 2024-01-11 15:00 UTC - "An issue has been identified that is causing jobs in Platform Cloud to stall in the "Submitted" state." [Resolved] 2024-01-11 16:30 UTC - "The problem was caused by a stuck thread in our job scheduler component that was preventing job submissions from being performed correctly. We restarted the service and implemented a code fix to prevent the scenario from happening again. All stalled jobs should now be proceeding as normal."Thu, 11 Jan 2024 15:00:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/fbbdd38aa87f2d81https://icy-pine-0a983bdf.cronitorstatus.com/history/d9350ba04afad7fb[Investigating] 2023-11-27 01:55 UTC - "A timeout issue has been identified that is impacting users of Wave containers [HTTP status=408]." [Resolved] 2023-11-27 08:29 UTC - "The issue has been identified and resolved."Mon, 27 Nov 2023 01:55:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/d9350ba04afad7fbhttps://icy-pine-0a983bdf.cronitorstatus.com/history/d22b2d34bed5ee32[Unresolved] 2023-11-14 21:30 UTC - "An incident with quay.io container registry is impacting the launch of data pipelines on Seqera Enterprise on-prem installations. We are monitoring the problem. Please contact Seqera support for more details." [Resolved] 2023-11-14 23:50 UTC - "The incident was solved by quay.io team."Tue, 14 Nov 2023 21:30:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/d22b2d34bed5ee32https://icy-pine-0a983bdf.cronitorstatus.com/history/dc3175f1487525a8[Investigating] 2023-11-01 04:10 UTC [Resolved] 2023-11-01 10:04 UTC - "An "Expired License Error" prevented a small number of users running pipelines on AWS Batch from launching pipelines between midnight and 09:00 CET on November 1st. We have now fixed the issue and we will be implementing solutions to prevent this from happening in the future. We apologize for any inconvenience this may have caused."Wed, 01 Nov 2023 04:10:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/dc3175f1487525a8https://icy-pine-0a983bdf.cronitorstatus.com/history/b2b71d7d6e8e83fe[Investigating] 2023-10-11 20:50 UTC - "A temporary connection failure has been reported by some users. We are investigating the possible problem." [Resolved] 2023-10-11 21:30 UTC - "A failure during the rollout of a system upgrade caused some backend replicas not to reach the ready status, resulting in a temporary system unreliability."Wed, 11 Oct 2023 20:50:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/b2b71d7d6e8e83fehttps://icy-pine-0a983bdf.cronitorstatus.com/history/9a8608e5ad55856a[Resolved] 2023-10-02 12:20 UTC - "An issue has been identified in the Wave service that caused a partial system outage from Fri, September 30 15:30 until Mon, October 2 12:20. The problem is related to a bug in Java HTTP client used by Wave backend to access remote repositories, which caused the system to consume the Java VM heap memory in an uncontrolled manner and exhaust the underlying threads pool handling the incoming client requests. https://bugs.openjdk.org/browse/JDK-8308144 A solution has been delivered to prevent this problem."Mon, 02 Oct 2023 12:20:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/9a8608e5ad55856ahttps://icy-pine-0a983bdf.cronitorstatus.com/history/af4d768f503a1350[Unresolved] 2023-10-01 08:35 UTC - "Issue opened on monitor failure." [Resolved] 2023-10-01 08:44 UTC - "Issue resolved on monitor recovery."Sun, 01 Oct 2023 08:35:54 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/af4d768f503a1350https://icy-pine-0a983bdf.cronitorstatus.com/history/6498e8ddfbf2d2f2[Unresolved] 2023-10-01 05:27 UTC - "Issue opened on monitor failure." [Resolved] 2023-10-01 05:35 UTC - "Issue resolved on monitor recovery."Sun, 01 Oct 2023 05:27:30 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/6498e8ddfbf2d2f2https://icy-pine-0a983bdf.cronitorstatus.com/history/251109c69b968f94[Unresolved] 2023-10-01 01:33 UTC - "Issue opened on monitor failure." [Resolved] 2023-10-01 01:42 UTC - "Issue resolved on monitor recovery."Sun, 01 Oct 2023 01:33:24 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/251109c69b968f94https://icy-pine-0a983bdf.cronitorstatus.com/history/d05f20c5cb87c331[Unresolved] 2023-09-30 14:30 UTC - "Issue opened on monitor failure." [Resolved] 2023-09-30 14:30 UTC - "Issue resolved on monitor recovery."Sat, 30 Sep 2023 14:30:00 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/d05f20c5cb87c331https://icy-pine-0a983bdf.cronitorstatus.com/history/8ee15cd0048ae60a[Unresolved] 2023-09-29 13:58 UTC - "Issue opened on monitor failure." [Resolved] 2023-09-29 14:14 UTC - "Issue resolved on monitor recovery."Fri, 29 Sep 2023 13:58:39 +0000https://icy-pine-0a983bdf.cronitorstatus.com/history/8ee15cd0048ae60a