Sunday, August 12, 2012

Deletion policy of private pads

Following up on the last post we need to extend the deletion policy to private subdomains.

Starting with today we're going to delete all private subdomains which haven't been accessed for more than two years.

To prevent this from happening to your subdomain logging in once every year is more than enough to prevent your subdomain from expiring.

Wednesday, April 11, 2012

Deletion policy of public pads

The constant growth of TitanPad made it necessary that we think about data persistence. While I'm writing this blog post there are close to 90.000 public pads and over 45.000 pads in private subdomains. In total they take up about 100 GiB of disk space.

To slow down the growth of the disk usage we're going to delete public pads which haven't been used for a long time.

Starting with April 22nd 2012 we're going to delete all public pads which haven't been accessed in the last 12 months.

Since most of the public pads are very transient in nature we don't expect to hit major problems with this approach - if you've still got important data in public pads now might be a good time to move them into your own private subdomain!

Friday, February 3, 2012

Data loss of public pads

On Feb 2 2012 around 17:30 UTC an incident caused the complete loss of about 5200 public pads (<padname> URL). Of those 5200 pads about 870 were accessed in the last 9 days.

The data loss was introduced while trying to resynchronize an outdated database slave server which was used for backup purposes.


A backup with the state as of Jan 30 2012 00:17 UTC exists and is available at

This address will be reachable until Feb 14 2012 00:00, please copy the content of the pads you lost over to, if necessary under a new name. The broken Pads on will be removed eventually.

Unfortunately it's not possible to recover the changes between Jan 30 and Feb 2 for the broken/lost pads, we're very sorry about this.

Offering a stable and reliable hosted EtherPad site was the main reason why we started TitanPad in the first place and compromising our vision like this doesn't sit lightly with us. We'll improve our monitoring, backup processes and operations documentation to prevent fiascos like this in the future.