The issue is now resolved, it was due to an internal script.
We are experiencing an unusual load on our APIs - some services may be temporarily disrupted
System Status