Our first canaries fired for this at 9:43 PDT local time. The status page updated at 10:13.
AWS us-west-2 issues
11–20 of 107 posts
Re: AWS us-west-2 issues
#12Re: AWS us-west-2 issues
#13Database error: [Amazon](500310) Invalid operation: No response body.
Database error: [Amazon](500310) Invalid operation: curlCode: 28, Timeout was reached
in our logs during the last hour
Re: AWS us-west-2 issues
#14Re: AWS us-west-2 issues
#15Earlier quoted context omitted.
Would be nice if they could update their status dashboard.
It is. It's just currently set at "Informational" severity.
I was just investigating this degradation in service for some of my systems for about 1 hour before seeing this alert raised.
Re: AWS us-west-2 issues
#16Re: AWS us-west-2 issues
#17Re: AWS us-west-2 issues
#18[10:13 AM PDT] [10:10 AM PDT] We are investigating increased error rates for invokes in the US-WEST-2 Region.
AWS AppSync AWS Batch AWS Certificate Manager AWS Cloud9 AWS CloudShell AWS Device Farm AWS Global Accelerator AWS Greengrass AWS IoT 1-Click AWS IoT Device Management AWS Lambda AWS Proton AWS Resource Access Manager AWS RoboMaker AWS Service Catalog Amazon AppStream 2.0 Amazon CloudWatch Amazon Connect Amazon Elastic Compute Cloud Amazon Elastic Container Registry Amazon Elastic MapReduce Amazon EventBridge Amazon FinSpace Amazon Kendra Amazon Lightsail Amazon Location Service Amazon Managed Workflows for Apache Airflow Amazon Nimble Studio Amazon Pinpoint Amazon SageMaker Amazon WorkSpaces EC2 Image Builder
Re: AWS us-west-2 issues
#19I'm seeing multiple services as down: ECS, Medialive, etc.
Re: AWS us-west-2 issues
#20 -----------------------------------------------
error: No response body.
code: 30000
context:
query: 1154965
location: xen_aws_credentials_mgr.cpp:403
process: padbmaster [pid=15893]
-----------------------------------------------