EC2 Network Timeout Diagnostic Troubleshooter (Part 1)
Use the interactive troubleshooter below to identify your EC2 network timeout symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | timeout — ENA Keep alive watchdog timeout | [18509.800135] ena 0000:00:07.0 eth1: Keep alive watchdog timeout. | The ENA device failed to send a keep-alive notification, indicating it reached an unknown state or loaded an irrecoverable configuration. | N/A |
| 2 | timeout — ENA MMIO register read failed for timeout | [ 47.113698] [ENA_COM: ena_com_reg_bar_read32] reading reg failed for timeout. expected: req id offset actual: req id offset | Memory mapped I/O (MMIO) read operations failed during driver initialization due to an incompatible driver, busy hardware, or hardware failure. | N/A |
| 3 | timed out — Network error: Connection timed out (SSH/RDP) | Network error: Connection timed out | The instance's security group lacks an inbound rule allowing traffic from your local computer's public IPv4 address on the required port (22 or 3389). | In the EC2 console, edit the inbound rules for the instance's security group to allow SSH (port 22) or RDP (port 3389) from your IP range. |