From what WayneZ mentioned, it seems it was related to a server issue and it was not an EMO problem. I believe this has now been resolved. You can see the post that WayneZ created here:
Could it happen again, maybe, but hopefully not, but if it does, Living.Ai should be able to resolve it quite quickly.