2016, 01/30 01:20 (3375day) Posted
| 3371day Updated
We have confirmed that the problem has been resolved at 21:10 on 02/02, so this is the end of the matter.
We apologize for the inconvenience caused.
At 02/02 17:57, we found a fatal problem that seems to be the cause of the failure and fixed it.
I am observing the progress.
The workaround code was updated at 02/02 05:20, and the cause is still unknown, but we are observing the progress.
The failure was restored at 02/01 23:40,
We are still working on this as we have not yet identified the cause.
I'm sorry for causing you trouble.
It reoccurred around 21:00 on 02/01, and we are currently working on it.
There is a possibility of a software problem, but the cause has not yet been determined.
I'm sorry for causing you trouble.
The failure was resolved at 23:00 on 01/31, but
Since the cause has not yet been identified, we will continue to observe the situation for a few days.
I'm sorry for causing you trouble.
The problem has been occurring again since around 21:00 on 01/31.
We are currently working on it. We apologize for the inconvenience.
The service was restored by switching the equipment on 01/30 01:57.
Please accept my apologies for any inconvenience.
We are conducting temporary maintenance due to a MagicalDraw server failure.
We are in the process of switching the equipment, but as the server is located in a remote location, the recovery time has not yet been determined.
I'm sorry for causing you trouble.
https://magical.kuku.lu/?3256
ツイート
Articles with a posting date near the same category as this article:
2016, 02
2016, 01
2016/01/30
MagicalDraw
Apology and notification regarding equipment failure (resolved)
2015, 12
