Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Multiple Apple Services Experiencing Widespread Outage [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
Doesn't explain why the issue occurs on non-TWC networks though. But if there truly is an issue and they are working on it, at least maybe I can get downloads at home.
It's still very on and off for me. It causes all my devices to sign in and out, then they all panic and lock me out of my account and force me to reset my password. I've done this 5 times. I thought someone was trying to use brute force to hack into my account!
Guess I was a little slow there on getting that posted.
Unfortunately, the world is a more complex place than that. I'm certain they do not take you to the same server - what they may take you to is the same virtual server cluster, but behind that is a whole pool of real servers. Further, there may be many pools around the country using the same IP addresses, and depending on where you are you go to the most local instance. So maybe instead of it being a TWC issue it may be a CDN issue with one (or more) of those server pools.
I'm Comcast and am not having the problem. I also don't have it on AT&T. Nor FiOS (now that I've checked it too).
This actually tends to support the idea that the problem is related to the way the carrier(s) is(/are) routing traffic to the specific address(es) involved.
Just while I did a clean install from the recovery partition and swiped the whole drive before, but luckily it seemed to occur after logging in to the App Store and downloading the additional components.
Just realized that the recovery installation took me back from 10.11.2 Beta 4 to 10.11.0 (15A282b).
Servers are not my strong suit, if you haven't already been able to tell. I am a computer hardware guy. I can build a computer with my eyes closed. So thanks for your help, really appreciate it.
Note to self: if a carrier tells you they're not at fault, don't ever believe them....
lolHey, if it leads to an actual solution then glad to help... My work is in computer networks, with a hobby in programming - so I have a pretty good knowledge base on exactly this kind of issue.
Seems like TWC is admitting to a problem now, and it's getting late (or early) here - so I'm gonna hafta sign off on this for now - but I think you have some new directions to pursue toward resolution and in the meantime, luck!
Or ignorance on their part, even from T3. Perhaps the support tickets have been rolling in since Sunday and they're just now realizing there is a deep seated problem.
But hey, so much contradictory info out there atm. I think it's super cool the proactive role you're taking to try and get this solved btw.
Note to self: if a carrier tells you they're not at fault, don't ever believe them....
Hey, if it leads to an actual solution then glad to help... My work is in computer networks, with a hobby in programming - so I have a pretty good knowledge base on exactly this kind of issue.
Seems like TWC is admitting to a problem now, and it's getting late (or early) here - so I'm gonna hafta sign off on this for now - but I think you have some new directions to pursue toward resolution and in the meantime, luck!
Have a good night, and again thanks for baring with my ignorance on the matter!
As long as they get their act together in the next 12 hours I don't care. Just really frustrated that I have spent well over 12 hours between Apple and TWC over this issue when it was working perfectly Thursday AM. Get off work at 5PM Thursday its been down since.
---
Just got off the phone with TWC. Issue has been affecting them since Thursday PM. There is an issue between Apple's server and their own server. Apparently Apple issued an update to their server on Thursday that caused a disconnect between Apple and TWC. There is no ETA on the fix. This is good and bad news. Good, because now I know whats wrong, bad because its already been almost a week and they still don't have an ETA in sight. They are working directly with Apple. Joy.
So look at that - Apple is partially at fault.
That scenario makes sense to me. It's good news I think, we've been spending days trying to convince people that there even is a problem, now that's acknowledged, let the fixing begin.
I’m surprised you’re surprised. This is Apples MO. They keep schtum about everything until they’ve had time to come up with a patronising, hyperbolic and vague response.
This happens with everything so at least you could say they’re consistent.
This is why "the cloud" shouldn't be the authentication mechanism to get into your devices. I was not impressed when "Windows" decided to switch to "microsoft login" from normal login. My Apple devices don't rely on iCloud for logging into anything.
As for the "only affects WiFi" or "Works on LTE", this likely has more to do with the routing path being taken. If the people experiencing the problem are all on the west coast, their 'icloud' resources might also be on the west coast. So the DNS that resolves the login portal likely goes to different routes. For example AT&T routes through Dallas, Rogers routes through Toronto, T-Mobile routes through Seattle, and so forth.
My toilet is plugged. I sure hope Apple gets this resolved soon.
What does this have anything to do with both Apple and ISP server issues?
Terrible Trolling is terrible
That's a typical telco bs lie. I spent 2 years working for one as a T3 network support engineer. My boss encouraged me to lie about any problems we caused and blame it on someone else.
Their story is just like the post office not being able to deliver your mail because they upgraded their mail trucks. See how dumb that sounds? That's exactly the line of bs they gave you.
I don't care what lie they tell me as long as they are aware of the issue and working on it.