Go1 incident

Go1 Authentication Server experienced a brief connection outage

Notice Resolved View vendor source →

Go1 experienced a notice incident on April 8, 2026 affecting Go1 and API, lasting 46m. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2026, 06:40 AM UTC
Resolved
Apr 08, 2026, 07:26 AM UTC
Duration
46m
Detected by Pingoru
Apr 08, 2026, 06:40 AM UTC

Affected components

Go1API

Update timeline

  1. investigating Apr 08, 2026, 06:40 AM UTC

    We are currently investigating an issue with the database connection outage that occurred around 3:30 AEST.

  2. identified Apr 08, 2026, 06:53 AM UTC

    Our team has determined that there is a connection issue with the database. The Go1 login service may be affected.

  3. investigating Apr 08, 2026, 07:14 AM UTC

    Our team have fixed the connection issue. Users should be able to log in now after refreshing the page. We are monitoring the traffic, and it has started to decrease.

  4. investigating Apr 08, 2026, 07:14 AM UTC

    Our team have fixed the connection issue. Users should be able to log in now after refreshing the page. We are monitoring the traffic, and it has started to decrease.

  5. monitoring Apr 08, 2026, 07:16 AM UTC

    Our team have fixed the connection issue. Users should be able to log in now after refreshing the page. We are monitoring the traffic, and it has started to decrease.

  6. resolved Apr 08, 2026, 07:26 AM UTC

    The database connection outage affecting multiple authentication and authorization services related to identity management has been resolved. We appreciate your patience and sincerely apologize for any inconvenience caused.