The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

This incident has been resolved.

The scheduled maintenance has been completed.

This incident has been resolved.

This incident has been resolved.

Freckle is all back in action. The root cause of the errors was a temporary traffic spike on our API. Our emergency systems we have in place to recover from an overload like this worked as expected and Freckle came back after a downtime of about 4 minutes. Obviously this still sucks, and we're taking steps to prevent the same thing from happening again in the future so that temporary traffic spikes will no longer cause Freckle to become unavailable.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

This incident has been resolved.

The scheduled maintenance has been completed.

This incident has been resolved.

The scheduled maintenance has been completed.

This incident has been resolved.

Support chat is available again!

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

This incident has been resolved.

The scheduled maintenance has been completed.

This incident has been resolved.

All queues are processing normally. There's some backlog on syncing with Basecamp, but we're catching up. If that is the case for your account it should be resolved within the next hour or so.

This incident has been resolved.

All systems go! :)

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

We've tuned some background processing to lighten the load and haven't seen 500 errors in several hours. We're marking this issue as solved, but will continue to keep an eye on it.

We have increased capacity and tweaked a few things here and there for smoother loading.

Issues with Amazon's CloudFlare DNS not resolving have been fixed by Amazon. Happy Thanksgiving!

All background processing has been restored to normal.

The scheduled maintenance has been completed.

This incident has been resolved.

All is good! Have a nice weekend! :)

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

This incident has been resolved.

The scheduled maintenance has been completed.

This incident has been resolved.

Everything is back to normal. We've reached out to customers who couldn't update their credit card information in the time the payment provider wasn't available.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

All is good!

Software updates are complete! Have a nice weekend! :)

Landing page and blog are now available again.

We've finished our maintenance. All systems go! :)

Freckle is back! New DNS means that it might take a while for it to be available from your location again. Enjoy your weekend. :)

We've not seen any more issues with Norton DNS in several hours.

Freckle is back! There was a queued process using up too much memory causing a server load issue. We're working on a fix to prevent this from happening again in the future.

Database performance is back to normal. We will continue to monitor for slow queries.

All is back to normal. The root cause was an issue with an import that was processed in the background—we're now debugging exactly why this import stalled and used up resources and working on a fix to prevent this in the future.

We're all back and Freckle works normally. We're still researching the root cause of this problem.

Performance is back to normal. This problem was caused by an issue with Freckle API, which we have identified and will roll out a fix very soon. We'll keep on monitoring'.

This incident has been resolved.

All systems are go—the unicorns are prancing once more! :)

We've moved hosting providers for our landing page and blog, which means the scheduled maintenance will no longer affect the Freckle landing page and blog. Have a nice weekend! :)

This incident has been resolved.

Freckle is back, all systems go!

All systems go. We had to kill and restart a spurious Ruby process. Bad Ruby!

This incident has been resolved.

Freckle is back and up and running!

Database updates are complete and Freckle is available again! Happy 4th of July!

The scheduled maintenance has been completed.

...and we're back. :(

The Github integration now works as expected and will no longer log commits without time information. We also removed empty entries that where created because of this bug.

We've identified an issue with a hanging PhantomJS process that we use for generating graphs for the weekly report emails causing timeouts across the board with Freckle being unavailable for short periods of time. We've restarted the process and performance is back to normal now.

The Timer will no longer display bogus "disconnected" alerts. Please be sure to reload your timer window or simply close and open it again.

Due to a routing misconfiguration the sign in page tried to reload itself—this problem is now fixed and all systems are go!

Freckle was down for about 12 minutes due to a network outage at our hoster. All systems are go now.