Thanks for your patience whilst we rectified the issue yesterday, to give you a little more information about what happened and how we will prevent it from happening in the future, here is the breakdown. 

What happened? 

Between the hours of 11:15 am and 12:30 pm on Thursday 12th May 2022, a subset of Signable API users encountered a server 500 error when trying to interact with it. 

The event was triggered by a change first deployed at 10:27am, a failure in the automated deployment process meant that not all code was deployed as expected. 

The issue was detected within a minute of deploying and the team immediately proceeded to manually intervene and force a full re-deploy which reverted the code changes to get the system back to its original state. 

What are we doing about this? 

We’re bolstering the automated deployment routine to make sure all deployment tasks are fully integrated.

If you need any more information get in touch.