What’s happening: AWS is having a major incident centered on us-east-1 that’s causing elevated errors/latency across multiple services. Media and status trackers note DynamoDB issues cascading to many dependent services. Canva and other big apps are affected.
Reuters
+2
The Verge
+2
Your item: “Amazon AWS Application Migration Service Disrupted (1 service)” likely reflects MGN (Application Migration Service) showing degraded status on the Health Dashboard as a single listed service, even though the broader outage involves many components. Official dashboards are updating live.
Health AWS
If you rely on AWS Application Migration Service (MGN) right now
Avoid cutovers / test launches until status is green. Cutovers depend on back-end AWS services (networking/IAM/DynamoDB) that can stall or fail during an incident.
AWS Documentation
Pause non-urgent replications and don’t install new agents until stabilization—agent comms/auth can time out during control-plane issues.
AWS Documentation
Monitor in two places:
AWS Health Dashboard (per-region, per-service updates).
Health AWS
Your own logs/alarms (CloudWatch, third-party monitors) for replication lag or task failures; keep alerts noisy until recovery.
N2W Software
Have a fallback: If you designed cross-region DR, be ready to stage to an alternate region for critical migrations, or temporarily defer change windows. (Today’s impact is concentrated in us-east-1.)
Reuters
Sources tracking today’s outage (Oct 20, 2025)
Reuters live coverage of the AWS outage and affected services.
Reuters
The Verge roundup of what’s down (Fortnite, Alexa, Snapchat, Canva, etc.).
The Verge
Tom’s Guide live blog noting DynamoDB disruption impacting ~20 services.
Tom's Guide
AWS Health Dashboard (official status feed).
Health AWS
Reuters
+2
The Verge
+2
Your item: “Amazon AWS Application Migration Service Disrupted (1 service)” likely reflects MGN (Application Migration Service) showing degraded status on the Health Dashboard as a single listed service, even though the broader outage involves many components. Official dashboards are updating live.
Health AWS
If you rely on AWS Application Migration Service (MGN) right now
Avoid cutovers / test launches until status is green. Cutovers depend on back-end AWS services (networking/IAM/DynamoDB) that can stall or fail during an incident.
AWS Documentation
Pause non-urgent replications and don’t install new agents until stabilization—agent comms/auth can time out during control-plane issues.
AWS Documentation
Monitor in two places:
AWS Health Dashboard (per-region, per-service updates).
Health AWS
Your own logs/alarms (CloudWatch, third-party monitors) for replication lag or task failures; keep alerts noisy until recovery.
N2W Software
Have a fallback: If you designed cross-region DR, be ready to stage to an alternate region for critical migrations, or temporarily defer change windows. (Today’s impact is concentrated in us-east-1.)
Reuters
Sources tracking today’s outage (Oct 20, 2025)
Reuters live coverage of the AWS outage and affected services.
Reuters
The Verge roundup of what’s down (Fortnite, Alexa, Snapchat, Canva, etc.).
The Verge
Tom’s Guide live blog noting DynamoDB disruption impacting ~20 services.
Tom's Guide
AWS Health Dashboard (official status feed).
Health AWS