HCP Audit Log Viewer - high latency
Users should be able to see all their audit logs in the HCP Portal.
Users should be able to see all their audit logs in the HCP Portal.
We believe this issue has been resolved, and we'll be discontinuing updates at this time. If you need further help or information, please contact your HashiCorp Support team.
Our Engineering team has fully resolved the issue causing errors for secret writes and increased latency for secret reads in HCP Vault Secrets. The issue was related to the AWS CloudWatch log service degradation which has been resolved as well.
HCP Vault Secrets should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
We have verified that functionality has returned
Our Engineering team has resolved the following issue:
Some user might have experienced issues while deleting SAML configurations.
These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Our Engineering team has resolved the issue where some customers have not been receiving payment receipts. To mitigate this issue in the future, we recommend customers take the following actions:
Check your junk/spam folders. If you find the email there, mark it as "not spam". You can also save HashiCorp's email address, invoice+statements@cloud.hashicorp.com, to your contacts to prevent future occurrences.
Check for third-party filtering. If you use a corporate or business email address, your IT department may be using third-party services that are blocking the message. Your company's IT department or mail provider can confirm this. If so, they may need to specifically allow @cloud.hashicorp.com and @hashicorp.com to prevent future occurrences.
These systems should be operating normally. If you continue to experience any problems, please open a ticket with our support team.
HCP Boundary clusters are operational.
We have verified that the fix we have implemented before has caused recovery of all the impacted clusters. Currently, all the impacted clusters should be back up and healthy.
We have received another update from Azure provider verifying that all the Azure Storage clusters are recovered with their mitigation. On our side, all the impacted clusters are back up and healthy too.
The applied mitigations have successfully resolved the issue.
During the incident customers may have noticed Terraform Runs failing due to the increased latency: those can now be retried.