Siemens - Notice history

This incident has been resolved.

Root cause was the configuration of the file system performance and the sizing of the database server.

We have identified the bottleneck in the infrastructure and are working on a fix.
Until the fix has been deployed, some users still may experience errors.

This incident has been resolved.

We implemented a fix and are currently monitoring the result.

AWS is now working on the root cause.

The issue seems to be limited to AUS Cloudfront nodes. We opened a ticket with AWS and asked for support.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

[03:42 PM PDT] Between 11:49 AM PDT and 3:37 PM PDT, we experienced increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. Our engineering teams were immediately engaged and began investigating. We quickly narrowed down the root cause to be an issue with a subsystem responsible for capacity management for AWS Lambda, which caused errors directly for customers (including through API Gateway) and indirectly through the use of other AWS services. Additionally, customers may have experienced authentication or sign-in errors when using the AWS Management Console, or authenticating through Cognito or IAM STS.

AWS has reported that the issue has been solved. We are continuing to monitor the situation closely.

AWS confirmed issues with Lambda in us-east-1.
As a result a lot of services are affected.

This incident has been resolved.

We identified still some issues and continue monitoring.

The Author is now running on a larger instance with enough headroom for the currently increased demand.

Authoring will be back soon.

We are continuing to monitor the situation.

Author has been restarted, and operations have returned to normal.