Starting around 9:25am EST today (June 30th) our primary database server locked up, leading to 502 errors and making the service unavailable for everyone. This also affected our email importing and other background jobs. The outage for the web interface lasted about an hour and a half and then it took us a few more hours to clear out the email importing backlog and process all our background jobs. While no emails were lost (they were delayed), unfortunately an hour worth of reporting updates and background app jobs (for example, syncing up your replies with a CRM) were lost in this outage. This was due to a manual error in trying to speed up the recovery. We are terribly sorry for this. We have a few manual steps in recovering from such outages and we are going to work on automating everything so there is no room for such errors.
Please accept our sincere apologies for the trouble this has caused you. We always post any service issues as they happen on Twitter so please follow us there to stay updated - @SupportBee. If you have any questions, please do reach out to us using the 'Contact Us' link in the footer or by sending us a Tweet.