Intermittent missing or delayed EC2 instance and status check metrics - N. Virginia

We can confirm significant signs of recovery, and continuing to monitor to ensure stability. At this time, missing/delayed metrics and instance status checks are recovered. We are actively working to backfill delayed data.

We are seeing early signs of recovery and continue to work toward full resolution. We will continue to provide updates.

We can confirm issues with intermittent missing and/or delayed EC2 instance metrics and status checks in the US-EAST-1 Region. While existing instances are unaffected by this issue and operating normally, metrics and status checks may be delayed or reporting INSUFFICIENT_DATA. We have identified the issue to be in an underlying subsystem responsible for publishing EC2 metric data to CloudWatch. Engineers were automatically engaged, and continue to investigate multiple paths to mitigate the issue in parallel. We recommend customers treat the INSUFFICIENT_DATA state as missing data instead of an alarm breach, especially when configuring the alarm to stop, terminate, reboot, or recover an instance. More information is available here. While we do not have a firm ETA for resolution, we will provide another update by 12:30 PM, or sooner if we have additional information to share.

We are experiencing intermittent missing or delayed EC2 instance and status check metrics in the US-EAST-1 Region. Alarms on delayed or missing metrics may transition into an INSUFFICIENT_DATA state. We are taking multiple parallel paths to mitigate this issue. While underlying resources are not affected by this issue, customers with automated actions based off of delayed or missing metric data may see their automations start. EC2 APIs are not impacted and therefore EC2 AutoScaling will not be affected by this issue.