Incidents | Infactory Incidents reported on status page for Infactory https://status.infactory.ai/ https://d1lppblt9t2x15.cloudfront.net/logos/dfac47a6e3a2ad94ed201e1e99f53fcf.png Incidents | Infactory https://status.infactory.ai/ en daily-api.infactory.ai/docs recovered https://status.infactory.ai/ Thu, 02 Oct 2025 12:22:58 +0000 https://status.infactory.ai/#5f39057d96a84f7014ee5afd34b4cf1acb64384827c0c9f77df02eb378fa7820 daily-api.infactory.ai/docs recovered daily-api.infactory.ai/docs went down https://status.infactory.ai/ Thu, 02 Oct 2025 12:17:57 +0000 https://status.infactory.ai/#5f39057d96a84f7014ee5afd34b4cf1acb64384827c0c9f77df02eb378fa7820 daily-api.infactory.ai/docs went down staging-api.infactory.ai/docs recovered https://status.infactory.ai/ Fri, 26 Sep 2025 19:41:16 +0000 https://status.infactory.ai/#50ee9c8457e5b917d34b89ce7351c46b0f147bca0cfd5c571cc3f80c106fc75a staging-api.infactory.ai/docs recovered staging-api.infactory.ai/docs went down https://status.infactory.ai/ Fri, 26 Sep 2025 19:36:13 +0000 https://status.infactory.ai/#50ee9c8457e5b917d34b89ce7351c46b0f147bca0cfd5c571cc3f80c106fc75a staging-api.infactory.ai/docs went down staging-api.infactory.ai/docs recovered https://status.infactory.ai/ Mon, 22 Sep 2025 17:01:57 +0000 https://status.infactory.ai/#02dafdfc6bf92b2ae937b14d5e2c90e1a6a9378d3fe0fe2235ef42d5913b26d1 staging-api.infactory.ai/docs recovered staging-api.infactory.ai/docs went down https://status.infactory.ai/ Mon, 22 Sep 2025 16:56:55 +0000 https://status.infactory.ai/#02dafdfc6bf92b2ae937b14d5e2c90e1a6a9378d3fe0fe2235ef42d5913b26d1 staging-api.infactory.ai/docs went down daily-api.infactory.ai/docs recovered https://status.infactory.ai/ Fri, 19 Sep 2025 12:17:31 +0000 https://status.infactory.ai/#4aa0997a63b48eb176f64d25f37d8860a9176cada0618d53b925b019a5b6efbe daily-api.infactory.ai/docs recovered daily-api.infactory.ai/docs went down https://status.infactory.ai/ Fri, 19 Sep 2025 12:12:19 +0000 https://status.infactory.ai/#4aa0997a63b48eb176f64d25f37d8860a9176cada0618d53b925b019a5b6efbe daily-api.infactory.ai/docs went down dev-api.infactory.ai/docs recovered https://status.infactory.ai/ Thu, 18 Sep 2025 03:50:57 +0000 https://status.infactory.ai/#969e71eae11b123f85ca09466d343b414cf49f4ccbd27751f76996e8d63012bd dev-api.infactory.ai/docs recovered dev-api.infactory.ai/docs went down https://status.infactory.ai/ Thu, 18 Sep 2025 03:28:35 +0000 https://status.infactory.ai/#969e71eae11b123f85ca09466d343b414cf49f4ccbd27751f76996e8d63012bd dev-api.infactory.ai/docs went down daily-api.infactory.ai/docs recovered https://status.infactory.ai/ Thu, 04 Sep 2025 12:17:32 +0000 https://status.infactory.ai/#5a42f1313c7e6a2f96f3a43255cfe44a2578cae75e34127b5d1d711fc53ebd31 daily-api.infactory.ai/docs recovered daily-api.infactory.ai/docs went down https://status.infactory.ai/ Thu, 04 Sep 2025 12:12:30 +0000 https://status.infactory.ai/#5a42f1313c7e6a2f96f3a43255cfe44a2578cae75e34127b5d1d711fc53ebd31 daily-api.infactory.ai/docs went down daily-api.infactory.ai/docs recovered https://status.infactory.ai/ Sat, 23 Aug 2025 12:15:18 +0000 https://status.infactory.ai/#f2a0d2de3226c6e868d8eb5eecf0766423616eb147cd65959db8adcc34b83dd3 daily-api.infactory.ai/docs recovered daily-api.infactory.ai/docs went down https://status.infactory.ai/ Sat, 23 Aug 2025 12:10:12 +0000 https://status.infactory.ai/#f2a0d2de3226c6e868d8eb5eecf0766423616eb147cd65959db8adcc34b83dd3 daily-api.infactory.ai/docs went down dev-api.infactory.ai/docs recovered https://status.infactory.ai/ Tue, 19 Aug 2025 22:54:43 +0000 https://status.infactory.ai/#6da79d975aa593d0c9031561e3202a024a34d149094feb71cf1005f31936c578 dev-api.infactory.ai/docs recovered dev-api.infactory.ai/docs went down https://status.infactory.ai/ Tue, 19 Aug 2025 22:49:34 +0000 https://status.infactory.ai/#6da79d975aa593d0c9031561e3202a024a34d149094feb71cf1005f31936c578 dev-api.infactory.ai/docs went down dev-api.infactory.ai/docs recovered https://status.infactory.ai/ Tue, 19 Aug 2025 21:53:41 +0000 https://status.infactory.ai/#e57d7b936a6ae12d1683cc5486ff072b54726870347b10254da374f6ab5f811a dev-api.infactory.ai/docs recovered dev-api.infactory.ai/docs went down https://status.infactory.ai/ Tue, 19 Aug 2025 21:44:33 +0000 https://status.infactory.ai/#e57d7b936a6ae12d1683cc5486ff072b54726870347b10254da374f6ab5f811a dev-api.infactory.ai/docs went down dev-api.infactory.ai/docs recovered https://status.infactory.ai/ Tue, 19 Aug 2025 20:39:27 +0000 https://status.infactory.ai/#c506a38cd065319a66418eab9af41a266e3e02ff02c062f167467cdc2b52b05d dev-api.infactory.ai/docs recovered dev-api.infactory.ai/docs went down https://status.infactory.ai/ Tue, 19 Aug 2025 20:09:31 +0000 https://status.infactory.ai/#c506a38cd065319a66418eab9af41a266e3e02ff02c062f167467cdc2b52b05d dev-api.infactory.ai/docs went down dev-api.infactory.ai/docs recovered https://status.infactory.ai/ Tue, 12 Aug 2025 21:42:57 +0000 https://status.infactory.ai/#00f58d2f295d82b8484e6a762e0e74905379dbad376888be425cf9da77937665 dev-api.infactory.ai/docs recovered dev-api.infactory.ai/docs went down https://status.infactory.ai/ Tue, 12 Aug 2025 21:37:45 +0000 https://status.infactory.ai/#00f58d2f295d82b8484e6a762e0e74905379dbad376888be425cf9da77937665 dev-api.infactory.ai/docs went down dev-api.infactory.ai/docs recovered https://status.infactory.ai/ Tue, 05 Aug 2025 17:53:09 +0000 https://status.infactory.ai/#a956a9baa827ca1baf9816dcb112a1e6b222370adfc4989162b81bd36a6b0bb6 dev-api.infactory.ai/docs recovered dev-api.infactory.ai/docs went down https://status.infactory.ai/ Tue, 05 Aug 2025 17:47:47 +0000 https://status.infactory.ai/#a956a9baa827ca1baf9816dcb112a1e6b222370adfc4989162b81bd36a6b0bb6 dev-api.infactory.ai/docs went down Upgrade to encrypt data at rest https://status.infactory.ai/incident/674656 Fri, 01 Aug 2025 19:00:00 -0000 https://status.infactory.ai/incident/674656#94e257c2bb31bf8bf2bfef4a2222c310a2d0f0c6962fd9778c252747db31a99a Maintenance completed Upgrade to encrypt data at rest https://status.infactory.ai/incident/674656 Fri, 01 Aug 2025 19:00:00 -0000 https://status.infactory.ai/incident/674656#94e257c2bb31bf8bf2bfef4a2222c310a2d0f0c6962fd9778c252747db31a99a Maintenance completed Upgrade to encrypt data at rest https://status.infactory.ai/incident/674656 Fri, 01 Aug 2025 17:30:00 -0000 https://status.infactory.ai/incident/674656#514ac5a9d1728e277767149f3c120f0a5220bc1586e0db592c38c5c36bca8b19 The Infactory platform will be offline for a system upgrade to encrypt data at rest. This improves the security of your data on our platform and adds additional protections. Upgrade to encrypt data at rest https://status.infactory.ai/incident/674656 Fri, 01 Aug 2025 17:30:00 -0000 https://status.infactory.ai/incident/674656#514ac5a9d1728e277767149f3c120f0a5220bc1586e0db592c38c5c36bca8b19 The Infactory platform will be offline for a system upgrade to encrypt data at rest. This improves the security of your data on our platform and adds additional protections. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549453 Wed, 23 Apr 2025 05:30:00 -0000 https://status.infactory.ai/incident/549453#992a18cd9d1b27014262cbc9f0070169c173b151bef11d8acd6d16b1ba7dfe0a Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549453 Wed, 23 Apr 2025 05:30:00 -0000 https://status.infactory.ai/incident/549453#992a18cd9d1b27014262cbc9f0070169c173b151bef11d8acd6d16b1ba7dfe0a Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549453 Wed, 23 Apr 2025 04:45:00 -0000 https://status.infactory.ai/incident/549453#6b4a3bbc65e6cc23e06b552acaad2f91c38f776dade2682a2b9f24526211dad1 During this scheduled downtime, the Infactory platform MAIN cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549453 Wed, 23 Apr 2025 04:45:00 -0000 https://status.infactory.ai/incident/549453#6b4a3bbc65e6cc23e06b552acaad2f91c38f776dade2682a2b9f24526211dad1 During this scheduled downtime, the Infactory platform MAIN cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549246 Tue, 22 Apr 2025 22:30:00 -0000 https://status.infactory.ai/incident/549246#a78e607510d36089a629e4be866d72b8a81031920d46314394f0ea6a8d32e06d Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549246 Tue, 22 Apr 2025 22:30:00 -0000 https://status.infactory.ai/incident/549246#a78e607510d36089a629e4be866d72b8a81031920d46314394f0ea6a8d32e06d Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549246 Tue, 22 Apr 2025 20:15:15 -0000 https://status.infactory.ai/incident/549246#9c3a693c5dc95867db383ff67c45835cd116c46a96b5cd6e3d9c5f2f32868e05 During this scheduled downtime, the Infactory platform STAGING cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549246 Tue, 22 Apr 2025 20:15:15 -0000 https://status.infactory.ai/incident/549246#9c3a693c5dc95867db383ff67c45835cd116c46a96b5cd6e3d9c5f2f32868e05 During this scheduled downtime, the Infactory platform STAGING cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 17:30:00 -0000 https://status.infactory.ai/incident/549159#73c4ae7ed9f239904b95a0b7d08a02edcc611d7e7170643f6882d25552735834 Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 17:30:00 -0000 https://status.infactory.ai/incident/549159#73c4ae7ed9f239904b95a0b7d08a02edcc611d7e7170643f6882d25552735834 Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 17:30:00 -0000 https://status.infactory.ai/incident/549159#73c4ae7ed9f239904b95a0b7d08a02edcc611d7e7170643f6882d25552735834 Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 17:30:00 -0000 https://status.infactory.ai/incident/549159#73c4ae7ed9f239904b95a0b7d08a02edcc611d7e7170643f6882d25552735834 Maintenance completed Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 16:30:00 -0000 https://status.infactory.ai/incident/549159#b927868c86eb25fb8c236a136d2a28fa023a20999741939fff69e8077a61e308 During this scheduled downtime, the Infactory platform dev cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 16:30:00 -0000 https://status.infactory.ai/incident/549159#b927868c86eb25fb8c236a136d2a28fa023a20999741939fff69e8077a61e308 During this scheduled downtime, the Infactory platform dev cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 16:30:00 -0000 https://status.infactory.ai/incident/549159#b927868c86eb25fb8c236a136d2a28fa023a20999741939fff69e8077a61e308 During this scheduled downtime, the Infactory platform dev cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems. Kubernetes cluster upgrade from version 1.30 to version 1.32 https://status.infactory.ai/incident/549159 Tue, 22 Apr 2025 16:30:00 -0000 https://status.infactory.ai/incident/549159#b927868c86eb25fb8c236a136d2a28fa023a20999741939fff69e8077a61e308 During this scheduled downtime, the Infactory platform dev cluster will be undergoing a Kubernetes version upgrade from version 1.30 to version 1.32. This extends the standard support window provided by Amazon Web Services (AWS) until spring 2026 from the current end date of July 22, 2025, adds automatic cleanup of unused PersistentVolumeClaims from StatefulSets, enhances security with restricted anonymous authentication, and brings more efficient memory allocation to the Kubernetes stack. Additionally, AWS container insights will be enabled that provides pod-level metrics across all namespaces, node health metrics beyond basic EC2 data, and links between container issues and infrastructure problems.