Further investigation by GBG Support teams has confirmed that the impact was due to a configuration issue following a routine change made. This was quickly identified, and remediation actions are being implemented to prevent reoccurrence.
GBG would like to thank you for your patience whilst we worked to investigate and fix this.