Many users search for aws problems today when they notice unexpected behavior, slow deployments, or connectivity gaps in their environments. This article maps the most common issues reported across regions and services today, focusing on what is visible in public status feeds, incident timelines, and operational patterns.
Cloud teams rely on clear signals to triage issues quickly, and a concise overview helps align engineering, support, and leadership on impact. The following sections break down the current landscape into focused topics you can scan and act on.
| Service | Region | Issue Type | Status | Last Update |
|---|---|---|---|---|
| EC2 | us-east-1 | Instance provisioning delays | Investigating | 2024-06-18 14:30 UTC |
| Lambda | eu-west-1 | Increased error rates | Mitigating | 2024-06-18 15:05 UTC |
| RDS | ap-southeast-1 | Minor replica lag | Resolved | 2024-06-18 14:50 UTC |
| S3 | Multiple | Intermittent latency on GET | Monitoring | 2024-06-18 15:10 UTC |
| EKS | ca-central-1 | Control plane connectivity issues | Open | 2024-06-18 15:15 UTC |
Compute Service Disruptions and Scaling Events
Across us-east-1 and eu-west-1, EC2 and ECS users reported delays in instance provisioning and task placement. Auto Scaling groups took longer than usual to launch capacity, and some services experienced uneven distribution across Availability Zones.
Investigations traced part of the delay to underlying host maintenance and network reconfiguration. Most teams saw resolution within the hour as AWS automated recovery actions stabilized the fleet.
Impact on containerized workloads
EKS clusters experienced control plane stalls, causing Kubectl commands to time out. Restarts of node groups and rescheduling of pending pods helped reduce error rates while underlying issues were addressed.
Serverless and Function Errors
Lambda throttling and timeouts
In eu-west-1, a spike in invocations combined with cold starts pushed error rates above normal thresholds. Increased concurrency limits and provisioned concurrency reduced tail latencies for downstream APIs.
Storage and Database Latency
S3 GET latency and RDS replica lag
S3 GET operations in multiple regions showed intermittent latency due to internal network congestion. Engineers balanced traffic across edge caches and retried with exponential backoff.
RDS read replicas in ap-southeast-1 experienced replication lag under heavy write bursts. Failover to a healthy replica and tuning of write-intensive queries restored expected consistency.
Networking and Control Plane Health
EKS control plane connectivity issues in ca-central-1 led to sporadic API server responses. AWS support confirmed routing anomalies that were corrected by re-provisioning managed plane components.
VPC attached endpoints and security group evaluations also faced brief processing delays, impacting microservice calls. Refreshing endpoint policies and simplifying route tables helped stabilize communications.
Recommendations and Key Takeaways
- Monitor service health dashboards and AWS Personal Health Dashboard for region-specific alerts.
- Enable proactive retries with jitter and exponential backoff for API calls.
- Use provisioned concurrency for critical Lambda functions during traffic spikes.
- Spread workloads across multiple Availability Zones to absorb localized disruptions.
- Coordinate with AWS Support for persistent control plane or database replication issues.
FAQ
Reader questions
Why are my EC2 instances stuck in pending in us-east-1 today?
EC2 instances are experiencing provisioning delays due to host maintenance and capacity rebalancing in us-east-1. Retrying after a short backoff or selecting a different Availability Zone often resolves the pending state.
Why is Lambda error rate high in eu-west-1 at the moment?
Higher concurrency and cold starts are driving elevated Lambda errors in eu-west-1. Adding provisioned concurrency and optimizing function initialization can reduce error rates until the platform fully scales.
What is causing RDS replica lag in ap-southeast-1 right now?
Replica lag in ap-southeast-1 is linked to write bursts overwhelming the replication pipeline. Reducing heavy write batches, adding read-ahead replicas, and tuning checkpoint intervals help bring lag back to normal.
Why are EKS control plane requests timing out in ca-central-1?
Control plane connectivity issues in ca-central-1 are caused by route anomalies and transient network congestion. AWS is re-provisioning plane components, and short-term workarounds include using alternate endpoints and simplifying VPC configurations.