Incidents reported on status page for ForestAdmin https://status.forestadmin.com/ https://d1lppblt9t2x15.cloudfront.net/logos/04e7b65522a4f1c717ce29311fa7a377.png https://status.forestadmin.com/ en https://status.forestadmin.com/incident/600252 Wed, 11 Jun 2025 07:05:00 -0000 https://status.forestadmin.com/incident/600252#d339a5a75087dbeb32b7475d0f4dcd65085e0aa28bd563bff94e688e00787463 The issue with our provider has been fully resolved. All services are back up and running normally. We apologize for any inconvenience this may have caused and thank you for your patience. https://status.forestadmin.com/incident/600252 Tue, 10 Jun 2025 18:04:00 -0000 https://status.forestadmin.com/incident/600252#fcf522ca87ae64b5f0df15f8fe139d8543368c98d8c530e7b82479a66bacae28 We've mitigated the issue by deploying our application on AWS. The application should be back but custom domains are still not working. If you are on a custom domain, please add app.forestadmin.com to your CORS configuration and access https://app.forestadmin.com instead. https://status.forestadmin.com/ Tue, 10 Jun 2025 18:02:09 +0000 https://status.forestadmin.com/#ea27cc58a8e3ec7ae8015325e790f400e71e847132a340d7321e681ebf731abd Web App recovered https://status.forestadmin.com/ Tue, 10 Jun 2025 17:46:06 +0000 https://status.forestadmin.com/#ea27cc58a8e3ec7ae8015325e790f400e71e847132a340d7321e681ebf731abd Web App went down https://status.forestadmin.com/ Tue, 10 Jun 2025 17:44:07 +0000 https://status.forestadmin.com/#62702c2b5f3944ca47b8b4f8010dcbb0258f5fbaf6972b63284ed4e046b1e7c4 Web App recovered https://status.forestadmin.com/ Tue, 10 Jun 2025 15:34:31 +0000 https://status.forestadmin.com/#62702c2b5f3944ca47b8b4f8010dcbb0258f5fbaf6972b63284ed4e046b1e7c4 Web App went down https://status.forestadmin.com/incident/600252 Tue, 10 Jun 2025 15:34:00 -0000 https://status.forestadmin.com/incident/600252#d8a68ec9a351635b436084f43f42a1384a062cc1531add9d91004577d1b28228 We are currently experiencing a service disruption due to an ongoing outage at our hosting provider, Heroku. You can follow their status updates here: https://status.heroku.com/incidents/2822. Our technical team is actively investigating the impact on our services and is closely monitoring the situation. We will continue to provide updates here as we learn more. Thank you for your patience and understanding. https://status.forestadmin.com/incident/535013 Wed, 26 Mar 2025 16:22:00 -0000 https://status.forestadmin.com/incident/535013#62359c27944c56d301bd67724e639478a745305a405d3762f63d9dbc8a1ce285 Public API is now restored https://status.forestadmin.com/incident/535013 Wed, 26 Mar 2025 16:01:00 -0000 https://status.forestadmin.com/incident/535013#24bde2f9715f4a01f720f7a598210460977a5c9ea6ce98f5dd350b1ca6bf9203 Outage started at 17:01 (GMT+1) Outage ended at 17:22 (GMT+1) Servers have stopped responding to requests due to incorrect configuration. After a reconfiguration, systems have been able to start up properly and we could answer to requests. https://docs.forestadmin.com/public-api https://status.forestadmin.com/incident/500527 Wed, 22 Jan 2025 11:47:00 -0000 https://status.forestadmin.com/incident/500527#1d733066eba9a7048ff52acf1dc4a520130ab74ed18fea5870771b4286737933 The issue is now resolved. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience. https://status.forestadmin.com/incident/500527 Wed, 22 Jan 2025 11:17:00 -0000 https://status.forestadmin.com/incident/500527#52fc997e46b5a07a25049e3b383fe6864f2c64f21fd3210b63f9ed3a377f0444 We have identified the source of the issue and are rolling back one of this morning's releases to resolve it. https://status.forestadmin.com/incident/500527 Wed, 22 Jan 2025 09:48:00 -0000 https://status.forestadmin.com/incident/500527#1e0777c4aef5abd6349dd99cf7ec75e1c7b140a1075cb1296c991a52e915a18f We’re currently investigating reports of a potential issue on Smart Charts and Alter values. We apologize for any inconvenience and will post another update as soon as we learn more. https://status.forestadmin.com/incident/498634 Mon, 20 Jan 2025 09:51:00 -0000 https://status.forestadmin.com/incident/498634#1c6e3a328260a3a4ffd63731ad42b7b3ff4f28ac36520e6771294c2a7883f56a The issue is now resolved. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience. https://status.forestadmin.com/incident/498634 Mon, 20 Jan 2025 09:38:00 -0000 https://status.forestadmin.com/incident/498634#cc4d519eb7a9ccaad69635a374e7548e963e3175792de87b95c216bf7e5ec739 We identified the cause of the hidden collections issue some clients were experiencing. Those affected were using the new folder feature. They were able to generate unexpected requests that resulted in folders being created but not listed. As a result, after a refresh, those folders and their contents would disappear. We have addressed the issue on our backend, and a migration is currently underway to fix the affected projects. The issue should be resolved within a few minutes. We are still investigating how these requests were generated. https://status.forestadmin.com/incident/498634 Fri, 17 Jan 2025 16:00:00 -0000 https://status.forestadmin.com/incident/498634#fdf8e2b75068cbb1b9f4d350b7805cabb86bfe1f5c98de831fd760893807156a Some customers have reported that their collections are not visible. We are currently investigating the issue. https://status.forestadmin.com/incident/492534 Wed, 08 Jan 2025 10:49:00 -0000 https://status.forestadmin.com/incident/492534#187c54888e361e14c754c53ad7afa01c072bbbec0aa545cb905206fec67400e3 A migration of our database has been incorrectly propagated across our instances, preventing some of our customers to have access to their project. https://status.forestadmin.com/incident/492534 Wed, 08 Jan 2025 10:33:00 -0000 https://status.forestadmin.com/incident/492534#cfade7fd47bb0df1280cd9c1c695508b3bf7cac34f02f3c26a1228f8fe3b8948 The service is back to normal! We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience. We are still investigating the reason behind. https://status.forestadmin.com/incident/492534 Wed, 08 Jan 2025 10:19:00 -0000 https://status.forestadmin.com/incident/492534#cc9066daa4c9d5899296f2756c89543dfccea7adceababaacecb1cccbc18d1dc We are currently experiencing a service outage. This outage has affected our api. The engineering team is working to identify the root cause and fix the issue. We apologize for any inconvenience and we'll keep you updated on the status. https://status.forestadmin.com/incident/479158 Mon, 16 Dec 2024 17:34:00 -0000 https://status.forestadmin.com/incident/479158#3e69795946456345cbbcace16c23729b15f784cc18556d5bec041a4e0c9886f7 We released a contribution that introduced a regression on some project. Some of their collections were not visible anymore because of data inconsistency on our side. We have reverted the culprit contribution to take the time to investigate more on it. https://status.forestadmin.com/incident/479158 Mon, 16 Dec 2024 16:32:00 -0000 https://status.forestadmin.com/incident/479158#336d18827508c073d0614cdf8b1ec9d0ad7167da0a2de08b206ad838a480cd59 Some collections are not showing anymore in the navigation bar on the left https://status.forestadmin.com/incident/472926 Tue, 03 Dec 2024 12:53:00 -0000 https://status.forestadmin.com/incident/472926#16887a4dfa4e9d0ed5f4c3c0eed31f375d920b29465ed6a2d61fe181b86227de The issue is now solved, you will need to refresh your page to fix it. This regression was introduced while doing a technical migration of our app framework. We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience. https://status.forestadmin.com/incident/472926 Tue, 03 Dec 2024 11:36:00 -0000 https://status.forestadmin.com/incident/472926#e62832d601071b92ef12c6d8c883caf5ee1d944ec100583f6f1e4fcbc3d92130 We’re currently investigating the issue and will keep you updated once we got more information. https://status.forestadmin.com/incident/472926 Tue, 03 Dec 2024 10:23:00 -0000 https://status.forestadmin.com/incident/472926#99822b55c707a8bfbd07b4e13bd40d5348980a2e71c5720136ee59488d67243b Our app is currently experiencing an issue where "belongs to" data is unexpectedly displayed as a record alongside the actual records in the Related Data views https://status.forestadmin.com/incident/469139 Thu, 28 Nov 2024 17:04:00 -0000 https://status.forestadmin.com/incident/469139#c74b3e0eba116b373ac46421dc33f76b4bd39e1227c0a72f36fea8cf65a7d0ad This morning, our Technical Team triggered a release containing a database migration to prepare a new important feature. This migration aimed to update our main database. The migration locked the main database to execute schema and data transformation. For the entire time the migration was running, a transaction lock prevented users from accessing our main database, via API calls, for their own needs. All requests ended up in error. This migration used a new utility function that was introduced last week to prevent migrations from running more than once (in very rare concurrent cases) but its usage requires further work. Our Technical Team is currently working on aligning migration practices and documentation for this new utility function. This will prevent similar events in the future. Thank you for your patience during this incident. https://status.forestadmin.com/incident/469139 Thu, 28 Nov 2024 17:04:00 -0000 https://status.forestadmin.com/incident/469139#c74b3e0eba116b373ac46421dc33f76b4bd39e1227c0a72f36fea8cf65a7d0ad This morning, our Technical Team triggered a release containing a database migration to prepare a new important feature. This migration aimed to update our main database. The migration locked the main database to execute schema and data transformation. For the entire time the migration was running, a transaction lock prevented users from accessing our main database, via API calls, for their own needs. All requests ended up in error. This migration used a new utility function that was introduced last week to prevent migrations from running more than once (in very rare concurrent cases) but its usage requires further work. Our Technical Team is currently working on aligning migration practices and documentation for this new utility function. This will prevent similar events in the future. Thank you for your patience during this incident. https://status.forestadmin.com/incident/469139 Thu, 28 Nov 2024 09:16:00 -0000 https://status.forestadmin.com/incident/469139#cdb321e9630e5a0d09da4a85357fe57e0ed10ae3c6ae16a19ef5e86358dfe6aa The locks are decreasing and the service is now available. We will continue to investigate why this specific technical migration degraded our service. https://status.forestadmin.com/incident/469139 Thu, 28 Nov 2024 09:16:00 -0000 https://status.forestadmin.com/incident/469139#cdb321e9630e5a0d09da4a85357fe57e0ed10ae3c6ae16a19ef5e86358dfe6aa The locks are decreasing and the service is now available. We will continue to investigate why this specific technical migration degraded our service. https://status.forestadmin.com/incident/469139 Thu, 28 Nov 2024 09:12:00 -0000 https://status.forestadmin.com/incident/469139#15ef2a5b91e3461a06b417bdf02f7ad527e8438bb120bd134bd181cc9c293284 The migration should be finalized soon. Our team is investigating why such generic migration led to the current situation. https://status.forestadmin.com/incident/469139 Thu, 28 Nov 2024 09:12:00 -0000 https://status.forestadmin.com/incident/469139#15ef2a5b91e3461a06b417bdf02f7ad527e8438bb120bd134bd181cc9c293284 The migration should be finalized soon. Our team is investigating why such generic migration led to the current situation. https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 19:39:00 -0000 https://status.forestadmin.com/incident/452094#c333dc1b158418c762798698cd57e0c105e1b7128b53053c9a40c6cd32dde5af Our hosting provider just acknowledged their incident: https://status.heroku.com/incidents/2721 They confirmed that this new issue was once again affecting the EU area. https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 19:39:00 -0000 https://status.forestadmin.com/incident/452094#c333dc1b158418c762798698cd57e0c105e1b7128b53053c9a40c6cd32dde5af Our hosting provider just acknowledged their incident: https://status.heroku.com/incidents/2721 They confirmed that this new issue was once again affecting the EU area. https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 19:31:00 -0000 https://status.forestadmin.com/incident/452094#2e413ea74fb46beb666bb0b7809d20bc1004cf93e6878d5a7255376c8da567df We switched again our platform to the US area. The service is apparently up again. https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 19:31:00 -0000 https://status.forestadmin.com/incident/452094#2e413ea74fb46beb666bb0b7809d20bc1004cf93e6878d5a7255376c8da567df We switched again our platform to the US area. The service is apparently up again. https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 19:14:00 -0000 https://status.forestadmin.com/incident/452094#4fb9d734432ec1ed942495f139d92a6299cc62f03a3e37e77a7524fe06b769f9 We suspect that our hosting provider is currently facing new routing issues. Other customers report similar issues right now on X: https://x.com/search?q=heroku&src=typed_query https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 19:14:00 -0000 https://status.forestadmin.com/incident/452094#4fb9d734432ec1ed942495f139d92a6299cc62f03a3e37e77a7524fe06b769f9 We suspect that our hosting provider is currently facing new routing issues. Other customers report similar issues right now on X: https://x.com/search?q=heroku&src=typed_query https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 18:49:00 -0000 https://status.forestadmin.com/incident/452094#e3c7b20326267d0850dfe0df82e0f0113e1d889cb216300e5d47a89295cb49e1 The Technical team observes a high level of 4XX responses. We are currently investigating. https://status.forestadmin.com/incident/452094 Mon, 28 Oct 2024 18:49:00 -0000 https://status.forestadmin.com/incident/452094#e3c7b20326267d0850dfe0df82e0f0113e1d889cb216300e5d47a89295cb49e1 The Technical team observes a high level of 4XX responses. We are currently investigating. https://status.forestadmin.com/incident/443739 Sun, 13 Oct 2024 08:01:00 -0000 https://status.forestadmin.com/incident/443739#f661194981a70f161abf51aaa8e8a26c1d2205fdf6d16d520e006747d7eb2e43 Our "Authentication API" monitor automatically moved back to the "up" status. The incident is now closed. https://status.forestadmin.com/incident/443739 Sun, 13 Oct 2024 07:58:00 -0000 https://status.forestadmin.com/incident/443739#fcfcfe796a837df751ea07f4e82954518e5e7b9ae3d5d0c99f1a97b2fac29a3b The switch to the EU area has been done. We can now log in to the platform on our end. The new DNS record needs to propagate. Its Time To Live is 5 minutes, so it should be up for everybody in 5 minutes maximum. https://status.forestadmin.com/incident/443739 Sun, 13 Oct 2024 07:44:00 -0000 https://status.forestadmin.com/incident/443739#41b5a01ffe2d1c8672159bed4a4736a4fe7715e31a9d82d3e27799dc02e640ac As explained in the previous report update, due to a planned automatic maintenance on a specific database early this morning, the US area platform is probably pointing to a wrong database. The technical team is switching back the Forest Admin platform to the EU area to attempt to resolve the issue. https://status.forestadmin.com/incident/443739 Sun, 13 Oct 2024 07:24:00 -0000 https://status.forestadmin.com/incident/443739#38a0db1d9dd500e919a49e2c70227503b235d99c6932775c3825d9153fef3fec Our technical team acknowledged the incident and started the investigations. The US area platform has been deployed temporarily after the incidents of the previous week, in order to bypass EU area issues. Some automatic maintenance processes (usually on Sunday mornings) might be the reason of the current incident https://status.forestadmin.com/incident/443739 Sun, 13 Oct 2024 03:03:00 -0000 https://status.forestadmin.com/incident/443739#99f63d9b11351b60ca96c1aa59c4180f8a310f89abc164fc719ff7bbfed97976 A configuration change on our new temporary US area platform probably led to this situation. https://status.forestadmin.com/incident/441819 Thu, 10 Oct 2024 15:20:00 -0000 https://status.forestadmin.com/incident/441819#e7d7f9d26e5653675da54fba82810ee95ba364ccef2ed5e01f05d6b806f6daa7 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441819 Thu, 10 Oct 2024 15:20:00 -0000 https://status.forestadmin.com/incident/441819#e7d7f9d26e5653675da54fba82810ee95ba364ccef2ed5e01f05d6b806f6daa7 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441819 Thu, 10 Oct 2024 15:20:00 -0000 https://status.forestadmin.com/incident/441819#e7d7f9d26e5653675da54fba82810ee95ba364ccef2ed5e01f05d6b806f6daa7 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441819 Thu, 10 Oct 2024 15:20:00 -0000 https://status.forestadmin.com/incident/441819#e7d7f9d26e5653675da54fba82810ee95ba364ccef2ed5e01f05d6b806f6daa7 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441344 Thu, 10 Oct 2024 15:11:00 -0000 https://status.forestadmin.com/incident/441344#ecace5731224a9e1d3efbc96de1333eae869d91ade3eba2ce89403d232b41d96 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441344 Thu, 10 Oct 2024 15:11:00 -0000 https://status.forestadmin.com/incident/441344#ecace5731224a9e1d3efbc96de1333eae869d91ade3eba2ce89403d232b41d96 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441344 Thu, 10 Oct 2024 15:11:00 -0000 https://status.forestadmin.com/incident/441344#ecace5731224a9e1d3efbc96de1333eae869d91ade3eba2ce89403d232b41d96 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441344 Thu, 10 Oct 2024 15:11:00 -0000 https://status.forestadmin.com/incident/441344#ecace5731224a9e1d3efbc96de1333eae869d91ade3eba2ce89403d232b41d96 Please read our official communication to the community about the recent incidents: https://community.forestadmin.com/t/october-2024-forest-admin-important-downtime-on-october-8-9/7529 https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 21:55:00 -0000 https://status.forestadmin.com/incident/441819#05289b64ecfa97d4711c38d4c10e161926eeff00d349e375aba934fce43f7931 Custom domains are now accessible again. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 21:55:00 -0000 https://status.forestadmin.com/incident/441819#05289b64ecfa97d4711c38d4c10e161926eeff00d349e375aba934fce43f7931 Custom domains are now accessible again. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 21:55:00 -0000 https://status.forestadmin.com/incident/441819#05289b64ecfa97d4711c38d4c10e161926eeff00d349e375aba934fce43f7931 Custom domains are now accessible again. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 21:55:00 -0000 https://status.forestadmin.com/incident/441819#05289b64ecfa97d4711c38d4c10e161926eeff00d349e375aba934fce43f7931 Custom domains are now accessible again. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 17:09:00 -0000 https://status.forestadmin.com/incident/441819#ad069bbecb9d2fe4ae23f8b1dc597bbf18ff80140dac04cd392289f17e5e8f08 New infrastructure DNS records are now fully propagated. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 17:09:00 -0000 https://status.forestadmin.com/incident/441819#ad069bbecb9d2fe4ae23f8b1dc597bbf18ff80140dac04cd392289f17e5e8f08 New infrastructure DNS records are now fully propagated. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 17:09:00 -0000 https://status.forestadmin.com/incident/441819#ad069bbecb9d2fe4ae23f8b1dc597bbf18ff80140dac04cd392289f17e5e8f08 New infrastructure DNS records are now fully propagated. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 17:09:00 -0000 https://status.forestadmin.com/incident/441819#ad069bbecb9d2fe4ae23f8b1dc597bbf18ff80140dac04cd392289f17e5e8f08 New infrastructure DNS records are now fully propagated. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 15:44:00 -0000 https://status.forestadmin.com/incident/441819#db6d665243146dcead945361a408e1d6abc495f1232ec1d12b43e174be8432cb DNS records propagation started at ~4:09pm UTC+2 with a Time To Live (TTL) of 3 hours. So we hope to have everything back for every user at ~7:09pm UTC+2 maximum. Thanks for your patience. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 15:44:00 -0000 https://status.forestadmin.com/incident/441819#db6d665243146dcead945361a408e1d6abc495f1232ec1d12b43e174be8432cb DNS records propagation started at ~4:09pm UTC+2 with a Time To Live (TTL) of 3 hours. So we hope to have everything back for every user at ~7:09pm UTC+2 maximum. Thanks for your patience. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 15:44:00 -0000 https://status.forestadmin.com/incident/441819#db6d665243146dcead945361a408e1d6abc495f1232ec1d12b43e174be8432cb DNS records propagation started at ~4:09pm UTC+2 with a Time To Live (TTL) of 3 hours. So we hope to have everything back for every user at ~7:09pm UTC+2 maximum. Thanks for your patience. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 15:44:00 -0000 https://status.forestadmin.com/incident/441819#db6d665243146dcead945361a408e1d6abc495f1232ec1d12b43e174be8432cb DNS records propagation started at ~4:09pm UTC+2 with a Time To Live (TTL) of 3 hours. So we hope to have everything back for every user at ~7:09pm UTC+2 maximum. Thanks for your patience. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:21:00 -0000 https://status.forestadmin.com/incident/441819#22dbf1f7d4cefd075af6c932d0af40aff33ad1ac9bb81e7d3a2bd48fb0fb8405 The new infrastructure is up. DNS records are still propagating. So far: - Custom domains do not work, so please use app.forestadmin.com to access the service. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:21:00 -0000 https://status.forestadmin.com/incident/441819#22dbf1f7d4cefd075af6c932d0af40aff33ad1ac9bb81e7d3a2bd48fb0fb8405 The new infrastructure is up. DNS records are still propagating. So far: - Custom domains do not work, so please use app.forestadmin.com to access the service. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:21:00 -0000 https://status.forestadmin.com/incident/441819#22dbf1f7d4cefd075af6c932d0af40aff33ad1ac9bb81e7d3a2bd48fb0fb8405 The new infrastructure is up. DNS records are still propagating. So far: - Custom domains do not work, so please use app.forestadmin.com to access the service. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:21:00 -0000 https://status.forestadmin.com/incident/441819#22dbf1f7d4cefd075af6c932d0af40aff33ad1ac9bb81e7d3a2bd48fb0fb8405 The new infrastructure is up. DNS records are still propagating. So far: - Custom domains do not work, so please use app.forestadmin.com to access the service. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:09:00 -0000 https://status.forestadmin.com/incident/441819#35a977d62fcf120cee3988bc821c5f219c0c033e48fc73eaec278994caf4f136 We have moved our infra to the Heroku US area. We are waiting for the DNS to propagate (TTL is quite long). https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:09:00 -0000 https://status.forestadmin.com/incident/441819#35a977d62fcf120cee3988bc821c5f219c0c033e48fc73eaec278994caf4f136 We have moved our infra to the Heroku US area. We are waiting for the DNS to propagate (TTL is quite long). https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:09:00 -0000 https://status.forestadmin.com/incident/441819#35a977d62fcf120cee3988bc821c5f219c0c033e48fc73eaec278994caf4f136 We have moved our infra to the Heroku US area. We are waiting for the DNS to propagate (TTL is quite long). https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 14:09:00 -0000 https://status.forestadmin.com/incident/441819#35a977d62fcf120cee3988bc821c5f219c0c033e48fc73eaec278994caf4f136 We have moved our infra to the Heroku US area. We are waiting for the DNS to propagate (TTL is quite long). https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:52:00 -0000 https://status.forestadmin.com/incident/441819#34a8976d2c2a98d9497092d7e4ad752471c02395fafbe432dfef4358eaafc165 Heroku acknowledged the incident: https://status.heroku.com/incidents/2685 https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:52:00 -0000 https://status.forestadmin.com/incident/441819#34a8976d2c2a98d9497092d7e4ad752471c02395fafbe432dfef4358eaafc165 Heroku acknowledged the incident: https://status.heroku.com/incidents/2685 https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:52:00 -0000 https://status.forestadmin.com/incident/441819#34a8976d2c2a98d9497092d7e4ad752471c02395fafbe432dfef4358eaafc165 Heroku acknowledged the incident: https://status.heroku.com/incidents/2685 https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:52:00 -0000 https://status.forestadmin.com/incident/441819#34a8976d2c2a98d9497092d7e4ad752471c02395fafbe432dfef4358eaafc165 Heroku acknowledged the incident: https://status.heroku.com/incidents/2685 https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:16:00 -0000 https://status.forestadmin.com/incident/441819#c7d0cb0e39a6ea52c2c55a4533db4a2feafb495b7bfa515be18bbaafbaafda56 Our team is trying to deploy the infrastructure in another geographic area to bypass Heroku EU area downtimes. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:16:00 -0000 https://status.forestadmin.com/incident/441819#c7d0cb0e39a6ea52c2c55a4533db4a2feafb495b7bfa515be18bbaafbaafda56 Our team is trying to deploy the infrastructure in another geographic area to bypass Heroku EU area downtimes. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:16:00 -0000 https://status.forestadmin.com/incident/441819#c7d0cb0e39a6ea52c2c55a4533db4a2feafb495b7bfa515be18bbaafbaafda56 Our team is trying to deploy the infrastructure in another geographic area to bypass Heroku EU area downtimes. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:16:00 -0000 https://status.forestadmin.com/incident/441819#c7d0cb0e39a6ea52c2c55a4533db4a2feafb495b7bfa515be18bbaafbaafda56 Our team is trying to deploy the infrastructure in another geographic area to bypass Heroku EU area downtimes. https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:00:00 -0000 https://status.forestadmin.com/incident/441819#42e6dc022e85ef524eab2270494205ae1094731dbe486fc201c7001a35c2ef44 Very likely a replica of the hosting provider issue we observed yesterday. Similar incidents described here: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:00:00 -0000 https://status.forestadmin.com/incident/441819#42e6dc022e85ef524eab2270494205ae1094731dbe486fc201c7001a35c2ef44 Very likely a replica of the hosting provider issue we observed yesterday. Similar incidents described here: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:00:00 -0000 https://status.forestadmin.com/incident/441819#42e6dc022e85ef524eab2270494205ae1094731dbe486fc201c7001a35c2ef44 Very likely a replica of the hosting provider issue we observed yesterday. Similar incidents described here: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441819 Wed, 09 Oct 2024 13:00:00 -0000 https://status.forestadmin.com/incident/441819#42e6dc022e85ef524eab2270494205ae1094731dbe486fc201c7001a35c2ef44 Very likely a replica of the hosting provider issue we observed yesterday. Similar incidents described here: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 21:57:00 -0000 https://status.forestadmin.com/incident/441344#e32c24503ececcda22f443fda640aa148d3d46b6a7f1ffd0569ed17061eaa6a0 All services are back up now. We will request clear explanation of what happened to our hosting provider and design solutions for emergency setups if such similar situation occurs in the future. Thanks for you patience in such difficult moments. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 21:57:00 -0000 https://status.forestadmin.com/incident/441344#e32c24503ececcda22f443fda640aa148d3d46b6a7f1ffd0569ed17061eaa6a0 All services are back up now. We will request clear explanation of what happened to our hosting provider and design solutions for emergency setups if such similar situation occurs in the future. Thanks for you patience in such difficult moments. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 21:57:00 -0000 https://status.forestadmin.com/incident/441344#e32c24503ececcda22f443fda640aa148d3d46b6a7f1ffd0569ed17061eaa6a0 All services are back up now. We will request clear explanation of what happened to our hosting provider and design solutions for emergency setups if such similar situation occurs in the future. Thanks for you patience in such difficult moments. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 21:57:00 -0000 https://status.forestadmin.com/incident/441344#e32c24503ececcda22f443fda640aa148d3d46b6a7f1ffd0569ed17061eaa6a0 All services are back up now. We will request clear explanation of what happened to our hosting provider and design solutions for emergency setups if such similar situation occurs in the future. Thanks for you patience in such difficult moments. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 18:13:00 -0000 https://status.forestadmin.com/incident/441344#ba51f226a54aa568438867d05c4a2225c2746917dd6cb12a2c0bd225311b5dbf Heroku just acknowledged the issue on their end, you can follow the evolution directly following this link: https://status.heroku.com/incidents/2684 https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 18:13:00 -0000 https://status.forestadmin.com/incident/441344#ba51f226a54aa568438867d05c4a2225c2746917dd6cb12a2c0bd225311b5dbf Heroku just acknowledged the issue on their end, you can follow the evolution directly following this link: https://status.heroku.com/incidents/2684 https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 18:13:00 -0000 https://status.forestadmin.com/incident/441344#ba51f226a54aa568438867d05c4a2225c2746917dd6cb12a2c0bd225311b5dbf Heroku just acknowledged the issue on their end, you can follow the evolution directly following this link: https://status.heroku.com/incidents/2684 https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 18:13:00 -0000 https://status.forestadmin.com/incident/441344#ba51f226a54aa568438867d05c4a2225c2746917dd6cb12a2c0bd225311b5dbf Heroku just acknowledged the issue on their end, you can follow the evolution directly following this link: https://status.heroku.com/incidents/2684 https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 17:37:00 -0000 https://status.forestadmin.com/incident/441344#c0cef93d4a3d79e1ea7f63cbb327841bc9b1cbb065b326cad973be8b57f297f9 Similar apps using the same hosting platform observe the same downs. Users of our hosting platform report similar issues on X: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 17:37:00 -0000 https://status.forestadmin.com/incident/441344#c0cef93d4a3d79e1ea7f63cbb327841bc9b1cbb065b326cad973be8b57f297f9 Similar apps using the same hosting platform observe the same downs. Users of our hosting platform report similar issues on X: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 17:37:00 -0000 https://status.forestadmin.com/incident/441344#c0cef93d4a3d79e1ea7f63cbb327841bc9b1cbb065b326cad973be8b57f297f9 Similar apps using the same hosting platform observe the same downs. Users of our hosting platform report similar issues on X: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 17:37:00 -0000 https://status.forestadmin.com/incident/441344#c0cef93d4a3d79e1ea7f63cbb327841bc9b1cbb065b326cad973be8b57f297f9 Similar apps using the same hosting platform observe the same downs. Users of our hosting platform report similar issues on X: https://x.com/search?q=heroku&src=typed_query We are waiting for Heroku to acknowledge the issue: https://status.heroku.com https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 16:29:00 -0000 https://status.forestadmin.com/incident/441344#f15674d8e8c3631cc9c604f4fef7df640f1f9572e3b026af7f4850bcb93be557 Our team is investigating, we suspect our hosting platform to be the culprit. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 16:29:00 -0000 https://status.forestadmin.com/incident/441344#f15674d8e8c3631cc9c604f4fef7df640f1f9572e3b026af7f4850bcb93be557 Our team is investigating, we suspect our hosting platform to be the culprit. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 16:29:00 -0000 https://status.forestadmin.com/incident/441344#f15674d8e8c3631cc9c604f4fef7df640f1f9572e3b026af7f4850bcb93be557 Our team is investigating, we suspect our hosting platform to be the culprit. https://status.forestadmin.com/incident/441344 Tue, 08 Oct 2024 16:29:00 -0000 https://status.forestadmin.com/incident/441344#f15674d8e8c3631cc9c604f4fef7df640f1f9572e3b026af7f4850bcb93be557 Our team is investigating, we suspect our hosting platform to be the culprit. https://status.forestadmin.com/incident/435179 Thu, 26 Sep 2024 08:30:00 -0000 https://status.forestadmin.com/incident/435179#fc5640027308ae2c3ed3357826c73a18fceeb1bcd45727710ac085eaad29bc00 The impacted projects should now be able to use the impacted Smart Views and Smart Chart as before the incident. This regression has been introduced while working on improving the overall Smart View and Smart Chart edition experience. Editors must now opt-in the JavaScript activation, understanding the consequences in terms of security. This improvement is now entirely live and does not impact any existing Smart View and Smart Chart anymore. Thanks for your patience. https://status.forestadmin.com/incident/435179 Wed, 25 Sep 2024 13:51:00 -0000 https://status.forestadmin.com/incident/435179#12d02a395e0b824e8b35d99b8a96f1bffe5d7089aab57690ceb6d8423d620f8d Smart Views on collections without Analytics per record charts on any environment type, Smart Charts in Analytics per record section on non-production environments, are not usable anymore. Custom JavaScript is not executed on these Views and Charts. https://status.forestadmin.com/incident/370464 Thu, 16 May 2024 16:09:00 -0000 https://status.forestadmin.com/incident/370464#d9416e063dd6e0cad994d72b0e90f9e12f827934c8513d77cf1bf4480ee34b88 The team quickly investigated to understand the reasons of these errors. We have rollbacked a recent contribution that led to the current situation. All API services are now up and running. https://status.forestadmin.com/incident/370464 Thu, 16 May 2024 16:09:00 -0000 https://status.forestadmin.com/incident/370464#d9416e063dd6e0cad994d72b0e90f9e12f827934c8513d77cf1bf4480ee34b88 The team quickly investigated to understand the reasons of these errors. We have rollbacked a recent contribution that led to the current situation. All API services are now up and running. https://status.forestadmin.com/incident/370464 Thu, 16 May 2024 15:58:00 -0000 https://status.forestadmin.com/incident/370464#d2af8f1dd317b769a8b5d054a2bfd7f173a90a13e28db601f3bf86b3fcb34f85 All API endpoints respond with the 500 status code. https://status.forestadmin.com/incident/370464 Thu, 16 May 2024 15:58:00 -0000 https://status.forestadmin.com/incident/370464#d2af8f1dd317b769a8b5d054a2bfd7f173a90a13e28db601f3bf86b3fcb34f85 All API endpoints respond with the 500 status code. https://status.forestadmin.com/incident/357257 Thu, 18 Apr 2024 14:16:00 -0000 https://status.forestadmin.com/incident/357257#805ccf921ce644951f461a9e60d65721d428e73971348cf60b76b0a1c368cf8c All the missing activity logs have been re-introduced. This is the final update for this incident. https://status.forestadmin.com/incident/357257 Thu, 18 Apr 2024 13:25:00 -0000 https://status.forestadmin.com/incident/357257#153afcb60ca5b2cf281de23a3cf145d43352b79ce80be75bca08698eadcc1449 The service is now fully functional again. The team will re-introduce the missing activity logs via a dedicated migration, by the end of the week. https://status.forestadmin.com/incident/356671 Wed, 17 Apr 2024 12:14:00 -0000 https://status.forestadmin.com/incident/356671#2225b4ed1b206c49c5d4cc782d4a97f2c932b137afc85181a2284c3fa501a2eb The patch has been released and the service is now restored. https://status.forestadmin.com/incident/357257 Mon, 15 Apr 2024 09:22:00 -0000 https://status.forestadmin.com/incident/357257#aaa3a2dc374607f87e515ee47eff0d1f6c93e215c5ced0a2a6f57b8bce603f5b The team is currently investigating on this regression. https://status.forestadmin.com/incident/356671 Tue, 09 Apr 2024 10:00:00 -0000 https://status.forestadmin.com/incident/356671#803e033c3a23983d670e57651db413255a4c27c8e51387c4f2998db961595dcd An error is raised: "✖ Bootstrap failed: Please install sqlite3 package manually." The contribution that introduced the regression is identified, the team is currently looking for a way to patch it and resume the customization feature on Cloud projects. https://status.forestadmin.com/incident/324019 Thu, 08 Feb 2024 09:00:00 -0000 https://status.forestadmin.com/incident/324019#bc1011d2130e69a786893802c1ef3bfa514fdf26768414b96281676512c5e513 The regression introduced yesterday has been identified and rollbacked. Please make sure to refresh your browser to ensure the service resumes. https://status.forestadmin.com/incident/324019 Wed, 07 Feb 2024 16:06:00 -0000 https://status.forestadmin.com/incident/324019#0cd0416f781a15a547642bcc374abb74b5225eebab8aefef45af2c7bd386f2fe Summary View usage and layout edition break when having configurations including Smart Actions that have disappeared in the project lifecycle. https://status.forestadmin.com/incident/320935 Thu, 01 Feb 2024 15:30:00 -0000 https://status.forestadmin.com/incident/320935#db2a8791b700a77b2f00e29adb1525a7d065b082185762ff2a12ba3686613ff3 All services is now up. The team rollbacked a recent contribution that led to theses unexpected errors. https://status.forestadmin.com/incident/320935 Thu, 01 Feb 2024 14:31:00 -0000 https://status.forestadmin.com/incident/320935#7c4ffeb20f25c90f3ec5e044a5e820f136294794c654a60b6e2a40fa8955768e Various services returned unexpected errors: - login with Google, - user creation / update / project dissociation, - project creation / update, - invitation creation, - schema update, - permissions export. https://status.forestadmin.com/incident/311769 Fri, 12 Jan 2024 10:41:00 -0000 https://status.forestadmin.com/incident/311769#4499b823147de901a630c8d9b9b61224ac72c863513a59b2dd79a7e2968e67e4 The traffic is now back on the gateway. https://status.forestadmin.com/incident/311769 Thu, 11 Jan 2024 23:00:00 -0000 https://status.forestadmin.com/incident/311769#4f04d8847abd9eb832dcdc3540e16cfbd7fd2c050acaf6533f65bf5ce6fbee36 The Forest Admin gateway domain has not been renewed automatically last night. It’s been renewed manually once the incident discovered. We are waiting for the domain propagation to resume the Cloud services. https://status.forestadmin.com/incident/265394 Thu, 28 Sep 2023 05:53:00 -0000 https://status.forestadmin.com/incident/265394#bd43140e236302706f92cffd40f1881971f3f1db0388ef0ef2336b956c6edaa8 Custom domains are now restored and can be used as expected. https://status.forestadmin.com/incident/265394 Wed, 27 Sep 2023 19:38:00 -0000 https://status.forestadmin.com/incident/265394#fb1b2a89effb922f854a20ac2bf4ff1bdf420c63a843240fda9b9a1348fbeb8f Due to the previous incident, in order to restore the service on https://app.forestadmin.com, projects configured with a custom domain cannot use this domain to access their admin panel. The team aims to restore this feature today. In the meantime, please use https://app.forestadmin.com. https://status.forestadmin.com/incident/265171 Wed, 27 Sep 2023 19:38:00 -0000 https://status.forestadmin.com/incident/265171#4a54ae7f2bfb37140335affff7ac2112a298c78ca1ae1fa43a927cb208749539 We moved our frontend servers on another region of our hosting provider. So https://app.forestadmin.com should now be accessible. Custom domains remain down so far, so please use https://app.forestadmin.com. https://status.forestadmin.com/incident/265171 Wed, 27 Sep 2023 17:38:00 -0000 https://status.forestadmin.com/incident/265171#f01e4dae7b127b0d2f3fe3c9f51b5d8b7cdb505374897c80d8b5e7c21cc7c5ed More information on our hosting provider status page incident: https://status.heroku.com/incidents/2590 In the meantime, please use https://future.forestadmin.com. https://status.forestadmin.com/incident/247468 Fri, 18 Aug 2023 09:39:00 -0000 https://status.forestadmin.com/incident/247468#3dbf744b2c4ce341b664d65f4a0e90b80026041086aa4e6a57a525d2e57e3224 A recent contribution introduced this issue. We monitored 40 layouts experiencing such errors. We’ve automatically restored the layouts in the expected state. https://status.forestadmin.com/incident/247468 Thu, 17 Aug 2023 10:14:00 -0000 https://status.forestadmin.com/incident/247468#d9072a5babb03f18f600a3c9f2e7b321424f3f9f987b27d71458cfde2c1d9872 A few users raised the alarm. The team investigated on the issue after a few hours delay. https://status.forestadmin.com/incident/245598 Fri, 11 Aug 2023 13:23:00 -0000 https://status.forestadmin.com/incident/245598#589c242086046e55a483beba33bcff3f9ebfba8ad10dc2f64e6fde2327accf7a We’ve rollbacked an important library update. Some misconfigurations led to this situation. https://status.forestadmin.com/incident/245598 Fri, 11 Aug 2023 13:23:00 -0000 https://status.forestadmin.com/incident/245598#589c242086046e55a483beba33bcff3f9ebfba8ad10dc2f64e6fde2327accf7a We’ve rollbacked an important library update. Some misconfigurations led to this situation. https://status.forestadmin.com/incident/245598 Fri, 11 Aug 2023 13:19:00 -0000 https://status.forestadmin.com/incident/245598#6de2cf46e76d70118445e7305a9dabf3978217ba5acc85e847bdc3935b2231e8 Users cannot login. Some asynchronous operations (like layout cache update) fail. https://status.forestadmin.com/incident/245598 Fri, 11 Aug 2023 13:19:00 -0000 https://status.forestadmin.com/incident/245598#6de2cf46e76d70118445e7305a9dabf3978217ba5acc85e847bdc3935b2231e8 Users cannot login. Some asynchronous operations (like layout cache update) fail. https://status.forestadmin.com/incident/229408 Thu, 06 Jul 2023 07:37:00 -0000 https://status.forestadmin.com/incident/229408#ab8c0a2de8d53296fbdb6027c532ba7c3587021e33c7ba96426182394b069c65 We’ve rollbacked our latest contributions and this project returned to a normal situation. This incident is related to the previous one: https://status.forestadmin.com/incident/227805 We will try to make our contribution work in close collaboration to the related projects maintainers. https://status.forestadmin.com/incident/229408 Wed, 05 Jul 2023 15:22:00 -0000 https://status.forestadmin.com/incident/229408#e6487255e136560c6fea0cc0dfef1fff1ad3a2036fe7aceb34ac9be452057802 Business data cannot be accessed by users on a one specific project. https://status.forestadmin.com/incident/227805 Tue, 04 Jul 2023 12:36:00 -0000 https://status.forestadmin.com/incident/227805#e00ffc047c47a83935017bb612d349837ae88aa40fe5864be8f235185e0f0a6e This incident was due to an old library removal that made a specific request header disappear. 2 projects with a restrictive custom Admin API configuration were not able to reach their data due to this change. https://status.forestadmin.com/incident/227805 Sat, 01 Jul 2023 09:57:00 -0000 https://status.forestadmin.com/incident/227805#1339d3e9189c3f31d7e2a17ec5eee7e56e246b049f48c91f9b107216de9227dc We’ve rollbacked our latest contributions and those projects returned to a normal situation. We are now digging into those contributions to isolate the guilty one. https://status.forestadmin.com/incident/227805 Fri, 30 Jun 2023 13:00:00 -0000 https://status.forestadmin.com/incident/227805#60c1cdf28bc9e20f706df79de15680d13f3337915a7e5731343ed880802baeec Business data cannot be accessed by users on a few projects. https://status.forestadmin.com/incident/212326 Fri, 26 May 2023 08:54:00 -0000 https://status.forestadmin.com/incident/212326#88eb56baf71f22577784aa648c1de55a003d7ce87ae5491a20b6c54e7ec8b1b0 All projects are now accessible as expected. We’ve rollbacked a recent contribution that led to this situation for some projects that never received schema update for at least 6 months (to be confirmed with further investigations). https://status.forestadmin.com/incident/212326 Fri, 26 May 2023 08:12:00 -0000 https://status.forestadmin.com/incident/212326#fbd226aad69a9d43703acea9bdedcf4058bd3292e9801f55a055f51c351ae036 Some customers cannot access their projects for unknown reasons so far. We are investigating. https://status.forestadmin.com/incident/210111 Sun, 21 May 2023 08:32:00 -0000 https://status.forestadmin.com/incident/210111#11f1ad8c675376679a81f71e57cf7692c19fe4b3f54a0fb0186a8344b3750097 Database maintenance is now over, the Authentication API is now responding as expected. https://status.forestadmin.com/incident/210111 Sun, 21 May 2023 08:23:00 -0000 https://status.forestadmin.com/incident/210111#10931ae83ee70e30520affeb3f445d023a44ae436b648a8aff002d8ae7e97a90 Due to an unexpected maintenance from our database provider, the authentication API does not allow anyone to log in. https://status.forestadmin.com/incident/207585 Mon, 15 May 2023 07:00:00 -0000 https://status.forestadmin.com/incident/207585#443dfb0488be7e354f6ee8c3bd081f6b97f7fc096563be9f862eca3361521e3c The asynchronous tasks are now working as expected. We reset our queuing system. The team is still looking for the root cause of the issue. https://status.forestadmin.com/incident/207585 Fri, 12 May 2023 22:03:00 -0000 https://status.forestadmin.com/incident/207585#cab7ad08353da143b0c980f51ed1aecf89e5eabdd868cca847f44a5596d16d8d Heavy lifecycle or requested tasks are not executed: - Installation - Layout updates - Schema updates - Copy environment layout - Copy team layout - Create environment - Create team - Export activities - Export permissions - Export approvals - Notify Approval https://status.forestadmin.com/incident/190574 Wed, 29 Mar 2023 13:45:00 -0000 https://status.forestadmin.com/incident/190574#581ee7e39d5afb88f415cf6ead19c9a518949480eac147b17af131627c440a7b Our latest release triggered at 2:50pm (GMT+2) broke the cache access in our layout service making it impossible for users to display their admin panel. Our continuous delivery process did not raise any alert despite our extended automated test base. Our Technical Tech team will found out and implement solutions to prevent further similar incidents in the future. https://status.forestadmin.com/incident/190574 Wed, 29 Mar 2023 13:08:00 -0000 https://status.forestadmin.com/incident/190574#97cfe136df2f176e92ff0145ae95c2288e410811e37f45980b234bf236104782 All customers can now access to their layouts. Our team is still investigating to find out the origin of the issue. https://status.forestadmin.com/incident/190574 Wed, 29 Mar 2023 12:55:00 -0000 https://status.forestadmin.com/incident/190574#22aa3b5b936f91261c95ea248050dba8134f59bb40238628772b5281b17a2e41 All projects have an infinite loading view while requesting an access to a team/layout. https://status.forestadmin.com/incident/175541 Sat, 18 Feb 2023 22:30:00 +0000 https://status.forestadmin.com/incident/175541#e10cac26bb7393310e4f50f74e8e38c644011d29f7e89d693e4c9a4cf0f15187 Maintenance completed https://status.forestadmin.com/incident/175541 Sat, 18 Feb 2023 22:00:00 -0000 https://status.forestadmin.com/incident/175541#1e6d32b69aa75111c2e559079a060983a9eab4a9d728efc21a7687604325b92e The Forest Admin General API will be in maintenance on Saturday, February 18, 2023 from 22:00 to 22:30 UTC. We will proceed a technical upgrade of one of our main databases. https://status.forestadmin.com/incident/170075 Mon, 30 Jan 2023 10:21:00 -0000 https://status.forestadmin.com/incident/170075#ae16bf38bd6c7ddd2604c1c5de7474e9984af3effc41be45911c80b80ddd739a The issue have been fixed on the web app, users must reload their application in order to have the issue fixed on their side. Approval ids that have failed to be correctly saved have been marked as executed with the following message: ``` Due to a technical regression on January 27-30, 2023, Forest Admin cannot tell if this action was accepted or rejected by the approver. As a security measure, it has been set to approved even if your operator actually rejected it. Please contact us to correct this status if necessary. ``` https://status.forestadmin.com/incident/170075 Fri, 27 Jan 2023 10:54:00 -0000 https://status.forestadmin.com/incident/170075#e52df428817e49ba93b33b11f8047e47bd6466f3373e76d857e84f21a39546db A regression introduced in the web app prevented the action approval requests to be correctly updated after being executed or rejected. As a consequence, action approval requests that have been approved could have been executed but remain in the list of pending actions. https://status.forestadmin.com/incident/165975 Thu, 19 Jan 2023 09:40:00 -0000 https://status.forestadmin.com/incident/165975#38a71b9fc757099b16fe129691032499878041e6e3a1cfaf3e9e3cab4132e0ca The issue has been identified and solved. A recent contribution has been rollbacked. https://status.forestadmin.com/incident/165975 Thu, 19 Jan 2023 09:22:00 -0000 https://status.forestadmin.com/incident/165975#a2383fb35b04bbb10c17c82b40e313f81c1c27df23ccd9fe1fbbfc7bef4dcedd Users that authenticate using email and password failed to login. https://status.forestadmin.com/incident/151694 Tue, 10 Jan 2023 11:30:00 -0000 https://status.forestadmin.com/incident/151694#800ad1501d745c4260b83cc9893c5d6a1d64c143e3ca1d354f936717584c4f36 This partial outage has been caused by a combination of 2 events: - the first outage episode that occurred during the week, - a maintenance planned by our hosting provider that wrongly reset some services in an unexpected state. We will improve the monitoring on those services, to improve our response time if any new similar third-party issue event occurs in the future. https://status.forestadmin.com/incident/151694 Sun, 08 Jan 2023 18:28:00 -0000 https://status.forestadmin.com/incident/151694#096be5906aeae5adc25e09ae0a8161d4ffca3652caa0921d7f705588fdf64f69 The asynchronous tasks are now working as expected. We increase our queuing capacity. The team is still looking for the root cause of the issue. https://status.forestadmin.com/incident/151694 Sun, 08 Jan 2023 02:06:00 -0000 https://status.forestadmin.com/incident/151694#3883353f6caae30a5f03eec8b354cbb869f8db961b5f9f8a5da94f95381826c8 Heavy lifecycle or requested tasks are not executed: - Installation - Layout updates - Schema updates - Copy environment layout - Copy team layout - Create environment - Create team - Export activities - Export permissions - Export approvals - Notify Approval https://status.forestadmin.com/incident/150315 Tue, 03 Jan 2023 13:26:00 -0000 https://status.forestadmin.com/incident/150315#2f6587c5623307fe4f75ccdce4939e7be2e3e808e1662540fdaf38bd93bd5588 The root cause has been identified and resolved. We reverted a recent contribution to return to a normal situation. https://status.forestadmin.com/incident/150315 Tue, 03 Jan 2023 07:46:00 -0000 https://status.forestadmin.com/incident/150315#c1476f630397ec49efa2866efc36fff31c923444254eacb1dff67f22c9ef85e9 Heavy lifecycle or requested tasks are not executed: - Layout updates, - Schema updates, - Copy environment layout - Copy team layout - Approval creation - Create team - Export activities - Export permissions - Export approvals https://status.forestadmin.com/incident/132480 Thu, 03 Nov 2022 16:52:00 -0000 https://status.forestadmin.com/incident/132480#29ab22115ce9b69a83b2f36434b5ed30ee2072360e0b5727141aee8bc4e7d00c The issue has been identified and fixed. Impacted API services are now responding as expected. https://status.forestadmin.com/incident/132480 Thu, 03 Nov 2022 16:27:00 -0000 https://status.forestadmin.com/incident/132480#5f75969a288d6ebb64ba58e09b430876f1907ebdd15d6dfc51274f5939ba3ea5 Some API services are currently experiencing a higher than normal amount of load, and may be causing pages to be slow or unresponsive. We're investigating the cause and will provide an update as soon as possible. https://status.forestadmin.com/incident/122172 Thu, 29 Sep 2022 20:17:00 -0000 https://status.forestadmin.com/incident/122172#16bcec4be5ebe92947982c77dab03b1718d725218fc79ede518c09e99383042e The activity logs services are now up and running and all the history has been properly restored. Some activities data have been permanently lost during the incident and the data restoration phase: - from 8:59 to 9:21am UTC, - from 12:03pm to 12:05pm UTC, - from 12:15pm to 12:30pm UTC, - from 8:08pm to 8:16pm UTC (total of 47 minutes) https://status.forestadmin.com/incident/122172 Thu, 29 Sep 2022 12:35:00 -0000 https://status.forestadmin.com/incident/122172#2f6084e6b13d170ef5c40ada8c5bae9d93c5251f88d21804b6ebf436a8fc0398 The activity logs index, search and export services are back but some recent history is still missing. https://status.forestadmin.com/incident/122172 Thu, 29 Sep 2022 09:20:00 -0000 https://status.forestadmin.com/incident/122172#85f03fe4fb0cb0b085ac6cef5b70cba339921f440abf1d09f33659f58c97e710 ⚠️ Our activity logs API services are not accessible right now. ⚠️ The origin of this issue is identified, the technical team is working on a solution to restore the services as soon as possible. https://status.forestadmin.com/incident/55494 Thu, 30 Sep 2021 17:37:09 -0000 https://status.forestadmin.com/incident/55494#caf5723ba841891977863f18b05a08044d1a3c9777f4156c419dadf3855bb553 Customers using our Ruby on Rails agent v6+ were still encountering issue while logging in. This was related related to a Ruby dependency called httpclient (issue can be found here - https://github.com/nahi/httpclient/issues/445). Please upgrade to the latest version of the major you are using; v6.6.3 or v7.2.2 to fix the Ruby on Rails agent issue. https://status.forestadmin.com/incident/55494 Thu, 30 Sep 2021 15:42:54 -0000 https://status.forestadmin.com/incident/55494#a61ca7c8053ce970227fe5e08e5d7709925143a2b64c169fa4cc4c621a5687d1 We encountered an issue with our authentication system. It got fixed, but action is now required on your side to ensure continuity. More info can be found here: https://community.forestadmin.com/t/sept-30-trouble-logging-in/3381 We want you to know that we’re working internally to prevent similar issues in the future and are deeply sorry for the inconvenience. https://status.forestadmin.com/incident/55494 Thu, 30 Sep 2021 14:56:47 -0000 https://status.forestadmin.com/incident/55494#f17309f6b35ae0a28b1ef4fff8784b0f64d4b8b04956cb41720c3057eca71d77 This problem affects projects using Node.js agents v7+ and Ruby on Rails agents v6+. To resolve this issue, - Customers not using a static FOREST_CLIENT_ID need to restart their server to log in back to Forest Admin. - Customers using a static FOREST_CLIENT_ID will need to regenerate it on all environments and restart their servers. To generate a new FOREST_CLIENT_ID, run the following command in a terminal: curl -H "Content-Type: application/json" \ -H "Authorization: Bearer FOREST_ENV_SECRET" \ -X POST \ -d '{"token_endpoint_auth_method": "none", "redirect_uris": ["APPLICATION_URL/forest/authentication/callback"]}' \ https://api.forestadmin.com/oidc/reg (Please replace the FOREST_ENV_SECRET and APPLICATION_URL by your own project values) https://status.forestadmin.com/incident/55494 Thu, 30 Sep 2021 14:39:41 -0000 https://status.forestadmin.com/incident/55494#3cfe9936f1880dbf73ffed0bee038687c690abc5399f0b3f9942d53e16c36861 We have identified the root of the issue and are working on a fix. Thank you for your patience! https://status.forestadmin.com/incident/55494 Thu, 30 Sep 2021 14:20:00 -0000 https://status.forestadmin.com/incident/55494#3697cd50dcc16ce2840ebf42a83bee967d1af8976355bf2ab7bcd3c7e1e8b009 We're encountering an issue with our application currently SSL certificate. Some users may be experiencing trouble when logging in to Forest Admin. Our engineering team is working to identify the root cause and fix the issue. We apologize for any inconvenience and we'll keep you updated on the status. https://status.forestadmin.com/incident/54809 Mon, 20 Sep 2021 08:56:15 -0000 https://status.forestadmin.com/incident/54809#aacbf231422dfa045957f04ec6220b69c4c1c0681a20bdfaa115e4fc1c5506af We confirm Heroku (our hosting provider) is at the origin of this incident. More info can be found here: https://status.heroku.com/incidents/2360 https://status.forestadmin.com/incident/54809 Mon, 20 Sep 2021 08:53:31 -0000 https://status.forestadmin.com/incident/54809#9680e49856a22a5899c0ffbeac0c59e2c59e8c08df5f137f5e316faa826b4da4 The service is back to normal! We want you to know that we’re still working internally to find the root of the issue and are deeply sorry for the inconvenience https://status.forestadmin.com/incident/54809 Mon, 20 Sep 2021 08:34:49 -0000 https://status.forestadmin.com/incident/54809#5b7164e6ef21983e49bcaeb740e0e8d1093d2b723d7fd533f9ca280418b12587 We are currently experiencing a service outage. This outage has affected our frontend application. The engineering team is working to identify the root cause and fix the issue. We apologize for any inconvenience and we'll keep you updated on the status. https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 07:20:23 -0000 https://status.forestadmin.com/incident/54661#0e1d52a5c3f576d6fa01431d3bc8649a87256331d66fe9fdda4828bf8fdff896 The issue has been resolved and our service is back to normal. Thank you for your patience! https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 07:20:23 -0000 https://status.forestadmin.com/incident/54661#0e1d52a5c3f576d6fa01431d3bc8649a87256331d66fe9fdda4828bf8fdff896 The issue has been resolved and our service is back to normal. Thank you for your patience! https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 07:20:23 -0000 https://status.forestadmin.com/incident/54661#0e1d52a5c3f576d6fa01431d3bc8649a87256331d66fe9fdda4828bf8fdff896 The issue has been resolved and our service is back to normal. Thank you for your patience! https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 06:44:06 -0000 https://status.forestadmin.com/incident/54661#a4c8b00bdfa0f90aef12537a67dfaa3c72d1146130e5bbfe2269b8cec48f0e55 More info from Heroku can be found here - https://status.heroku.com/incidents/2359 https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 06:44:06 -0000 https://status.forestadmin.com/incident/54661#a4c8b00bdfa0f90aef12537a67dfaa3c72d1146130e5bbfe2269b8cec48f0e55 More info from Heroku can be found here - https://status.heroku.com/incidents/2359 https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 06:44:06 -0000 https://status.forestadmin.com/incident/54661#a4c8b00bdfa0f90aef12537a67dfaa3c72d1146130e5bbfe2269b8cec48f0e55 More info from Heroku can be found here - https://status.heroku.com/incidents/2359 https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 05:40:29 -0000 https://status.forestadmin.com/incident/54661#07221ac6802515675d753849ab0773f441456964291a4a1b542b5e5f185203f5 Our hosting provider (Heroku) is experimenting issues right now - https://status.heroku.com/ - which affects the accessibility of our platform. We apologize for any inconvenience and will post another update as soon as we learn more. https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 05:40:29 -0000 https://status.forestadmin.com/incident/54661#07221ac6802515675d753849ab0773f441456964291a4a1b542b5e5f185203f5 Our hosting provider (Heroku) is experimenting issues right now - https://status.heroku.com/ - which affects the accessibility of our platform. We apologize for any inconvenience and will post another update as soon as we learn more. https://status.forestadmin.com/incident/54661 Fri, 17 Sep 2021 05:40:29 -0000 https://status.forestadmin.com/incident/54661#07221ac6802515675d753849ab0773f441456964291a4a1b542b5e5f185203f5 Our hosting provider (Heroku) is experimenting issues right now - https://status.heroku.com/ - which affects the accessibility of our platform. We apologize for any inconvenience and will post another update as soon as we learn more.