5 ms·

I'm grasping at straws here, but maybe it was a security breach?

• ferdo 13y ago
  My first thought also.
  • rgbrenner 13y ago
    Why? There's really no reason to think that. Of all of the things that can go wrong - power, equipment, network, etc - you pick 'security breach'... Not impossible.. but not the most likely either.
    • outside1234 13y ago
      Plus its Apple, who have proven themselves as amateurs at anything in the cloud.
    • ferdo 13y ago
      Power, network, etc. have redundancy. Security breach is a show stopper.
      • res0nat0r 13y ago
        Except for the AWS EBS outage a couple of years ago which had nothing to do with a security breach. http://aws.amazon.com/message/65648/ http://aws.amazon.com/message/65648/ Cascading catastrophic failures do happen that don't involve security.
        • ferdo 13y ago
          I'd think that Apple would be happy to tell us it was a simple power/network failure were that the case. Sudden shutdown of vital service + silence = most likely a security prob. I'm not saying that's what it is but it seems likely.
          • res0nat0r 13y ago
            Note that the AWS writeup above didn't get published until a week after the incident. Maybe they don't know enough of what is going on yet (hence why it is an outage in the first place, because something is breaking in unknown ways) and they are focusing on fixing it vs. tweeting status updates without any useful info every 15 minutes...
          • spartango 13y ago
            Silence really doesn't imply anything except that the responsible parties are busy fixing things and that there may not be hands free/allocated to communicate with the outside world. IMO not communicating with the outside world is a fail, but I've seen delays in this when small teams suddenly get swamped.
            • freehunter 13y ago
              I'm sure that the PR department is not busy fixing this technical issue.
              • res0nat0r 13y ago
                PR isn't the best department to post updates regarding technical issues. The technical people who understand the issue are, and they are possibly busy fixing the problem right now.
            • ferdo 13y ago
              Apple is a small team?
              • jfb 13y ago
                Apple teams are much smaller than is often assumed.
                • rdl 13y ago
                  OTOH they outsource a lot. From the people I've talked to at vendors "they (Apple) just don't fucking care" is what I've been hearing on this incident, which makes me think it's nothing technically interesting.
      • ams6110 13y ago
        Should have redundancy. You'd expected it to. But mistakes happen. I recall an incident where a data center found out that their two "redundant" incoming utility power feeds were really wired to the same source only when the power failed.
    • freehunter 13y ago
      If something goes down without warning and there's no response from the organization about why it's down or when it will be back up, security incident is a natural line of thinking. Especially considering it is Apple, they'll likely keep quiet until they know exactly what is going on and how they will resolve it before saying anything on the matter. If it was just power or network, they'd have it back online pretty quick. This seems like they're taking time to investigate something.
      • millerm 13y ago
        I'm guessing we will never hear anything regarding the matter.
        • freehunter 13y ago
          If it was a breech, whether we hear something about it depends on what was accessed and what California's laws have to say about data breech notification requirements.
        • kennywinker 13y ago
          If it was a security breach, and any data was leaked, they have a responsibility to inform anyone affected. At least in California http://oag.ca.gov/ecrime/databreach/reporting http://oag.ca.gov/ecrime/databreach/reporting