Good news! Everything stays online tonight. We’ll schedule another maintenance window for our final server upgrade tomorrow.
As of 11:03 PDT all server operations have been running normally. Sorry about the delayed update.
We’re currently experiencing some issues with our server causing users to experience severe slowness on the site and are working to resolve the problem.
We’re back. Maintenance was completed within 10 minutes, just waited for existing connections to clear before we gave the all good.
Basically, we added additional hardware to the system to account for the delayed response times users have been experiencing. Meanwhile, we’re still preparing for a complete transition of our setup to the Engine Yard Cloud.
We’re about to perform system maintenance. We expect 5-10 minutes of downtime while the server comes back online.
Email notifications and invitations are up and running again. We’re still performing system maintenance though. We’ll post an official status update shortly.
We’re still experiencing outgoing email issues and are working to resolve the problem.
Scheduled maintenance has been pushed back to Saturday. False alarm. No downtime today!
We’ve schedule an emergency maintenance window at 4 p.m. PDT (UTC/GMT -7 hours) to account for the slow response times in Lighthouse.
Maintenance is expected to take 30 minutes, with 5-10 minutes of downtime while the servers restart. We apologize for the short notice and any inconvenience this may cause.
We’re currently experience heavy load times on the server. Users are reporting slow load times and intermittent error pages.
There is an issue with email notifications being sent out to users when a Lighthouse ticket has been updated. All notifications are not currently being delivered. We’re currently working to resolve the issue.
As of 9:15 a.m. PDT the attachment issues that carried over from last night have been fixed. All systems are in working order.
A quick update about the attachments issue in Lighthouse. All attachments are intact. We’re experiencing a hiccup with the linking to the s3 files. We should have this fixed in the morning. Sorry about the delay.