If it is not on the in-game calendar, it is unscheduled, I believe. Considering all the grief Daybreak got for calling downtimes in the past 'Scheduled' when they were really out of the blue unscheduled, I can see why they are erring in favor of just calling them unscheduled...
It was only about 14.5 hours of notice and I think that is short enough to classify it as unscheduled.
A hard server crash is called "a potential issue", so them calling this an "unscheduled downtime", is not really that surprising... That said, I prefer them to fix bugs early on, rather than let them linger for weeks.
Good rule of customer support: If you overstate the ramifications of a problem and understate the organization that goes into addressing the organization, the customer doesn't feel motivated to whine about it. Somehow the statement of, "Our issue strike team is executing their investigation procedure to look at a potential problem some customers may be experiencing" will garner a lot less frustration than "Yeah, everything is on fire and we locked Mikey in the server until he puts it out."
HAHA... I love this. I missed this. My only hope is one of these server fire patches will fix the game to make it interesting again and not just a regurgitation of higher and higher numbers that will eventually end up with no one able to zone in to an area without taking 10 billion points of damage from proximity to a mob that is one level higher than you.
And it still gave me a chuckle when I saw it. In any case, the proof of things will be in the bugs fixed and not in the title.
