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.
Apple Launches MobileMe and Apple TV 2.1
- Thread starter lazygregg
- Start date
- Sort by reaction score
Oh my God... you're right. 13 HOURS! OMG! WTF?! BBQ!!!!!1~
._.
Something tells me that you didn't really need those "services" for the majority of those 13 hours.
Actually, I paid for .mac. On the way to giving me a huge upgrade in disc size and quality of service (for free, and one they never promised or even hinted at) they're running into a few bumps.
I'm not going to complain.
Haha that's funny.
Try the .mac status page, it has more detail. I'm guessing MobileMe is good to go but they're still having some transition / integration issues in shifting over to the other servers...
http://www.apple.com/support/dotmac/
Actually this all depend on the .Mac/MobileMe SLA (Service Level Agreement). I don't have my original information when I signed up for .Mac with me at the moment so I can't find out what the SLA is for sure.
If they provided a 99.9% uptime (or other arbitrary number) and they have breached that then you would have a leg to stand on. Until the SLA is breached we (.mac subscribers) don't really have a leg to stand on.
Just to make it clear I am a .Mac subscriber as well, so I understand your frustration, but you need to be aware of the SLA on services you pay for if downtime could/will cause problems.
I have had responsibility for large enterprise wide installations and one DUPLICATES necessary data in the test environment - tests tests tests and then - and ONLY THEN - takes the old service off line and supplants with the new tested service - BASIC 101 implementation.
Funniest Comment all day...
It IS Apple's responsibility to report to us when WE are the ones experiencing troubles, on a service that we pay $$$ for. I, personally, don't rely on .Mac for much, but there are other people who do. The least they could do is put a "Sorry, We Are Experiencing Troubles" message so we can at least know they acknowledge us...
If you guys need something to keep yourselves occupied while your waiting give this flash game a try.
Its addictive
Portal : Flash Version
Its addictive
Portal : Flash Version
Clearly the .mac 2.0 update is ruining his lemonade stand sales and preventing browsers from surfing his Tupperware/Amway/Mary Kay site.
Nobody with a reputable 24/7 business would use .mac, period.
Funniest Comment all day...
It IS Apple's responsibility to report to us when WE are the ones experiencing troubles, on a service that we pay $$$ for. I, personally, don't rely on .Mac for much, but there are other people who do. The least they could do is put a "Sorry, We Are Experiencing Troubles" message so we can at least know they acknowledge us...
Considering that MobileMe doesn't technically exist yet, are you saying that this message isn't acceptable yet:
Attachments
If that's the case, then you will surely know sometimes roll-outs don't always go 100% to plan, outages go over time etc.
Stuff happens...
Added Perspective - Apple's .Mac services have worked very well for me. My site development is done in iWeb, hosted by Apple, and I don't have to worry about site optimization, FTP uploads, etc. Their service has generally been very good for my needs. Thus - I have supported and trusted them them as "ready for prime time".
This outage is inexcusable - poor implementation design and execution - it really makes them look incompetent.
It will get fixed - but should never have happened.
This outage is inexcusable - poor implementation design and execution - it really makes them look incompetent.
It will get fixed - but should never have happened.
.Mac Down, MobileMe not up
I write web software that processes quite a bit of data, and we have had problems with deployment into production, even with all the testing required for FDA devices. It sucks when a migration doesn't work as planned and tested, but it happens.
With a project of this magnitude, it is extremely hard to have two sets of services up and running at the same time, editing the same data. Most likely database fields needed to be added, and probably (for this big a change) full database structures probably flat out changed so that the software that provides .Mac wouldn't be able to access the information once the database change took place. I'm sure they took a copy of the production servers recently and ran a migration test on it and it worked, or they would have delayed. I'm sure they had a farm of computers pounding the heck out of the testing servers too to simulate millions of users too. But simulation and testing, while are 100% necessary are not 100% proof it will work.
Yes, you always could roll back to your backups, and I'm sure they have logs to add all the mail that came in since their last backup. But then you have to start from the beginning all over again, usually it is better to just keep pushing till it's running.
I don't know what went wrong, but things creep up you'd never imagine moving from development to testing environments, and then further on from testing to production. I can say from experience, I feel for those developers, who hopefully have a Starbucks Batista onsite making quad-shot espressos to keep them going, they'll need it.
I write web software that processes quite a bit of data, and we have had problems with deployment into production, even with all the testing required for FDA devices. It sucks when a migration doesn't work as planned and tested, but it happens.
With a project of this magnitude, it is extremely hard to have two sets of services up and running at the same time, editing the same data. Most likely database fields needed to be added, and probably (for this big a change) full database structures probably flat out changed so that the software that provides .Mac wouldn't be able to access the information once the database change took place. I'm sure they took a copy of the production servers recently and ran a migration test on it and it worked, or they would have delayed. I'm sure they had a farm of computers pounding the heck out of the testing servers too to simulate millions of users too. But simulation and testing, while are 100% necessary are not 100% proof it will work.
Yes, you always could roll back to your backups, and I'm sure they have logs to add all the mail that came in since their last backup. But then you have to start from the beginning all over again, usually it is better to just keep pushing till it's running.
I don't know what went wrong, but things creep up you'd never imagine moving from development to testing environments, and then further on from testing to production. I can say from experience, I feel for those developers, who hopefully have a Starbucks Batista onsite making quad-shot espressos to keep them going, they'll need it.
Well, I agree with you about Apple's message.
But, MobileMe DOES technically exist. They announced it on my computer this morning. It said MobileMe is now available and directed me to install the Mac OS X MobileMe update.
The me.com website does not show a considerate message like the .mac web site does.
MobileMe DOES exist.
1) Me.com has worked several times.
2) Mac.com has intermittently redirected to MobileMe.
3) iPhone can use MobileMe features.
4) The MobileMe software has been pushed to some users by System Preferences (depending on how far they managed to get into the service before it totally died earlier).
5) MobileMe is part of iTunes on Windows, and as such there are users being told they can't login (despite registering on me.com) because the service has failed.
6) Several parts of Apple's site declare that .mac is now MobileMe.
7) I've had an e-mail with MobileMe branding (as if it's just normal to use it).
a) i'm not talking about going to court with them. I am just saying, in terms of general responsibility, they should be telling us what's going on. I think I have more than one "leg to stand on" in that argument.
b) the SLA or EUA ("End User Agreement") or whatever agreement you can come up with has nothing to do telling people what's happening when the service goes down. I am not saying it is unreasonable that it is down, just that it is unreasonable that they don't tell us when we can expect it to be up or why it is down.
On the other point about paying for .mac instead of mobile me, where is that .mac service you paid for? How's it working for you? Can you log on to it? Last I checked, that isn't up either so your point is moot.