@ Nifty's cocolog is undergoing large scale maintenance for 53 hours continuous



The maintenance date and time is about 53 hours of 10:00 to 5 December 2006 (Thu) 15:00 on December 5, 2006.

Large-scale maintenance of 48 hours on July 11, large maintenance maintenance of 14 hours on October 3, 8 hours on November 8 and 53 hours at the start of December 5 this time. What it says, it is a number that blots like something difficulty in blog service management. Is it okay ... ?.

It seems that this time large-scale maintenance will divide the database, although it can be displayed during maintenance, comments and trackbacks can not be done and articles can not be posted as well. Recently, it was this reason why nothing crawlers crawled out from the cocologue association ....

Details are as follows.
Information Kokorog: Currently, we are maintaining Cocorog Basic / Plus / Pro.

That's why "Cocorog Response Problems Announcement Blog"The status of maintenance has been written one by one and the opinion from the cocolog user is still exploding in the comment column.

Cocorog Response Problems Announcement Blog: About Distribution Implementation of 12/5 Cocoglog Database

Cocorog Response Problems Announcement Blog: 12/5 cocorog Basic / Plus / Pro Maintenance Announcement

Cocorog Response Problem Information Blog: Cocolog Maintenance progress status (12/5 as of 11:00)

Cocorog Response Problem Information Blog: Cocolog Maintenance progress status (12/5 at 5 pm)

Cocorog Response Problem Information Blog: Cocolog Maintenance progress status (12/5 at 19 o'clock)

Cocorog Response Problem Information Blog: Cocolog Maintenance progress status (12/6 at 10 pm)

Cocorog Response Problems Information Blog: Cocolog Maintenance progress status (12/6 16 as of present time)

Cocorog Response Problems Announcement Blog: 12/6 About the troubles that take time to browse blogs that set up rubbing

Cocorog Response Problem Information Blog: Cocolog Maintenance progress status (12/6 at 20 as of present)

As expected it can not be updated for about 3 days, so the anger of paid users is a big explosion. Although there are quite a lot of writing that you can return the use fee under suspension, I do not know whether there is no problem in terms of regulation or what number of users can not deal with it, but it seems that refunds etc. will not be done .

in Note,   Web Service, Posted by darkhorse_log