January 22, 2010
December 14, 2009
~

Our jobs processor is a little backed up at the moment.  We apologize for any delays in the system and should be back up to speed shortly.

December 3, 2009
~

s3 attachment issues have been fixed.

~

We’re currently investigating reports of issues involving attachments and s3.

October 20, 2009
~

Restore of membership data complete. All systems are go. If you have any issues, let us know on support@lighthouseapp.com.

~

About an hour ago, a bad db query caused a number of membership data to be corrupted so some users are noticing they do not have access to their accounts.  We are working to restore the data now.  You can also get a fresh invite to the account. We apologize about the issue.

October 5, 2009
~

Look like we’re all caught up.  Sorry about the delay.

September 28, 2009
~

Our job queue is currently running behind schedule. We’re working to resolve the issue now and get everything back up to speed.

September 23, 2009
~

We’ve received multiple reports from users about email issues in Lighthouse.  We’re currently investigating.

September 2, 2009
~

All systems are back to stable. Sorry about the downtime.  We’re working with our host to prevent it from happening in the future.

~

Our host is currently experiencing an issue with the cluster which is causing Lighthouse to be unreachable.  We’re working with them while they investigate the issue.

August 29, 2009
~

There is an issue with editing a tickets body/comment after it has been created, where the changes are not reflected in the interface.  We’re currently working on the issue and will deploy a fix as soon as possible.

August 24, 2009
~

We’re experiencing some intermittent database and response time spikes, which may cause the site to respond slowly or occasionally error out.

August 19, 2009
~

Everything is running smooth again. If you are experiencing any issues please let us know at support@lighthouseapp.com

~

We’re currently experiencing some extremely slow response times on the server, causing most users to just see errors after long periods of waiting.