Apple Offers No Explanation for 7-Hour Outage (nbcnews.com)
Apple services went offline for up to 7 hours Thursday -- and the company has yet to offer an explanation. An anonymous reader writes:
The outage affected the App Store, iTunes in the Cloud, Apple TV, Mail Drop, Find my iPhone, and Photos. During the outage, Apple responded to complaints on Twitter, "Thank you for the information. We're aware of this issue and are investigating,"
Tech Times reports that the iCloud Music Library had also experienced an outage on Wednesday, and that just weeks ago Apple released an operating system update which bricked several iPad Pros. And yesterday Amazon also experienced a service outage.
When companies have outages like this and don't want to talk about it it's usually a DDoS.
They don't want to brag they can be DDoSed nor do they want to help pump up the group who did it. They don't want to give any info which is feedback about how well it worked either so the attackers can tune their attacks or gauge their chance of success if it was a dry run.
http://lkml.org/lkml/2005/8/20/95
1) It's really late to post this story
2) Wow, there's a ton of tangential or unrelated crap in the summary
Holy shit the editing sucks now. Amazon's downtime is almost certainly unrelated to Apple's outage. The part about Apple's bad OS update is completely unrelated. Why add that crap to the summary?
Apple services went offline for up to 7 hours Thursday -- and the company has yet to offer an explanation...
Can someone tell us whether Apple's "contract" with its fans, or users of its services, contains any clause that requires it to explain incidents like the one described?
apple, amazon, teamviewer and maybe more have had similarish seeming outages recently. one theory in the teamviewer incident was that attackers manipulated dns to gather credentials that the teamviewer client leaked when redirected. another is that the LinkedIn compromise combined with users using the same password on multiple sites lead to the teamviewer exploits and maybe some on Tumblr and myspace too.
spooky week for security things. if this is an organized thing and now apple accounts are targeted, about to get worse. but maybe its nothing, i honestly have no idea.
-Lod
(He uploaded a series of >2Gb app updates at the same time). https://m.facebook.com/story.p...
You didn't think that Apple runs only Apple computers, did you? Looks like there's been another unintended upgrade. Funny, same thing might be happening to Cricket Wireless today.
I was once asked to gather EU data protection guarantees from various cloud companies. Basically, a new law came in that meant that we couldn't just take their word that they only stored and processed our data on EU datacentres, but an actual written guarantee. ISO 27001 was apart of that.
At the time, Apple were the only large cloud company completely unable / unwilling to supply one. I don't know if that's changed because, well... since then we've only ever supplied fake personal information and/or disabled iCloud on products that we use, and the decision was made that Google Apps would be the cloud services of choice because they complied and were free (for schools).
Hilarious that people point fingers at Google for privacy and data processing, and yet Apple was the one to fail hardest on this, for a period of many months, forcing our hand.
Only slightly tongue in cheek... What did the users do? 7 hours without TV, Tunes and Photos. There has to have been some major angst.
iPads.
Education.
Though I agree with your sentiment, someone should tell Apple that they aren't targeting education. And the rest of the world that also believes that (because they are TOLD that).
Yeah. Amazon servers have outage. Affected Appl servicese.
I'm not sure of the total duration, but Cricket and AT&T both had major, multi-hour outages on Thursday starting about 4:15 p.m. Eastern. From the chart below, it looks like the majority of it lasted...about 7 hours.
http://downdetector.com/status/cricket-wireless
Things that make you go "hmmmm...."
Learning HOW to think is more important than learning WHAT to think.
Technology, i.e. mechanics and electronics, is failure prone. Since major failures don't occur often, we become psychologically conditioned to believe that technology should never fail. I used to battle this all of the time when people would complain about emails not being delivered. It is (and always has been) a best effort service. The SMTP protocol makes allowances for delivery of an email to take 7 days but because most of the time delivery is instantaneous, people have expectations that this will always be. I loved some of the end-users complain that it worked yesterday. Well, yesterday is gone and today is today. I had a PHB once complain about email so I cited the very white paper written on the protocol. I was out of hot water but clearly he did not like the answer.
Seriously-- Itunes and all associated services run on storage controllers.
To me, the obvious answer is a botched OS upgrade on the storage controller head units.
If memory serves, Apple uses Netapp controllers. By now, the support for OnTap 7 should be nearing the end of the legacy support stage. That means data migration to clustered mode in Ontap 8.
Most likely, they established a snapmirror relationship with the new filer equipment, and got the data transferred, but couldnt get the VIF configuration right-- or their 7 mode filer pair went into a takeover-giveback loop cycle of panics.
Not saying netapp is bad equipment, just saying things can and sometimes do happen in a deployment upgrade.
I dont have access to anything that would give me insider knowledge of exactly what happened, but these seem like plausible explanations for an extended, unplanned 7 hour downtime.
It could also be a fibrechannel switch deciding it needed to drop its configuration data and act all goofy, taking out a big chunk of the fabric.
Or worse still, a combination of the two.
I seriously doubt it was planned or malicious.
Forces in government are miffed with Apple. On a rogue basis or not they sent a message. Call me paranoid if you like.
Correction: It's a AWS iFeature