Our webhosting service CloudVPS encountered downtime during the night of March 29th.
https://cloudvps-status.com/incidents/bbqppjfn4665
After our hosting party restored functionality, our systems automatically rebooted and operations continued as usual.
When higher load occured during the day however, we saw that our SMS service did not reboot fully as expected, and delivered up to five sms messages where one was expected as mentioned here. https://status.signhost.com/incidents/mhc18lwx58cz
Because of the high amount of sms messages our system had to queue, we saw some slowing behaviour in our API, where sometimes it took longer than expected to create a transaction because of the other traffic our queue had to work with. After diagnosing this issue and restoring the queue nodes we were fully operational again. During emergency reboot of the queue node to prevent further slowing of transaction creation, we saw a few errors where transactions could not be created, and this was resolved as soon as reboot was complete.