Further investigation by GBG Support teams confirmed the root cause as a configuration issue following a routine change made. This was quickly identified, and a fix was deployed to restore service. Remediation actions are being implemented to prevent reoccurrence.