Between 12:52 and 12:55 we saw that calls to our API encountered a higher level of 500 Server Error responses than usual
We have investigated this and it appears to relate to a period where we saw a large spike in traffic, a rapid drop and another spike in quick succession resulting in some temporary 500 errors.
This is now resolved but we will continue monitoring for any further issues.