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
A fix has been implemented and we are monitoring the results.
Last update on
The issue has been identified and a fix is being implemented.
Last update on
After a recent browser update from Microsoft, we identified an issue affecting some Windows devices using Microsoft Edge where webpages may load indefinitely. After investigation, we’ve determined that in certain cases the browser extension is not automatically starting, which prevents traffic from being processed as expected. Our Engineering team has been working on this throughout the day and is actively finalizing a fix. We expect to have an updated extension available soon. Once released, the update will be automatically pushed out, no action will be required on your end. We sincerely apologize for the disruption this may have caused and understand how impactful browser performance issues can be in a school environment. Please know this is our top priority, and we are moving as quickly as possible to resolve it fully. Thank you for your patience and for being a valued customer. We truly appreciate your partnership.
Last update on
Some requests may be incorrectly failing with 401 error codes in our US region.
Last update on
RingCentral Operations teams are working with the underlying carrier to resolve this issue. If you are experiencing this issue, please reach out to customer care. The next update will be in 4 hours or when a significant change in status occurs.
Last update on
Monitors
Amazon Web Services
Instructure
Microsoft Edge Issue - Webpages not Loading Intermittently
A portion of customers in Ontario, Canada may be experiencing inbound call and fax failures due to an underlying carrier issue.
RingCentral
Shakopee Infinite Campus
StatusGator