Fourth incident

High Priority Incident - Receiving App - Unable to accept GRN's from EDI suppliers ONLY

Major Resolved View vendor source →

Fourth experienced a major incident on May 31, 2024 affecting Fourth App, lasting 2d 22h. The incident has been resolved; the full update timeline is below.

Started
May 31, 2024, 09:42 AM UTC
Resolved
Jun 03, 2024, 08:18 AM UTC
Duration
2d 22h
Detected by Pingoru
May 31, 2024, 09:42 AM UTC

Affected components

Fourth App

Update timeline

  1. investigating May 31, 2024, 09:42 AM UTC

    We are aware of a high priority incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  2. identified May 31, 2024, 10:15 AM UTC

    We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  3. identified May 31, 2024, 10:23 AM UTC

    UPDATE: As part of the investigation, we have been able to determine that this only affects EDI transmissions. Non EDI suppliers are not impacted by this issue. We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  4. identified May 31, 2024, 11:24 AM UTC

    UPDATE: We have been able to identify that this affects all customers using EDI document transmission and the Receiving App We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  5. identified May 31, 2024, 12:29 PM UTC

    UPDATE: We have been able to identify that this affects all customers using EDI document transmission and the Receiving App We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  6. identified May 31, 2024, 01:25 PM UTC

    UPDATE: We have been able to identify that this affects all customers using EDI document transmission and the Receiving App We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  7. monitoring May 31, 2024, 03:15 PM UTC

    We have now implemented a solution and are confident that the issue is resolved. We do recommend that all users clear cache and cookies to ensure the resolution Fourth have deployed is fully enabled. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

  8. resolved Jun 03, 2024, 08:18 AM UTC

    We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage. We greatly apologise for this disruption.