Fourth incident

Critical Incident - Multiple Solutions Inaccessible

Critical Resolved View vendor source →

Fourth experienced a critical incident on July 27, 2024 affecting Engage and HR (UK) and 1 more component, lasting 1d 17h. The incident has been resolved; the full update timeline is below.

Started
Jul 27, 2024, 02:15 PM UTC
Resolved
Jul 29, 2024, 07:44 AM UTC
Duration
1d 17h
Detected by Pingoru
Jul 27, 2024, 02:15 PM UTC

Affected components

EngageHR (UK)PayrollFnB (Stock Live)Inventory (Stock R9)Purchase to Pay (Tradesimple)Fourth App

Update timeline

  1. investigating Jul 27, 2024, 02:15 PM UTC

    We are aware of a critical 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. investigating Jul 27, 2024, 02:25 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 27, 2024, 02:43 PM 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 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  4. investigating Jul 27, 2024, 03:12 PM 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 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  5. investigating Jul 27, 2024, 03:40 PM 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 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  6. monitoring Jul 27, 2024, 04:11 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.

  7. resolved Jul 29, 2024, 07:44 AM UTC

    This incident has been resolved.