AWS Amazon Elastic MapReduce (N. Virginia) Status

We are investigating increased API error rates in the US-EAST-1 Region.

We continue to investigate increased API error rates in the US-EAST-1 Region.

We continue to investigate increased API error rates in the US-EAST-1 Region

Between 0:11 AM and 4:34 AM/PM PDT we experienced increased API error rates in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Between 5:10 PM on August 7th, and 3:50 AM PDT on August 8th, we experienced increased error rates in starting clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We are investigating increased error rates impacting start up of clusters operations in the US-EAST-1 Region.

We are investigating delays in starting Amazon EMR clusters in the US-EAST-1 Region. Existing clusters are not impacted.

Between 7:00 AM and 8:15 AM PDT we experienced delays in starting Amazon EMR clusters in the US-EAST-1 Region. Existing clusters were not impacted. The issue has been resolved and the service is operating normally.

Between 12:40 PM and 6:30 PM PST we experienced delays in starting and terminating clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We can confirm delays in launching and terminating clusters in the US-EAST-1 Region. Submission of jobs to existing clusters is not impacted. We continue to work towards resolution.

We can confirm delays in launching and terminating clusters in the US-EAST-1 Region and continue to work towards resolution.

We are investigating delays in launching and terminating clusters in the US-EAST-1 Region.

Between 9:37 AM and 5:20 PM PST we experienced increased error rates when launching new clusters in the US-EAST-1 Region and when existing clusters were accessing data and code objects in Amazon S3 in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We continue to see recovery when launching new clusters in the US-EAST-1 Region. We also continue to see recovery when accessing data and code objects in Amazon S3 from existing clusters.

We are starting to see recovery when launching new clusters in the US-EAST-1. We are also starting to see recovery when accessing data and code objects in Amazon S3 from existing clusters in the US-EAST-1 Region.

We can confirm errors launching new Amazon EMR clusters in the US-EAST-1 Region. We are also investigating errors when existing clusters are attempting to access data and code objects in Amazon S3.

Between 12:40 AM and 3:42 AM PST, we experienced delays in running steps, as well as starting and terminating Amazon EMR clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We are investigating delays in starting and terminating clusters in the US-EAST-1 Region.

We are continuing to investigate delays in starting and terminating clusters in the US-EAST-1 Region.

We are continuing to investigate delays in starting and terminating clusters in the US-EAST-1 Region

We are investigating delays in starting and terminating clusters in the US-EAST-1 Region.

Between 5:15 PM and 6:26 PM PDT we experienced delays when launching Amazon EMR clusters in the US-EAST-1 region. The issue has been resolved and the service is operating normally.

We are investigating extended delays when launching Amazon EMR clusters in the US-EAST-1 region. Running clusters are not impacted.

Between 11:15 AM PDT and 12:52 PM PDT we experienced delays when launching Amazon EMR clusters in the US-EAST-1 region. The issue has been resolved and the service is operating normally.

We are continuing to investigate delays in launching Amazon EMR clusters in the US-EAST-1 region. Running clusters are not impacted.

We are investigating delays in launching Amazon EMR clusters in the US-EAST-1 Region. Running clusters are not impacted.

Between 11:30 AM and 1:32 PM PDT , EMR experienced elevated cluster launch failures in the US-EAST-1 Region. Existing running clusters were not affected. The issue has been resolved and the service is operating normally.

We continue to work towards resolving elevated launch error rates and cluster launches are happening at a reduced rate in the US-EAST-1 Region. Running EMR clusters are not impacted.

We are investigating extended delays when launching Amazon EMR clusters in the US-EAST-1 region. Running clusters are not impacted.

We are investigating extended delays when launching Amazon EMR clusters in VPC in the US-EAST-1 Region. Running clusters are not impacted.

We continue to investigate extended delays when launching Amazon EMR clusters in VPC in the US-EAST-1 Region. Running clusters are not impacted.

We are now recovering from extended delays when launching Amazon EMR clusters in the US-EAST-1 Region. We continue to work towards full recovery. Running clusters were not impacted.

From 5:30 PM PDT to 9:45 PM PDT , Amazon EMR experienced delays when launching new clusters in the US-EAST-1 Region. Existing running EMR clusters were not impacted. The service has recovered and is operating normally.

From 5:30 PM PDT to 9:45 PM PDT , Amazon EMR experienced delays when launching new clusters in the US-EAST-1 Region. Existing running EMR clusters were not impacted. The service has recovered and is operating normally.

We are now recovering from extended delays when launching Amazon EMR clusters in the US-EAST-1 region. We continue to work towards full recovery. Running clusters were not impacted.

We continue to investigate extended delays when launching Amazon EMR clusters in VPC in the US-EAST-1 region. Running clusters are not impacted.

We are investigating extended delays when launching Amazon EMR clusters in VPC in the US-EAST-1 region. Running clusters are not impacted.

