EC2 (eu-north-1): Increased Error Rates and Latencies

What to do

• Check whether you use AWS EC2 in eu-north-1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 51m it lasted.

  Anything that failed between 2026-06-30 21:02 UTC and 2026-06-30 21:53 UTC may need a replay.

• Subscribe to AWS's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from AWS 4

1. investigatingJun 30, 2026, 9:02 PM UTC

   We are investigating increased launch errors and API errors in the EU-NORTH-1 Region. Existing instances are not affected by this issue.

   provider

2. investigatingJun 30, 2026, 9:21 PM UTC

   We can confirm increased error rates for the EC2 APIs, as well as errors launching new EC2 instances in the EU-NORTH-1 Region. Other AWS Services that launch new instances or call the EC2 APIs as part of their workflows may also be affected by this issue. During this time, customers may receive an Internal Server Error in the Management Console and APIs. Engineers were automatically engaged and began investigating the issue. We are actively working on identifying the root cause. Existing instances are unaffected by this issue. We will provide an update by 3:15 PM, or sooner if we have additional information to share.

   provider

3. investigatingJun 30, 2026, 9:29 PM UTC

   We are seeing early signs of recovery and continue to work toward full recovery.

   provider

4. investigatingJun 30, 2026, 9:53 PM UTC

   Between 1:42 PM and 2:25 PM PDT we experienced increased error rates and latencies for EC2 APIs in the EU-NORTH-1 Region. This issue also affected new instance launches. Other AWS Services that launch new instances or call EC2 APIs as part of their workflows were also affected by this issue. Existing EC2 instances were unaffected by this issue. During this time, customers would have received an Internal Server Error in the Management Console and APIs. Engineers were automatically engaged and began investigating the root cause. We identified the root cause as a planned configuration change. This change was reverted and we began observing recovery at 2:19 PM. By 2:25 PM, the issue was fully mitigated. We do not expect this issue to reoccur. Since the issue was mitigated at 2:25 PM, we have been processing a backlog for ELB workflows and expect this backlog to complete within the next 30 minutes. We recommend customers retry requests that failed during this time. The issue has been resolved and all services are operating normally.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.