Item checks affected by the incident:
UK Credit Header Identity (0154)
UK Credit Header AML (0155)
Impact Timescales
21:50 – 22:00 UK Credit Header Identity (0154) (Service was down)
21:50 – 22:00 UK Credit Header AML (0155) (Service was down)
22:00 – 01:00 UK Credit Header Identity (0154) (Local data file enabled)
22:00 – 01:00 UK Credit Header AML (0155) (Local data file enabled)
Cause Event
On Wednesday 15th of January, we experienced a service issue with our credit service that affected the above item checks.
The supplier’s investigation has identified that the cause of the impact was due to a Domain Controller going offline due to a storage space alert. The server support team expected that the application would have been able to connect to a secondary Domain Controller automatically, whilst the primary Domain Controller was being addressed. However during the root cause analysis it was discovered that the secondary server configured on the application servers was invalid. As a result the client applications were impacted.
At GBG we utilise a local Credit Header data file for UK Credit Header item checks (0154/0155) that is brought into use when there is a service outage for this supplier. It provides the capability to support basic credit header file matches while the supplier is unavailable (but does not support ‘advanced credit header’ responses, such as matching against multiple credit sources). The local data file is invoked when there is an outage for the supplier or planned maintenance. In these incidents, as the supplier was unable to process ID3global transactions the platform determined there to be a supplier outage and invoked that local file.
Timeline of events
Remediation Actions
The invalid secondary Domain Controller server configuration was removed from all the application servers and was updated with alternate working Domain Controller server.
This was completed and tested by supplier.
We are sorry for any inconvenience caused.