GBG incident

Service Incident for - GBG Go - Multiple Services

Major Resolved View vendor source →

GBG experienced a major incident on May 16, 2026 affecting Data Verification - Australia: Single match standard sources (non-AML) and Data Verification - Australia: Single match standard sources (AML) and 1 more component, lasting 9h 36m. The incident has been resolved; the full update timeline is below.

Started
May 16, 2026, 01:20 PM UTC
Resolved
May 16, 2026, 10:56 PM UTC
Duration
9h 36m
Detected by Pingoru
May 16, 2026, 01:20 PM UTC

Affected components

Data Verification - Australia: Single match standard sources (non-AML)Data Verification - Australia: Single match standard sources (AML)Data Verification - Australia: Single match standard sources (with additional sources) (AML)Data Verification - Australia: Single match standard sources (with additional sources) (non-AML)Data Verification - New Zealand: Single match all sources (including govID)Data Verification (Dual Match) - Australia Dual match additional sources (including govID)Data Verification (Dual Match) - Australia:Dual match all sources (including govID)Data Verification (Dual Match) - Australia: Dual match standard sources (AML)Data Verification (Dual Match) - Australia: Dual match standard sources (non-AML)

Update timeline

  1. investigating May 16, 2026, 01:20 PM UTC

    We are currently experiencing a service disruption that may be preventing you from using our service. We’re sorry for the impact this may be having on your business and we’re working hard to get this back up and running.

  2. investigating May 16, 2026, 04:29 PM UTC

    We're continuing to experience a service disruption that may be preventing you from using our service. We're sorry for the impact this may be having on your business. We're working hard to restore service. Incident Start Time: 16/05/2026 12:27 BST Next Update: 17/05/2026 09:00 BST

  3. resolved May 16, 2026, 10:56 PM UTC

    Service has been restored. We're sorry for the impact this may have had on your business. Action will be taken to determine root cause and remediate where required. Incident Start Time: 16/05/2026 21:25 AEST Incident Resolution Time: 16/05/2026 23:25 AEST