Resolved
These systems are now operating normally. If you experience any problems, please open a ticket with our support team.
Monitoring
Errors continue to trend downward. Some customers have confirmed the issue is resolved, and we suspect it may be for others as well. While new instances are still appearing and recovery is slower than expected, we continue to rely on LaunchDarkly for a permanent fix.
Identified
Our engineering team has identified an issue with an upstream provider, and is actively working on a fix. At this point in time we’ve identified that the issue is with the HCP Terraform frontend landing page and user settings, with other application pages unaffacted, and interactions with the service through APIs (including VCS or Terraform CLI) also unaffected.
Identified
Our engineering team has identified an issue with an upstream provider, and is actively working on a fix. At this point in time we’ve identified that the issue is with the HCP Terraform frontend landing page and user settings, with other application pages unaffacted, and interactions with the service through APIs (including VCS or Terraform CLI) also unaffected. As a work around, users can use the “oranization picker” in the bottom left of the UI or or Cmd/Ctrl-K shortcut to select the organization they wish to interact with and continue using the application as normal.
Identified
Our engineering team has identified an issue with an upstream provider, and is actively working on a fix. At this point in time we’ve identified that the issue is isolated to the HCP Terraform frontend, and interactions with the service through APIs (including VCS or Terraform CLI) are unaffected.
Investigating
We are aware of and investigating reports that HCP Terraform frontend is rendering “LaunchDarklyFlagError”. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.