Gnatta incident

Access Issues

Major Resolved View vendor source →

Gnatta experienced a major incident on February 3, 2023 affecting User Interface and Authentication Server, lasting 12d 5h. The incident has been resolved; the full update timeline is below.

Started
Feb 03, 2023, 09:20 AM UTC
Resolved
Feb 15, 2023, 02:42 PM UTC
Duration
12d 5h
Detected by Pingoru
Feb 03, 2023, 09:20 AM UTC

Affected components

User InterfaceAuthentication Server

Update timeline

  1. investigating Feb 03, 2023, 09:20 AM UTC

    We've received some reports that users are having issues accessing Gnatta. We're urgently investigating these reports and will provide further updates as these become available.

  2. monitoring Feb 03, 2023, 09:33 AM UTC

    We're currently monitoring this issue to ensure proper service has returned. Thanks for your patience whilst we addressed this. We'll post more information once we've had time to analyse what happened.

  3. investigating Feb 03, 2023, 04:08 PM UTC

    While we have been investigating the issue we've received some reports that users are having issues loading Gnatta. We're urgently investigating these reports and will provide further updates as these become available.

  4. monitoring Feb 03, 2023, 04:33 PM UTC

    We're currently monitoring this issue to ensure proper service has returned. We're continuing our investigations into the cause and will update here as more information is available.

  5. investigating Feb 06, 2023, 09:48 AM UTC

    We've received some reports that users are having issues accessing Gnatta this morning. We're urgently investigating these reports and will provide further updates as these become available. Thanks, Gnatta Support

  6. monitoring Feb 06, 2023, 10:04 AM UTC

    We're currently monitoring this issue and can see that performance has improved. We're continuing our investigations into the cause and will post updates here once we've had time to analyse and we have some more information.

  7. monitoring Feb 15, 2023, 11:05 AM UTC

    We've carried out further investigation into this issue with our teams and were able to identify a pattern and replicate the behaviour seen. On 10th February we deployed a change which has since resolved all further occurrences of the issue. Thanks again for your continued patience whilst we addressed this issue.

  8. resolved Feb 15, 2023, 02:42 PM UTC

    This incident has been resolved.