Resolved -
This incident has been resolved on 01-11-2024 5:00 am UTC 6:08 am
Nov 5, 21:23 UTC
Update -
This incident has now been resolved. All deployments are now successful.
Nov 1, 06:38 UTC
Update -
We are continuing to monitor for any further issues.
Nov 1, 06:25 UTC
Monitoring -
We are monitoring an issue where Forge app deployment failed during 01-11-2024 5:00 am UTC to 6:08 am with an error. If customers have tried to deploy during the time window and failed, re-deployment will fix the issue.
This issue is resolved now and we are monitoring the fix.
Nov 1, 06:18 UTC
Resolved -
At 2024-10-29 10:00 UTC users using the latest Forge CLI v10.8.0 would be facing issues including creating new Forge apps. Developers would receive the error: Error: The "path" argument must be of type string. Received undefined Users who installed the latest version need to downgrade the CLI to version 10.7.0 using npm install -g @forge/cli@10.7.0 for anyone who is on 10.8.0 version currently. You can know the current version you are in by executing the forge --version command The issue was mitigated at 2024-10-30 5:20 UTC where users using the latest Forge CLI ( npm install -g @forge/cli@latest) will automatically point to 10.7.0 The team apologies for inconvenience caused. There will be no further communications for this incident.
Oct 30, 18:30 UTC
Resolved -
This issue is now resolved and performance is back to normal. We recommend any apps deployed between 9:24 UTC on 2024-10-23 05:56 UTC 2024-10-25 to be re-deployed in case the app users identify any latency issues.
Oct 28, 22:41 UTC
Monitoring -
Between 08:59 UTC and 9:24 UTC on 2024-10-23 we have observed increased error rate on app deployments, similar to problem that happened on 2024-10-24.
After investigation we found an condition in one of cells in EU region which was causing deployments to fail.
We applied change to migrate new deployments off the impacted EU cell which mitigated impact.
We are keeping this incident in monitoring state and will resolve it once underlying issue is resolved and deployments are resumed to the affected cell.
From perspective of App developers this means that deployments of apps (new apps and updates to existing ones) will work correctly but may introduce minor performance degradation due to function being invoked from nearest EU cell when customer is located in the affected cell. Because of this we will post an update advising to re-deploy affected apps once this incident is resolved.
Oct 23, 09:53 UTC
Resolved -
Deployments of Forge apps in all EU cells are confirmed to be proceeding normally. We are now setting this issue as resolved.
Timeline 2024-10-22 08:58 UTC: deployments in one EU cell began to fail intermittently 2024-10-22 09:48 UTC: we moved deployments off the impacted cell, which resolved the issue 2024-10-23 00:25 UTC: all EU cells are confirmed to be operating normally
If you deployed apps between 2024-10-22 08:55 UTC to 2024-10-23 00:25 UTC and require them to deploy to the eu-west-1 region, we recommend deploying those apps again.
Oct 23, 03:31 UTC
Monitoring -
Between 08:55 UTC and 9:50 UTC on 2024-10-22 we have observed increased error rate on app deployments.
After investigation we found an condition in one of cells in EU region which was causing deployments to fail.
We applied change to migrate new deployments off the impacted EU cell which mitigated impact - no new errors were since 9:50 UTC.
We are keeping this incident in monitoring state and will resolve it once underlying issue is resolved and deployments are resumed to the affected cell.
From perspective of App developers this means that deployments of apps (new apps and updates to existing ones) will work correctly but may introduce minor performance degradation due to function being invoked from nearest EU cell when customer is located in the affected cell. Because of this we will post an update advising to re-deploy affected apps once this incident is resolved.
Oct 22, 11:20 UTC