Outage in Fourth

P1 -SSO- Unable to login single sign on

Resolved Major
May 11, 2025 - Started about 2 months ago - Lasted about 22 hours
Official incident page

Need to monitor Fourth outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Fourth, and never miss an outage again.
Start Free Trial

Outage Details

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.
Components affected
Fourth Inventory Fourth Purchase to Pay (Tradesimple) Fourth Recipe & Menu Engineering Fourth Purchasing & Inventory (Adaco) Fourth Platform & Single Sign-on Fourth Macromatix Mobile Fourth Hot Schedules Mobile Application
Latest Updates ( sorted recent to last )
RESOLVED about 2 months ago - at 05/12/2025 04:06PM

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.

MONITORING about 2 months ago - at 05/12/2025 10:38AM

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.

IDENTIFIED about 2 months ago - at 05/12/2025 10:01AM

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 about 2 months ago - at 05/12/2025 09:31AM

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 about 2 months ago - at 05/12/2025 08:59AM

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 about 2 months ago - at 05/12/2025 08:30AM

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 about 2 months ago - at 05/12/2025 08:01AM

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 about 2 months ago - at 05/12/2025 07:30AM

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 about 2 months ago - at 05/12/2025 07:00AM

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 about 2 months ago - at 05/12/2025 06:30AM

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 about 2 months ago - at 05/12/2025 05:59AM

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 about 2 months ago - at 05/12/2025 05:26AM

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 about 2 months ago - at 05/12/2025 04:56AM

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 about 2 months ago - at 05/12/2025 04:24AM

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 about 2 months ago - at 05/12/2025 03:52AM

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 about 2 months ago - at 05/12/2025 03:20AM

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 about 2 months ago - at 05/12/2025 02:53AM

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 about 2 months ago - at 05/12/2025 02:18AM

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 about 2 months ago - at 05/12/2025 01:42AM

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.

MONITORING about 2 months ago - at 05/11/2025 07:20PM

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.

INVESTIGATING about 2 months ago - at 05/11/2025 06:45PM

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 about 2 months ago - at 05/11/2025 06:13PM

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 about 2 months ago - at 05/11/2025 05:53PM

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.

Latest Fourth outages

High Priority Incident - Mobile Apps (Ordering, Counting & Receiving) - Intermittent Access Issues - about 1 month ago
High Priority Incident - Single Sign On - Extreme Latency - 6 months ago
P1 - SSO (APAC) - Unable to log in to core application through SSO - 7 months ago
P1 - HotSchedules - "Your connection is not private" Redirect Error - 8 months ago
P1 - Single Sign On - Unable to login through Single Sign On - 8 months ago

Be the First to Know When Vendors Go Down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4400 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook