The IT Nerd

If you rely on Amazon Web Services, and a lot of you do seeing as businesses like  Airbnb, Pinterest, Snapchat’s Bitmoji, Time, Citrix, CNBC, Expedia, Expensify, the U.S. Securities and Exchange Commission (SEC), and Zendesk among other rely on Amazon Web Services to conduct business, I have bad news for you that you likely already know. Amazon Web Services is down. And I really mean down. Here’s the details from USA Today:

Portions of Amazon Web Services, the nation’s largest cloud computing company, went offline Tuesday afternoon, affected multiple companies across the United States but especially on the east coast. The outage appeared to have begun around 12:45 pm ET. It was centered in AWS’ S3 storage system on the east coast. Many of the services that firms use AWS are for back-end processes, and therefore not immediately visible to consumers, though the outage could disrupt customer-facing activities like logins and payments.

Lovely. If you’ve been trying to access your favorite websites and you’ve been having difficulty doing so, this is why you’re having difficulty. Amazon is apparently working on it, but people are already taking to Twitter to express….. Whatever they want to express about the situation:

SEAN SPICER CONFIRMS AMAZON S3 FUNCTIONING NORMALLY pic.twitter.com/XhERorysuR

— tessa (@tepahk) February 28, 2017

So who messed up more The #oscars or Amazon S3 pic.twitter.com/w6KXPD8oDC

— Joe Satterwhite (@JustAnotherJoe3) February 28, 2017

#amazon #s3 , did you try this yet? pic.twitter.com/Tm6QBELIKX

— Ryan Ropero (@ryanropero) February 28, 2017

Throw your stuff in the cloud, they said.

The cloud never goes down, they said.#AWS #Amazon #S3

— david hunegnaw (@hunegnaw) February 28, 2017

UPDATE: Apparently the #Fail includes Amazon itself. Their status page is affected by this which means it is incorrectly reporting the status of Amazon AWS:

oh my god, they can't CHANGE THE COLORS OF THEIR STATUS DASHBOARD BECAUSE IT ALSO RUNS ON THE SERVICE THAT IS DOWN https://t.co/KAkKs8JodS

— Alp (@alplicable) February 28, 2017

UPDATE #2: The issue was resolved just before 5PM PST.

This entry was posted on February 28, 2017 at 3:13 pm and is filed under Commentary with tags Amazon. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.