Amwell

Warn

Amazon Web Services 2

We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams. For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.

Last update on Mar 19, 2026 1:00 PM

Warn

Firebase

**Investigating:** We are aware of a service disruption affecting App Hosting deployments from Firebase Studio. **Impact:** Users are currently unable to publish apps with App Hosting from Firebase Studio. **Action:** Our engineers are currently working to identify the root cause and restore deployment functionality as quickly as possible. We will provide an update as soon as we can. **Workaround:** In the meantime, you can publish using the Firebase App Hosting console or the Firebase CLI. Learn more at https://firebase.google.com/docs/app-hosting/get-started . We have pinpointed the issue and are actively working on a resolution; only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days. Creating and opening Android Studio workspaces is temporarily unavailable

Last update on Mar 19, 2026 1:02 PM

Warn

Fastly

Last update on Mar 19, 2026 1:01 PM

Warn

Twilio

We are observing recovery of SMS delivery receipt delays from a subset of Twilio Short Codes to network subscribers on multiple networks in the United States. Our team is monitoring this issue to ensure it is resolved. We will provide another update in 2 hours or as soon as more information becomes available.

Last update on Mar 19, 2026 1:02 PM