Apple apologizes for widespread service outage

“Several Apple services, including iTunes and the App Store, suffered outages Wednesday that began around 5 a.m. ET and extended through midday,” Everett Rosenfeld reports for CNBC.

“Some users reported seeing connection errors throughout the early morning when attempting to either access apps or download new data through them,” Rosenfeld reports. “Bloomberg reported the outages were found in U.S., Switzerland, Spain, and the U.K.”

“‘We apologize to our customers experiencing problems with iTunes and other services this morning. The cause was an internal DNS error at Apple. We’re working to make all of the services available to customers as soon as possible, and we thank everyone for their patience,’ Apple said in a statement to CNBC,” Rosenfeld reports. “”

Read more in the full article here.

MacDailyNews Take: Oh, for the love of…

Related article:
Apple’s iTunes, app stores, iCloud services experience outages worldwide – March 11, 2015

31 Comments

        1. They do not have to, but they also do not necessarily have to apologize either. It would be interesting to know what came up, and what Apple will do so that it will not be repeated ever after.

    1. Yea. I have a client giving serious thought to Dropbox Business and storing 4TB of data since it is so cheap. I’ve tried to explain the negatives.
      They are not listening.

    2. I know what you mean.

      Take fur-instance my trip to meet with the CEO of Apple the other day. I had a flat tyre. And I said, “Who would ever trust a car to get to a business meeting”.

      /s

  1. DNS is a critical system, and managing it takes great care, and even with the best of care, problems will occur and outages will happen to expect that there will be an issue is foolish. As more people place perhaps sensitive information into the cloud, they should still maintain local backups for their own protection. Possible Cyber attacks could also cause outages..

    Not sure exactly what Apple’s down time stat is, 99%, 98% 99.8%, whatever, considering the number of people they service, I think they are doing pretty well.

    1. Get a life, take 2 minutes and move what you don’t want into a folder and to the last page on your iPhone.. There are reasons Apple provides a core set of apps that they don’t want removed whether you want to use them or not.

        1. If you don’t understand the concept of core services, then you’ll never get it.., go get a POS Android phone with far more crap then you’ll ever see on an iPhone and call it a day… How lame are you that you cannot merely move them out of the way and call it a day, instead of whining online..

          1. It is not lame to not wish to have memory hogged with bullshit apps nobody wants or needs. Apple is just using it’s position to force this shit upon us.

            As to core services- I have owned/used computers going back to the Apple ][, the TRS-80, the Commodore PET, and Sinclair. I learned BASIC on Apples way back in the day. From then until now I have used and been the SysAdmin for a laundry list of UNIX computers- desktop to workstation to minicomputer to …
            Wangs, Data Generals, Digital Vax, SGI Workstations and much more.

            I have been involved in securely sending and using highly sensitive data over networks since before the internet- using DoD’s private setups.

            No, I would’t know anything about computers.

            Apple could make the Watch app stand alone- they just do not want to.

        2. What happens when you want it back and don’t know how to do so? What happens if you someone accidentally deletes it not knowing what it is. How do you software update something that doesn’t exist? Do you keep it hidden and then double QA resources to cover both hidden and un-hidden apps? What about bugs that could be introduced that could inadvertently hide apps? Do you show hidden apps after they are updated? What happens when you can’t find your Watch app? Call AppleCare? Cost Apple money? The apps are part of the operating system. Just like you can’t remove frameworks, you can’t remove core apps.

          Any other reasons?

  2. There may be a deeper issue here. It would seem that for as much time it took to solve the problem, if it was as simple as a DNS error, they spent an awful long time looking at something else. Which leads me to think there was something else.

    What I am saying, it may have only been a DNS error, but they may have coincidentally uncovered something else. We may never know what it was, but I bet we should be thankful. Apple is the Holy Grail of all hacks, and apparently the NSA’s nose picking. Wouldn’t you think 8 hours justifies something intensely significant? Kind of “All Hands On Deck”

    1. DNS servers are generally working copies of the master DNS server, for this reason, changes, including fixes, take time to propagate from the main server to all the copies. The outage was well within the time it would take to diagnose, remedy and propagation a normal DNS error.

  3. What I don’t get is that I was unable to share from my computer to my apple tv in Australia, being given an “error 5599”. Surely approval on an internal system needn’t have to go through Apple every time?

    1. Turning on sharing required authentication of your Apple ID password. That takes a connection to a remote server. The DNS error prevented that connection from happening.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.