Detailed root cause analysis investigations with GBG support teams confirmed this was caused by internal network activity against Loqate webservers at one of our datacentres, which caused a spike in CPU utilisation and the increased response times/timeout errors seen.
Support teams shifted traffic over to an alternative datacentre to restore service, before then restarting the non-performant webservers and rebalancing traffic to fully resolve.