Amazon Web Services works for others but not for me. What can I do?

1. Check whether it is only this device: Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service. 2. Test from the command line: Check name resolution and the route, to see where the connection stops. 3. Check your tokens and rate limits: An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down. 4. Restart the router and the device: Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service. 5. Flush the DNS cache: Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again. 6. Turn off VPN and proxy for a moment: VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set. 7. Change the DNS server: If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.

Is Amazon Web Services down?

Q: Is Amazon Web Services down right now?

Problems reported. The problem is reported by Amazon Web Services itself. The site still answers our check, so it may affect only some features or regions.

Amazon Web Services: problems reported

The problem is reported by Amazon Web Services itself. The site still answers our check, so it may affect only some features or regions.

Official status

2 open events (UAE, Bahrain)

From health.aws.amazon.com, read 3 min ago.

Our check, from Germany

Answered in 168 ms

Request to aws.amazon.com, 3 min ago. 258 of 288 checks in the last 24 hours succeeded, median 228 ms.

Is Amazon Web Services working for you?

One click, no account. It helps others see whether the problem is widespread.

We are still collecting reports. The numbers appear once 20 people have answered within 24 hours.

Open incidents

Multiple services – UAE: Region Availability

investigatingMajor impactStarted Mar 1, 12:51 UTC

We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources,…

Multiple services – Bahrain: Region Availability

investigatingMajor impactStarted Mar 2, 05:56 UTC

We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable t…

Response time, last 24 hours

measured from our server in Germany

Time to first responseFailed check

One request every 5 minutes from a single location (Falkenstein, Germany). It shows how the answer time changes; it is not the speed you will see on your own connection.

Works for everyone else? Fix it on your side

Check whether it is only this device. Open the service on your phone using mobile data instead of Wi-Fi. If it works there, the problem is your home network or this computer, not the service.
Test from the command line. Check name resolution and the route, to see where the connection stops.
nslookup aws.amazon.com tracert aws.amazon.com
Check your tokens and rate limits. An expired token or a rate limit returns errors that look like an outage. Read the exact HTTP status code and message before assuming the service is down.
Restart the router and the device. Unplug the router for 30 seconds, plug it back in, wait until it is online again, then restart the computer. This clears stuck connections and gives you a fresh route to the service.
Flush the DNS cache. Windows may still remember an old address for the service. Open Command Prompt as administrator and run the command below, then try again.
ipconfig /flushdns
Turn off VPN and proxy for a moment. VPN exit servers are often rate-limited or blocked. Disconnect the VPN, and in Settings > Network & internet > Proxy make sure no manual proxy is set.
Change the DNS server. If the name still does not resolve, switch DNS in Settings > Network & internet > your connection > DNS server assignment to a public resolver such as 1.1.1.1 or 8.8.8.8.

Still stuck? Search our guides for Amazon Web Services, browse all fix guides, or describe your case.

Recent incidents

Amazon Web Services's feed only reports the current state, not past incidents.

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…