Between 2:20 AM and 8:35 AM PDT we experienced higher than normal error rates and latencies for Amazon EMR APIs, and delays in starting and terminating clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We are seeing recovery on API error rates and latencies for Amazon EMR API calls in the US-EAST-1 Region. Customers may still see delays in starting and terminating clusters. We continue to work towards full resolution.

We can confirm increased error rates and latencies for all APIs and delays starting and terminating clusters in the US-EAST-1 Region. We continue to work towards resolution.

We are investigating increased error rates and latencies for Amazon EMR APIs in the US-EAST-1 Region.

Between 12:08 AM and 3:40 AM PDT we experienced delays in starting Amazon EMR clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We are investigating delays in starting Amazon EMR clusters in the US-EAST-1 Region.

Between 1:50 AM and 4:08 AM PDT we experienced increased error rates for Elastic MapReduce APIs in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Between 1:50 AM and 4:08 AM PDT we experienced increased error rates for Elastic MapReduce APIs in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We have identified the root cause of the increased error rates for Elastic MapReduce in the US-EAST-1 region and continue to make progress in resolving the issue.

We have identified the root cause of the increased error rates for Elastic MapReduce in the US-EAST-1 region and continue to make progress in resolving the issue.

We continue to investigate increased error rates for Elastic MapReduce in the US-EAST-1 region.

We continue to investigate increased error rates for Elastic MapReduce in the US-EAST-1 region.

We continue to investigate increased error rates for Elastic MapReduce in the US-EAST-1 region.

We are experiencing higher than usual error rates for Elastic MapReduce in the US-EAST-1 region and are investigating.

We are experiencing higher than usual error rates for Elastic MapReduce in the US-EAST-1 region and are investigating.

Between 3:40 PM and 5:44 PM PDT we experienced delays provisioning clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Between 3:40 PM and 5:44 PM PDT we experienced delays provisioning clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

We are continuing to work to resolve the issues causing delays in provisioning EMR clusters in the US-EAST-1 Region. All running EMR clusters are operating normally.

We are continuing to work to resolve the issues causing delays in provisioning EMR clusters in the US-EAST-1 Region. All running EMR clusters are operating normally.

We are continuing to work to resolve the issues causing delays in provisioning EMR clusters in the US-EAST-1 Region. All running EMR clusters are operating normally.

We are continuing to work to resolve the issues causing delays in provisioning EMR clusters in the US-EAST-1 Region. All running EMR clusters are operating normally.

We can confirm increased delays in provisioning EMR clusters in the US-EAST-1 Region.

We can confirm increased delays in provisioning EMR clusters in the US-EAST-1 Region.

We are investigating increased delays in provisioning EMR clusters in the US-EAST-1 Region.

We are investigating increased delays in provisioning EMR clusters in the US-EAST-1 Region.

We are investigating increased delays in provisioning EMR clusters in the US-EAST-1 Region.

Between 7:44 PM PDT on 3/20/14 and 12:14 AM PDT on 3/21/14 EMR experienced high cluster launch latencies. The issue has been resolved and the service is operating normally.

Between 7:44 PM PDT on 3/20/14 and 12:14 AM PDT on 3/21/14 EMR experienced high cluster launch latencies. The issue has been resolved and the service is operating normally.

Between 7:44 PM PDT on 3/20/14 and 12:14 AM PDT on 3/21/14 EMR experienced high cluster launch latencies. The issue has been resolved and the service is operating normally.

Between 7:44 PM PDT on 3/20/14 and 12:14 AM PDT on 3/21/14 EMR experienced high cluster launch latencies. The issue has been resolved and the service is operating normally.

We have identified the issue causing increased latencies in launching EMR clusters in the US-EAST-1 Region and are working to return the service to normal operation. We can confirm that running EMR clusters have not been impacted by this issue.

We have identified the issue causing increased latencies in launching EMR clusters in the US-EAST-1 Region and are working to return the service to normal operation. We can confirm that running EMR clusters have not been impacted by this issue.

We continue to investigate increased latencies in launching EMR clusters in the US-EAST-1 Region. We can confirm that running EMR clusters have not been impacted by this issue

We continue to investigate increased latencies in launching EMR clusters in the US-EAST-1 Region. We can confirm that running EMR clusters have not been impacted by this issue

We continue to investigate increased latencies in launching EMR clusters in the US-EAST-1 Region. We can confirm that running EMR clusters have not been impacted by this issue

We are currently investigating increased latencies in launching EMR clusters in the US-EAST-1 Region.

We are currently investigating increased latencies in launching EMR clusters in the US-EAST-1 Region.

We are currently investigating increased latencies in launching EMR clusters in the US-EAST-1 Region.

We are currently investigating increased latencies in launching EMR clusters in the US-EAST-1 Region.