Update timeline
This incident has been resolved.
We are continuing to monitor for any further issues.
All services have recovered and we will continue to monitor until the upstream service provider, AWS, officially resolves the issues.
We are observing recovery across ZeroKMS key generation/retrievals and workspace management in U.S. East (N. Virginia). As systems return to normal operational status, we will continue to monitor and provide updates.
We are experiencing significant improvements to the ZeroKMS Lambda invocation errors which impact key generation and retrieval, and accessibility of U.S. East Workspace environments in the CipherStash dashboard. We are continuing to monitor the situation.
Workspace environments that are configured in U.S. East (N. Virginia) are unaccessible in the CipherStash Dashboard resulting in Internal Service Errors, due to upstream provider issues at AWS.
We continue to see intermediate request failures to ZeroKMS is the us-east-1 region due to our upstream service provider, AWS. We are actively monitoring this issue.
We continue to see intermediate request failures to ZeroKMS is the us-east-1 region due to our upstream service provider, AWS. We are actively monitoring this issue.
We are currently monitoring this issue. ZeroKMS was unable to service requests in us-east-1 for ~2h during the broader us-east-1 outage earlier today. In the last 30 minutes we have observed the AWS Lambda platform sporadically fail to execute Lambda functions, resulting in HTTP status 500 responses being returned to clients.