Amazon RDS runs managed relational databases (PostgreSQL, MySQL, and more). RDS incidents hurt disproportionately because databases sit at the bottom of every request path - a few minutes of connection failures cascade into full application outages upstream.
Intermittent connection failures to a subset of instances
Failovers taking longer than expected on Multi-AZ deployments
Storage or IOPS degradation making queries slow, not failed
Maintenance-window reboots surprising teams that missed the notification
Recent Amazon RDS incidents
Intermittent connection errors for RDS instances in eu-west-1
May 6, 2026 · 1h 30m
A regional proxy fleet issue caused intermittent connection failures for a subset of RDS instances for ~90 minutes.
Check the live status above. If RDS shows Operational but your database is unreachable, look at your instance’s events tab, security groups, and whether a Multi-AZ failover just changed your writer endpoint.
Does Multi-AZ protect me from RDS outages?+
Multi-AZ handles single-AZ failures with automatic failover (typically 60–120 seconds of interruption). It does not protect against region-level control-plane incidents or storage-layer issues affecting both AZs.
What SLA does RDS carry?+
Multi-AZ RDS deployments carry a 99.95% monthly uptime SLA; falling below pays tiered credits from 10% up to 100% of the month’s RDS charges, on claim.
Get alerted when Amazon RDS breaks
Instant email the moment we detect an incident - affected services and regions included.
aws