Pages

Ads 468x60px

Saturday, 11 February 2017

Instapaper: more than 30 hours of breakdown service for bookmarks

Instapaper: more than 30 hours of breakdown service for bookmarks

It is a day of disaster that passed the site Instapaper this Thursday. The bookmark service experienced a failure lasting more than thirty hours.

More than thirty hours without being able to put links aside or access those previously recorded. This is what the users of Instapaper from Wednesday evening to this morning. In this case, a concern about too many accesses to the database, as explained by the service on his blog: "It seems that we have reached the limit of the system for our hosted database, which prevents new ones Items to be registered. Currently, our only option is to export all the data from our old database and integrate them into a new one. "

Instapaper also states that it has not lost any data for users and that all previously saved links are always stored on the servers of the site. Interrogated, the founder of the service, Brian Donohue, explains that he had to solve the crisis alone: ​​"The person who takes care of the maintenance is on vacation, so I had to manage everything myself".

As a reminder, Instapaper is a competitor of Pocket and allows to save links to read them later on another computer or a smartphone thanks to an application proposing a clean interface of reading. The service was bought last August by the social network Pinterest. Former Instapaper employees are now also working for the image sharing service, although the Pinterest teams also supported Brian Donohue during the blackout: "The developer teams helped me a lot, but in the end, 'I am responsible'.

Instapaper was finally again accessible from 4am on Friday after more than 30 hours of blackout. It is possible to save links again and those registered since December 20th can be read again. However, the content registered before this date should only be accessible by 17 February at the latest, as Instapaper explained on a second blog post.

0 comments:

Post a Comment