Loading ...
The Buxfer Post » Notice

Archive for the ‘Notice’ Category

Follow ‘buxfer’ on twitter for latest updates

Saturday, August 16th, 2008

You can now follow the user buxfer on twitter to get the latest updates about Buxfer. We will use it to inform you about recent problems / resolutions / new features or any other news which could be relevant.

We should have done this long ago, but I guess better late than never :)

Sorry for all those emails!

Sunday, February 24th, 2008

Some of you might have received 20-30 emails too many from Buxfer, this morning! Sorry folks, we screwed up. Please accept our apologies.

We have taken care of this issue now, and everything should be working fine. Thanks for your patience.

Upcoming downtime

Thursday, January 10th, 2008

The new year has brought on a lot of accolades, tons of new users and a lot of great feedback. However, we also noticed a consistent refrain: Buxfer is very cool and useful, but it’s slow - particularly for our international users! Well, that’s no good and it can certainly be a show-stopper.

So, we bought a new very powerful machine and we will be migrating to that server on Sunday. The planned downtime is from 9pm PST to 12midnight PST. If you find Buxfer unavailable or behaving erratically during that time, please cut us some slack :)

This is just the first step towards enhancing the performance of our system. We know there are quite a few places where we can optimize a lot. We will not stop until our interface is as responsive as GMail, for example, is.

Update: The migration has happened, folks, and we definitely feel a speed difference. Do you find Buxfer to be faster? Whatever the verdict, let us know so we will know what’s working and what isn’t!

Network problems at upstream ISPs

Monday, October 8th, 2007

Folks, one of our upstream ISPs (Savvis or Level3) is having a problem with their networks resulting in extremely slow network connections to Buxfer at least from California (and perhaps other places.) We have contacted our hosting provider about this. I hope you will be patient for the next couple days.

Update [Oct 08, 1747 PST]: Looks like the problem is resolved now.