brlawyer wrote: »
You mean Tim Cook? He should be replaced forthwith, or at least go back to his COO position.
Google has more outages than Apple, they're just not usually this long.
Google seems to have more frequent outages, just shorter and that they only affect a subset of accounts. That's how modern distributed systems are designed. Apple hasn't gotten the memo.
Hey Apple. Planning on reimbursing us app developers for your incompetence and a day of last sales?
When you create an App Store account, do you accept a Terms of Service agreement that includes a clause about not being allowed to indemnify Apple for lost revenue due to service outages?
From the Apple Developer User Agreement.
Originally Posted by mstone
Agreements will attempt to restrict liability for everything, but courts frequently find these clauses invalid, especially in cases of gross negligence and willful misconduct. State laws also limit what agreements can waive. This is why you have to go to school for three years and pay hundreds of thousands of dollars to be fully qualified to read contracts.
Appears to be back up. Logged in an downloading now.
To have all stores brought down by a DNS error represents an unacceptable "single point of failure" in their architecture. Let's hope they learn from this and refactor their stores so there's less dependency on a single system. Cloud-based systems are called "cloud" because they are meant to be mini-internets... fairly resilient to technical problems. That wasn't the case here.
thrang wrote: »
I am mildly concerned that the length of time this is taking to remedy, still ongoing, is because the issue was from external intrusion. If it was some planned change, I cannot imagine it is not tested on offline systems, nor would it have launched just before the start of the day. And if some error was introduced by Apple, they should have the ability to roll back very quickly.
It is smelling a little odd at this stage, though I hope my speculation is completely misguided.
That is just all kinds of bullshit. Mobile app devs that actively link back to the Apple domain before their apps will open should be publicly shamed.
To have all stores brought down by a DNS error represents an unacceptable "single point of failure" in their architecture.
The issues appeared to be related to verifying the AppleID. The stores were up, you just couldn't buy anything because you could not authenticate, which is the single point of failure. It didn't affect the developer log in though.
I'm not sure what you are referring to but to my knowledge this was not the case. The dev site was unaffected. In addition, at least I, was able to re-download to a new machine previously purchased apps without problem during the outage.