Some of you may know that we had a 2 hour of downtime at the end of the last month. It had caused us to rethink the single server situation. As you some of you are expecting reliable uptime from BeeIMG.
Last week we noticed that mailgun has lot of mail bounces from outlook mail address, because the mail delivery IP had been blocked. Usually mailgun fixes these issues automatically, but the issue was not solved after several days, so we asked them to change the IP. They refuced to do it because our bounce rate was high. This was a given as mailgun was mainly used to confirm valid mail address.
To fix it one option is to deliver mail by ourself, but since our server is IPv6 only, this won't work.
Second option is get our bounced rate back down by adding a notice in the registration page and making the backend validation more tougher. Which we took this option and while some users used a tempary email address(which is okay) some users were still adding non-existing email address.
To combact it, now we will send confirmation email by checking out the email address manually. This will take upto 24 hours. Also the upload page has been enabled to all users, so they can upload images wit…
Over the past few weeks BeeIMG has been a little unstable and just wanted to clarify on what happened.
the first unstable issue which in November were caused by our server provider doing maintenance on our servers. Our AMS node got hanged up during the maintenance and had to be manually restarted. However the impact on the
service was minimal and the maintenance on our CDG node affected our service as its where our databases is hosted. After the maintenance the db server had been moved to under performing hypervisor and
started to slow down the site. We had to move the server again to a
Forward to December, one on of our
free customers started hitting with lot of image view per second and this overloaded memory on AMS server and to redis node to fail. Making maters worse AMS server ran out of disk space. when a fail over to CDG happened
the traffic overload that servers redis node and caused the service to
fail. The site served 503 errors during the…