Fourth incident

High Priority Incident - Mobile Apps (Ordering, Counting & Receiving) - Intermittent Access Issues

Major Resolved View vendor source →

Fourth experienced a major incident on May 21, 2025 affecting Ordering (Marketplace) and Fourth App, lasting 23h 52m. The incident has been resolved; the full update timeline is below.

Started
May 21, 2025, 09:04 AM UTC
Resolved
May 22, 2025, 08:56 AM UTC
Duration
23h 52m
Detected by Pingoru
May 21, 2025, 09:04 AM UTC

Affected components

Ordering (Marketplace)Fourth App

Update timeline

  1. investigating May 21, 2025, 09:04 AM UTC

    We are aware of a situation where some customers are experiencing delays and timeouts when accessing our mobile apps. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 60 minutes until the incident has been resolved. We apologise for this disruption to your service.

  2. identified May 21, 2025, 09:21 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 21, 2025, 10:05 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.

  4. investigating May 21, 2025, 11:22 AM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 60 minutes until the incident has been resolved. We apologise for this disruption to your service.

  5. monitoring May 21, 2025, 01:02 PM UTC

    We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

  6. resolved May 22, 2025, 08:56 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.