Failure of our secondary server
Incident Report for Short.cm
Resolved
Today we had an emergency situation. On our secondary server, one of the
processes failed.

We usually don't have situations like this, so we worked on our mistakes
and added monitoring for errors like this. So it will not happen in
future

The server was down for 84 minutes.

Clients, who have only one IP address configured (52.2.56.64), experienced problems with links availability.

To protect from this issue you need to have 2 DNS A records for your domain:
One for 52.21.33.16 and another for 52.2.56.64
Posted Apr 12, 2017 - 19:23 UTC