The PPT
iBC Home   |    The Fly   |    Alpha   |    Ragin' Cajun   |    Woodshedder   |    Danny   |    Chart Addict   |    Gio   |    The Peanut Gallery   |    King of the PG   |   
Stock Discussion, Trading Ideas — iBankCoin.com

AMZN Amazon’s “Un-Planned Event”

by boca on June 6th, 2008 at 2:45 pm
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5 out of 5)
Loading ... Loading ...

Oops, our website is down, says Amazon.

Amazon Un-Planned Event (06/06)
Posted: Jun 6, 2008 10:37 AM
 
Greetings from Amazon.com,

We are currently investigating an issue that has impacted the availability of the Amazon.com website. Engineers are actively engaged in resolving this issue and we will provide an update once the issue is resolved. We appreciate your patience during this time.

Regards,

Technical Account Management

Amazon.com

Amazon is down like the DOW with a big boulder tied to it’s feet and tossed into the river by the local Mafia “boys”.  I love how they call this crap an Un-Planned Event.

If anybody ever tries to tell you Amazon is a tech company, just say Pah-leeze, take your cloud computing mantra from Amazon and sit and spin on it, baby.

AMZN is a wonderful online retailer, and lord knows I’ve made a ton of money from them and paid them a ton of commissions, but their site often runs like it was cobbled together by hamsters who haven’t been fed lately.

Rant over.  I got stopped out of a lot of stocks today, I’m raising cash and going to watch the carnage from the sidelines.  Ciao.

One Response to “AMZN Amazon’s “Un-Planned Event””

  1. nullpointer Says:

    agree on the crap coding

    the last 2 things that i sold on amazon, i wasnt notified via email…i didnt find out they sold until the buyers wrote, asking “where’s my stuff?”

    …and yes, i checked my spam folder, the email wasnt there either

Leave a Reply

Recent Comments on iBC
Top Ranked Peanuts
(20+ votes this month)
ripetrade 4.59
Mr. EB 4.41
Green Writer 4.00

hannamontanna (DECEASED)
Scum Bucket (BANNED)


Script executed in 0.44855618476868 seconds.