Cocolog, rush into large-scale maintenance for 48 hours



"Cocorog Response Problem Notice Blog" is opened, and the progress situation is being made live. It is updated as to what work I am doing every moment, but the comment section is tough.

In the first place, cocolog is becoming heavy weight in the beginning, it can not log in to the management screen, can not post even if login is possible, the text disappears even if posted, or the next day it is reflected in the next day. At the end of the phrase, someone else's article is displayed or my article is displayed somewhere on a different user's blog. There are many mountains in this comment section of "Cocorog Response Problem Announcement Blog" around here.

Below, the background to here and so forth.
【Special】 Cocorog Response Problems Announcement Blog
http://cocolog.typepad.com/blog/

Everything starts from here.

ITmedia News: "Cocorog" is also free to @nifty non-members
http://www.itmedia.co.jp/news/articles/0511/24/news050.html

So, somehow the free members are more functional than paid members.

Slashdot Japan | "cocolog" user, voice complaining about @ nifty's response
http://slashdot.jp/articles/05/12/02/1512201.shtml

At last an angry explosion of paid members. In addition to this.

ITmedia News: "Cocorog" Users complaining about obstacle litigation preparations (1/2)
http://www.itmedia.co.jp/news/articles/0606/20/news057.html

It is already a mess.

See how the disastrous thing is going on in the comment section below.

【Special】 Cocorog Response Problem Information Blog: Notice of Cocolog Maintenance Execution (July 11 - July 13)
http://cocolog.typepad.com/blog/2006/06/711713.html

【Special】 Cocorog Response Problem Notice Blog: About Cocolog Maintenance Execution (7/11 14: 00 - 7/13 14: 00)
http://cocolog.typepad.com/blog/2006/07/711_1400713_140.html

And finally I entered the 48 hour maintenance this time.

Slashdot Japan | Kokorog enters large-scale maintenance for 48 hours
http://slashdot.jp/articles/06/07/11/1437224.shtml

The reason why it will be over 48 hours is explained here.

【Special】 Cocorog Response Problem Information Blog: Notice of Cocolog Maintenance Execution (July 11 - July 13)
http://cocolog.typepad.com/blog/2006/06/711713.html

Well, will it become lighter properly ...... GIGAZINE has also experienced half crying due to a load problem, so I am watching while expecting. Good luck with all the staff.

in Note,   Web Service, Posted by darkhorse_log