Unbabel - Notice history

With the recovery of AWS systems, Unbabel is restoring its capacity. Currently most systems are operational, with some delays still taking place for messages lost in the process and that may need recovering.

AWS Update: Oct 20 12:15 PM PDT We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. For Lambda, customers may face intermittent function errors for functions making network requests to other services or systems as we work to address residual network connectivity issues. To recover Lambda’s invocation errors, we slowed down the rate of SQS polling via Lambda Event Source Mappings. We are now increasing the rate of SQS polling as we experience more successful invocations and reduced function errors. We will provide another update by 1:00 PM PDT.

https://health.aws.amazon.com/health/status

AWS update - "We continue to apply mitigation steps for network load balancer health and recovering connectivity for most AWS services. Lambda is experiencing function invocation errors because an internal subsystem was impacted by the network load balancer health checks. We are taking steps to recover this internal Lambda system. For EC2 launch instance failures, we are in the process of validating a fix and will deploy to the first AZ as soon as we have confidence we can do so safely." - https://health.aws.amazon.com/health/status

Our services are fully recovered. We will keep monitoring for the next few hours.

AWS is recovering and we are seeing significant signs of improvement.

We are being impacted by this AWS incident - https://health.aws.amazon.com/health/status

The team is trying to recover the services as soon as possible.