Skip to content

Severe latency and unresponsiveness in me-central-1 (UAE) region

0

Hello,

Since today we are experiencing severe issues in the me-central-1 (UAE) region: • AWS Console becomes extremely slow or even unusable when switching to me-central-1. • ECS/EKS/EC2 cluster lists fail to load with errors like “Deserialization error: network error”. • Deployed services behind ALB/API Gateway take over a minute to respond, sometimes not responding at all. • Even SSH sessions to bastion hosts in me-central-1 show heavy input lag (typing delayed several seconds). • We tested from multiple networks (corporate, home, mobile hotspot) and even from users physically located in UAE, and the issue is the same. • Other regions (ap-northeast-2, us-east-1, etc.) work perfectly fine.

We have checked our VPC routing, security groups, and ECS task health — all seem normal. This appears to be a region-wide latency or control plane issue in me-central-1.

Is anyone else seeing the same problem in me-central-1? Any confirmation from AWS side or workarounds would be appreciated.

Thank you.

2 Answers
0

Based on the symptoms you're describing, it appears you're experiencing significant latency issues specific to the me-central-1 (UAE) region. While I don't have information about a confirmed current outage in me-central-1, there are several potential factors that could be contributing to your experience.

High latency in specific AWS regions can be caused by various factors:

  1. Network connectivity issues between your location and the me-central-1 region
  2. Possible regional infrastructure challenges or maintenance
  3. High resource utilization on AWS services in that region
  4. Network congestion or routing problems

For your specific situation, the fact that the issue is consistent across multiple networks and even for users physically located in UAE suggests this may be related to the AWS infrastructure or network routing in that region rather than a client-side issue.

Some troubleshooting steps you could take:

  1. Monitor the AWS Service Health Dashboard for any announced issues in me-central-1
  2. Open a support case with AWS to report the issue and get region-specific information
  3. Temporarily redirect critical workloads to another region if possible
  4. Use CloudWatch metrics to check if your resources are experiencing unusual CPU, memory, or network utilization
  5. Test network performance using tools that can measure latency to specific AWS endpoints in that region

Since other regions are working normally for you, this appears to be isolated to me-central-1. Without official confirmation from AWS, it's difficult to determine if this is a widespread issue affecting all customers in that region or something specific to your account's resources.
Sources
Troubleshoot latency on calls or requests to Amazon ECS tasks | AWS re:Post
Troubleshoot high response times and ECS latency issues | AWS re:Post

answered a year ago

0

Hello,

Next time you experience degradation on the network performance for your applications, I suggest you to leverage either one of the following AWS services available to troubleshoot such issues:

1. Amazon CloudWatch Internet Monitor

Amazon CloudWatch Internet Monitor is a service that monitors your application's internet performance and availability, providing insights and recommendations to improve end-user experience across the global internet. Uses AWS's internal probes and detection algorithms that monitor connectivity between AWS Regions and the Points of presence (POPs). Tracks application performance and availability from client locations worldwide and provides near real-time suggestions for reducing latency by switching AWS services or regions.

2. Amazon CloudWatch Network Flow Monitor

Amazon CloudWatch Network Flow Monitor is a feature of Amazon CloudWatch Network Monitoring that provides near real-time network performance visibility for TCP traffic within your AWS workloads. Provides near real-time metrics for latency, packet loss, retransmissions, and data transfer for TCP-based traffic. Automatically categorizes and aggregates metrics by subnets, Availability Zones, VPCs, and AWS services. Agents are installed on AWS compute resources (EC2 and EKS) and collect TCP statistics using Linux kernel's "bpf_sock_ops" structure, which includes local and remote IP address and the source and destination TCP port, as well as counters and round-trip times.

Sources:

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-InternetMonitor.html

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-NetworkFlowMonitor.html

Regards

AWS
EXPERT

answered 8 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.