Fourth Outage History

Fourth is up right now

Fourth had 28 outages in the last 2 years totaling 98h 53m of downtime — averaging 1.2 incidents per month.

There were 28 Fourth outages since May 31, 2024 totaling 98h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fourth.com

Critical July 19, 2024

P1 - Fourth SSO - Major Outage

Detected by Pingoru
Jul 19, 2024, 12:57 AM UTC
Resolved
Jul 19, 2024, 08:35 AM UTC
Duration
7h 38m
Affected: Platform & Single Sign-on
Timeline · 5 updates
  1. investigating Jul 19, 2024, 12:57 AM UTC

    We are aware of a critical incident that may be affecting some of our customers. We believe this may be linked to a critical outage being experienced by Microsoft Azure which is relied upon to provide essential services. https://azure.status.microsoft/en-us/status This incident is currently being investigated to determine the root cause of the issue and we are doing all we can to minimise impact on our customers in the meantime 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 19, 2024, 01:29 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. We believe this may be linked to a critical outage being experienced by Microsoft Azure which is relied upon to provide essential services. https://azure.status.microsoft/en-us/status This incident is currently being investigated to determine the root cause of the issue and we are doing all we can to minimise the impact on our customers in the meantime 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 Jul 19, 2024, 02:12 AM UTC

    We are aware of a critical incident that may be affecting some of our customers. We are seeing an improvement in the situation and services are slowly coming back online. We are continuing to monitor and are following the below status page closely. https://azure.status.microsoft/en-us/status This incident is currently being investigated to determine the root cause of the issue and we are doing all we can to minimise the impact on our customers in the meantime. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

  4. monitoring Jul 19, 2024, 03:03 AM UTC

    We have seen a significant improvement in the situation and our Azure-related services are now functioning as expected meaning that access to our solutions through Single Sign On is now available. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

  5. resolved Jul 19, 2024, 08:35 AM 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.

Read the full incident report →

Critical July 11, 2024

P1 - Hotschedules - Customers experiencing Login issues

Detected by Pingoru
Jul 11, 2024, 12:49 PM UTC
Resolved
Jul 12, 2024, 09:28 AM UTC
Duration
20h 39m
Affected: HotSchedules Web Application
Timeline · 5 updates
  1. investigating Jul 11, 2024, 12:49 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. identified Jul 11, 2024, 12:58 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.

  3. identified Jul 11, 2024, 01:31 PM UTC

    We have been able to identify the cause of this incident and are currently continuing to work 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.

  4. monitoring Jul 11, 2024, 01:50 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.

  5. resolved Jul 12, 2024, 09:28 AM 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.

Read the full incident report →