← Full guide: Alexa Not Responding: Safe Checks for Echo Devices

Safe troubleshooting order

Safe troubleshooting order. Check the cause, evidence to keep, exact recovery steps, and escalation. Based on Alexa Not Responding.

Start here

Reseat the power connector at both ends.

What applies to this exact problem

1. Check power and the physical controls

  1. Reseat the power connector at both ends.
  2. Test the wall outlet with another low-power device.
  3. Use the supplied or manufacturer-approved adapter.
  4. Check that the microphone is not muted.
  5. Move the Echo away from heat, moisture, and tightly enclosed spaces.

Stop using the device if the adapter, cable, plug, or housing is unusually hot, damaged, or smells burnt.

2. Restart without resetting

  1. Disconnect power.
  2. Wait about 30 seconds.
  3. Reconnect power and allow the device to finish starting.
  4. Try one simple request, such as asking for the time.

A restart is reversible. A factory reset is not.

3. Separate device, network, and service problems

  • Confirm another phone or computer can use the same WiFi.
  • Open the Alexa app and check whether the Echo appears online.
  • Move the Echo temporarily closer to the router.
  • Restart the router only when other devices also show network trouble.
  • Check Amazon's service/help channels when several Alexa features fail at once.

Do not weaken router security, expose the network, or disable protections permanently just to make setup work. Use the router and Echo documentation for compatible settings.

4. Check the Alexa app and account

  • Verify the phone is signed into the intended Amazon account.
  • Confirm the correct Echo is selected in the device list.
  • Review pending app and device updates.
  • If one music service or smart-home device fails, reconnect only that service first.
  • Review household/profile settings when the device responds differently for different users.

5. Improve voice recognition conditions

  • Reduce nearby television or speaker noise.
  • Keep the microphones unobstructed.
  • Try the configured wake word from a normal speaking distance.
  • Test in a quieter room to separate acoustic interference from a network issue.

Check these first

  • State the exact expected result and the exact result you have now.
  • Find the official record that owns the result and compare it with your evidence.
  • Change one thing at a time, then verify the final state before moving on.

Fix it in this order

  1. State the exact expected result and the exact result you have now.
  2. Find the official record that owns the result and compare it with your evidence.
  3. Check device power and local status before blaming Wi-Fi or the cloud.
  4. Confirm phone, device, router band, account, and app are using the expected network and region/account.
  5. Restart only one layer at a time: device, app, router, then cloud/account reconnect.
  6. Re-pair only after saving automations/settings you may lose and checking the official reset sequence.
  7. After recovery, test remote control, automation, notifications, firmware, and reconnection after a power cycle.

Build the proof pack

  • Device model/firmware
  • LED/error state
  • Router/network details without passwords
  • App/account error screenshots

Avoid making the case harder

  • Factory-resetting before checking simpler causes
  • Posting Wi-Fi passwords or tokens in support screenshots
  • Changing multiple router settings at once

How you know it is really fixed

  • The official record and your real-world result agree.
  • You have enough written evidence to prove the issue is finished if it returns later.

If it is still not fixed

  1. Vendor status/support
  2. Router/ISP support if the network itself is failing
  3. Warranty/replacement when hardware diagnostics point to a device fault

Official sources from the full guide

Need the complete context?

This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.

Open the full guide