Apple Needed 12 Hours To Fix ITunes

Posted: Mar 12 2015, 2:40am CDT | by , Updated: Mar 12 2015, 3:14am CDT, in News | Apple

 

Apple needed 12 Hours to Fix iTunes
 

Apple suffered a dramatic iTunes outage that took 11 hours to fix on Wednesday.

As reported yesterday, the iTunes service suffered a major outage that started early Wednesday. It took Apple about 12 hours to fix. The Apple System Status shows an 11 hour outage, but reports of iTunes issues appeared well before Apple started to show the outage in their service monitoring tool.

So what happened? According to a brief Apple statement "an internal DNS error" is to blame. DNS errors are often the cause of severe service outages. A DNS error is time consuming to fix as data is replicated and cached with long update intervals. These long update intervals are necessary for performance. When an error gets into the system, it is like a virus. There should be some thought put in to make fixing a DNS error quicker. 

Another interpretation of why companies often claim that an internal DNS error is to blame might be though to cover up something else. To have an internal DNS error is an accepted bad error that takes long to fix. A company does not loose its face with saying that. It is much worse to say to have been hacked or an employee sabotaged the system.

Apple and content developers and artists lost a ton of money yesterday as iTunes was not able to serve customers for half a day. iTunes customers have been unable to make purchases from the App Store, iTunes Store, iBooks Store, or Mac App Store. 

This story may contain affiliate links.

Comments

The Author

<a href="/latest_stories/all/all/2" rel="author">Luigi Lugmayr</a>
Luigi Lugmayr () is the founding chief Editor of I4U News and brings over 15 years experience in the technology field to the ever evolving and exciting world of gadgets. He started I4U News back in 2000 and evolved it into vibrant technology magazine.
Luigi can be contacted directly at ml@i4u.com.

 

 

Advertisement

comments powered by Disqus