Fourth incident

P1 - Fuego - Issue creating EWA draws

Critical Resolved View vendor source →

Fourth experienced a critical incident on October 4, 2024 affecting Fuego App, lasting 2d 16h. The incident has been resolved; the full update timeline is below.

Started
Oct 04, 2024, 09:48 PM UTC
Resolved
Oct 07, 2024, 02:30 PM UTC
Duration
2d 16h
Detected by Pingoru
Oct 04, 2024, 09:48 PM UTC

Affected components

Fuego App

Update timeline

  1. investigating Oct 04, 2024, 09:48 PM UTC

    We are aware that a small subset of customers are currently experiencing issues with draws. This 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 Oct 04, 2024, 10:15 PM UTC

    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.

  3. investigating Oct 04, 2024, 10:59 PM UTC

    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 Oct 04, 2024, 11:29 PM UTC

    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. identified Oct 04, 2024, 11:55 PM 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 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  6. identified Oct 05, 2024, 12:28 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 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

  7. monitoring Oct 05, 2024, 12:54 AM 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.

  8. resolved Oct 07, 2024, 02:30 PM UTC

    We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage however a formal Incident Report will be posted here with the next 5 business days. We greatly apologise for this disruption.