Fourth experienced a critical incident on May 11, 2025 affecting HotSchedules Mobile Application and Platform & Single Sign-on and 1 more component, lasting 22h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 11, 2025, 05:53 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.
- investigating May 11, 2025, 06:13 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.
- investigating May 11, 2025, 06:45 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.
- monitoring May 11, 2025, 07:20 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.
- identified May 12, 2025, 01:42 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.
- identified May 12, 2025, 02:18 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.
- identified May 12, 2025, 02:53 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.
- identified May 12, 2025, 03:20 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.
- identified May 12, 2025, 03:52 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.
- identified May 12, 2025, 04:24 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.
- identified May 12, 2025, 04:56 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.
- identified May 12, 2025, 05:26 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.
- identified May 12, 2025, 05:59 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.
- identified May 12, 2025, 06:30 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.
- identified May 12, 2025, 07:00 AM UTC
We have identified the cause of this incident and are working towards 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.
- identified May 12, 2025, 07:30 AM UTC
We have identified the cause of this incident and are working towards 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.
- identified May 12, 2025, 08:01 AM UTC
We have identified the cause of this incident and are working towards 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.
- identified May 12, 2025, 08:30 AM UTC
We have identified the cause of this incident and are working towards 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.
- identified May 12, 2025, 08:59 AM UTC
We have identified the cause of this incident and are working towards 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.
- identified May 12, 2025, 09:31 AM UTC
We have identified the cause of this incident and are working towards 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.
- identified May 12, 2025, 10:01 AM UTC
We have identified the cause of this incident and are working towards 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.
- monitoring May 12, 2025, 10:38 AM UTC
We have implemented a fix for this incident, and services are now fully restored. Our teams are continuing to monitor closely to ensure stability. Thank you for your patience and understanding throughout this disruption.
- resolved May 12, 2025, 04:06 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 we will aim to post a formal Incident Report here within the next 5 business days. We greatly apologise for this disruption.