Kind of a weasely way to say "are down," or "are having problems," or "are not working."
Like the outage is some kind of external thing. Hey we were just sitting here minding our own business and a random outage came by and jumped into our system.
Having had my systems variously backhoed, struck by lightning, physically unplugged (backup and primary) by a sysadmin (cough who may have on another occasion been me not properly counting the rack I was on cough), and left without mains power for multiple weeks after an electrical fire in a substation, an outage is indeed something that can sneak up on you despite best intentions.
(yes yes "distribute" "build for failure" "it's apple we should expect more" are all valid answers, but wanted to make a tongue in cheek response to your wording.)
"are down" doesn't tell you whether it's intentional or not (whereas "outages" is a word that people don't use for expected downtime). "are having problems" and "are not working" don't even tell you anything about the symptoms. But "experiencing outages" means the service is partially or completely interrupted, and that it wasn't expected downtime.
"Are down" can also suggest that the downtime was deliberate.
[0] https://www.reddit.com/r/apple/comments/87lafa/issue_with_ap...
Edit: Aside Rant: At what point does the OS need to get out of the way and stop trying to earn money but just let the user use it? Bugs like what people describe in r/apple sounds completely unacceptable from an OS-user standpoint.
Here's a quote from a user in that thread,
> I had to turn off my phone. I am getting it every ~15 seconds. It's infuriating.
This reminds me of the system level UIAlertView's that used to pop up regarding iCloud, at seemingly random times.
I'm glad Apple re-worked that flow, but it sounds like several types of (previously) rarely occurring errors trigger similar behavior.
Hopefully this fiasco teaches them a little about being less obtrusive with such messages. In the past, it likely could be chalked up to a user misconfiguration, so they can blame a PEBKAC issue and push it on the user. When the failure is on Apple's end, and it affects many users at once, they'll hear pretty loud and clear that these need to go away.
~45 online services, and most of them are free. Extra cloud storage and third party content are the only things you pay for.
even if this is unrelated - disconcerting to hear that the unit's usability is so closely tied to online services
Figured at that point it was an issue with Apple web services.