Company Logo

Is there an Fourth outage?

Fourth status: Systems Active

Last checked: 8 minutes ago

Get notified about any outages, downtime or incidents for Fourth and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Fourth outages and incidents

Outage and incident data over the last 30 days for Fourth.

There have been 3 outages or incidents for Fourth in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Fourth

Outlogger tracks the status of these components for Xero:

Mobile Apps Active
Email Active
Help Centre & Chat Active
Phone System Active
Analytics Active
Fourth Platform & Single Sign On Active
Inventory Active
Labour Productivity Active
Macromatix Core Active
Macromatix Mobile Active
Purchasing & Inventory (Adaco) Active
Recipe & Menu Engineering (Starchef) Active
Analytics Active
Applicant Tracking System (ATS) Active
Engage Active
Eparts Active
ESS Active
FnB (Stock Live) Active
Fourth App Active
Fourth Platform & Single Sign On Active
HR (UK) Active
Inventory (Stock R9) Active
Ordering (Marketplace) Active
Payroll Active
Purchase to Pay (Tradesimple) Active
Purchasing and Inventory (Adaco) Active
Recipes and Menus (StarChef) Active
Scheduling (Labour Productivity) Active
Team Hours 3rd Party Active
Team Hours Standalone Active
Analytics Active
Fuego Admin Tool Active
Fuego App Active
HotSchedules Mobile Application Active
HotSchedules Train (Schoox) Active
HotSchedules Web Application Active
Integration Data processing Active
Inventory Active
Labor Productivity Active
Macromatix Core Active
Macromatix Mobile Active
Peoplematter Active
Platform & Single Sign-on Active
Purchase to Pay (Tradesimple) Active
Purchasing & Inventory (Adaco) Active
Recipe & Menu Engineering Active
US HR and Payroll Active
Component Status
Mobile Apps Active
Active
Email Active
Help Centre & Chat Active
Phone System Active
Active
Analytics Active
Fourth Platform & Single Sign On Active
Inventory Active
Labour Productivity Active
Macromatix Core Active
Macromatix Mobile Active
Purchasing & Inventory (Adaco) Active
Recipe & Menu Engineering (Starchef) Active
Active
Analytics Active
Applicant Tracking System (ATS) Active
Engage Active
Eparts Active
ESS Active
FnB (Stock Live) Active
Fourth App Active
Fourth Platform & Single Sign On Active
HR (UK) Active
Inventory (Stock R9) Active
Ordering (Marketplace) Active
Payroll Active
Purchase to Pay (Tradesimple) Active
Purchasing and Inventory (Adaco) Active
Recipes and Menus (StarChef) Active
Scheduling (Labour Productivity) Active
Team Hours 3rd Party Active
Team Hours Standalone Active
Active
Analytics Active
Fuego Admin Tool Active
Fuego App Active
HotSchedules Mobile Application Active
HotSchedules Train (Schoox) Active
HotSchedules Web Application Active
Integration Data processing Active
Inventory Active
Labor Productivity Active
Macromatix Core Active
Macromatix Mobile Active
Peoplematter Active
Platform & Single Sign-on Active
Purchase to Pay (Tradesimple) Active
Purchasing & Inventory (Adaco) Active
Recipe & Menu Engineering Active
US HR and Payroll Active

Latest Fourth outages and incidents.

View the latest incidents for Fourth and check for official updates:

Updates:

  • Time: Sept. 5, 2024, 8:21 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Sept. 4, 2024, 3:41 p.m.
    Status: Monitoring
    Update: UPDTATE: 09/04 We believe that the issues affecting Chase have been resolved. If we receive no further reports of issues, this advisory will be removed on 09/05. Thank you.
  • Time: Sept. 3, 2024, 3:08 p.m.
    Status: Investigating
    Update: UPDATE: 09/03 We are seeing some improvement with this issue and can confirm that there have been successful transfers from Fuego to Chase Debit cards in the last 24 hours. We are in the process of seeking confirmation from our banking partners to understand whether this is fully resolved and will update as soon as possible. Our advice remains, that if you are experiencing issues between Fuego and Chase Bank, please try an alternative payment method.
  • Time: Aug. 29, 2024, 2:53 p.m.
    Status: Investigating
    Update: We are aware of an issue affecting Fuego activity and Chase Bank. Earned wage access (EWA) draws, tip payouts (TPO) and transfers from the Fuego Card could be impacted. If you are experiencing any issues please try to use an alternate method of payment for this type of activity. We are currently in communication with our banking partner in an attempt to resolve this as quickly as possible and will keep this status updated as soon as there is more information available.

Updates:

  • Time: July 30, 2024, 4:30 p.m.
    Status: Resolved
    Update: After monitoring throughout the day, we are confident that the issue is resolved for all customers. 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.
  • Time: July 30, 2024, 8:58 a.m.
    Status: Monitoring
    Update: Dear Customer, We are pleased to inform you that our proactive monitoring efforts have successfully restored our solutions to full service. We have cleared all backlogs and updated all data to ensure accuracy. Rest assured, we will continue to closely monitor performance throughout the day to ensure ongoing reliability. If you happen to notice any data discrepancies on your platform, please don't hesitate to reach out to us via our help center, and we will promptly assist you. Thank you for your understanding and support during this time.
  • Time: July 29, 2024, 1:51 p.m.
    Status: Monitoring
    Update: We are confident that the actions taken previously have returned our Core API and Single Sign On to full functionality. These systems are currently working through the backlog which could take up to 24hrs for this to clear and bring the data in the core solutions up to date. This includes but is not limited to: • POS data submissions • Reporting data • Updates to Single Sign On users • Creation of new SSO users • Updating information of existing employees within our Workforce Management Solutions • Data imports for RME Although there are in-built retry mechanisms in place, if you believe that your platform is missing any data, please raise a ticket via our help centre and we will do all we can to assist. We apologise for this disruption to your service.
  • Time: July 29, 2024, 11:59 a.m.
    Status: Investigating
    Update: Our technical teams have implemented corrective measures that we believe have improved the situation with all affected services. Customers should notice immediate improvements when logging in through SSO. However, please note that it will take some time for the systems to process the backlog of data. We are continuing to investigate the root cause and determine any additional remedial actions that may be required, which could include the resubmission of POS and T&A data submitted during the affected period. The next update will be provided when further information is available.
  • Time: July 29, 2024, 11:37 a.m.
    Status: Investigating
    Update: Our technical teams have implemented corrective measures that we believe have improved the situation with all affected services. Customers should notice immediate improvements when logging in through SSO. However, please note that it will take some time for the systems to process the backlog of data. We are continuing to investigate the root cause and determine any additional remedial actions that may be required, which could include the resubmission of POS and T&A data submitted during the affected period.
  • Time: July 29, 2024, 11:09 a.m.
    Status: Investigating
    Update: Our technical teams have implemented corrective actions that we believe have improved the situation with all affected services. Customers should see immediate improvements when logging in through SSO. However, it will take some time for the systems to process the backlog of data. Please be aware that our teams are continuing to investigate the root cause and any additional remedial actions that may be required.
  • Time: July 29, 2024, 10:39 a.m.
    Status: Investigating
    Update: FOR ALL CUSTOMERS: Given the nature and impact of this incident, we must advise that the following services may be impacted. • POS data submissions • Reporting data • Updates to Single Sign On users • Creation of new SSO users • Updating information of existing employees within our Workforce Management Solutions • Data imports for RME FOR CUSTOMERS USING OUR INVENTORY SOLUTIONS: We strongly advise customers to invoke any disaster recovery procedures they have in place to ensure suppliers receive orders in a timely fashion. 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.
  • Time: July 29, 2024, 10:03 a.m.
    Status: Investigating
    Update: UPDATE FOR CUSTOMERS USING OUR INVENTORY SOLUTIONS: We strongly advise customers to invoke any disaster recovery procedures they have in place to ensure suppliers receive orders in a timely fashion. 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.
  • Time: July 29, 2024, 9:33 a.m.
    Status: Investigating
    Update: 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.
  • Time: July 29, 2024, 9:01 a.m.
    Status: Investigating
    Update: 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.
  • Time: July 29, 2024, 8:30 a.m.
    Status: Investigating
    Update: 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.
  • Time: July 29, 2024, 8 a.m.
    Status: Investigating
    Update: 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.
  • Time: July 29, 2024, 7:47 a.m.
    Status: Investigating
    Update: We are aware of a high priority 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 60 minutes until the incident has been resolved. We apologise for this disruption to your service.

Updates:

  • Time: July 29, 2024, 7:44 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 27, 2024, 4:11 p.m.
    Status: Monitoring
    Update: 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.
  • Time: July 27, 2024, 3:40 p.m.
    Status: Investigating
    Update: 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.
  • Time: July 27, 2024, 3:12 p.m.
    Status: Investigating
    Update: 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.
  • Time: July 27, 2024, 2:43 p.m.
    Status: Investigating
    Update: 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.
  • Time: July 27, 2024, 2:25 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: July 27, 2024, 2:15 p.m.
    Status: Investigating
    Update: 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.

Updates:

  • Time: July 21, 2024, 1:29 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 19, 2024, 8:57 a.m.
    Status: Investigating
    Update: Fourth is aware of reports of a significant Crowdstrike/Microsoft outage. We can confirm that this is NOT impacting the availability of the Fourth platform. We are continuing to monitor the situation and will provide updates when they become available.
  • Time: July 19, 2024, 8:40 a.m.
    Status: Investigating
    Update: Fourth is aware of reports of a significant Microsoft outage. We can confirm that this is NOT impacting the availability of the Fourth platform. We are continuing to monitor the situation and will provide updates when they become available.

Updates:

  • Time: July 19, 2024, 8:35 a.m.
    Status: Resolved
    Update: 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.
  • Time: July 19, 2024, 3:03 a.m.
    Status: Monitoring
    Update: 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.
  • Time: July 19, 2024, 2:12 a.m.
    Status: Investigating
    Update: 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.
  • Time: July 19, 2024, 1:29 a.m.
    Status: Investigating
    Update: 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.
  • Time: July 19, 2024, 12:57 a.m.
    Status: Investigating
    Update: 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.

Check the status of similar companies and alternatives to Fourth

Gusto
Gusto

Systems Active

Rippling
Rippling

Systems Active

Phenom
Phenom

Systems Active

Bullhorn
Bullhorn

Issues Detected

Justworks
Justworks

Systems Active

Webflow
Webflow

Systems Active

Gem
Gem

Systems Active

Lattice
Lattice

Systems Active

EmploymentHero
EmploymentHero

Systems Active

SmartRecruiters
SmartRecruiters

Systems Active

Go1
Go1

Systems Active

The Predictive Index
The Predictive Index

Systems Active

Frequently Asked Questions - Fourth

Is there a Fourth outage?
The current status of Fourth is: Systems Active
Where can I find the official status page of Fourth?
The official status page for Fourth is here
How can I get notified if Fourth is down or experiencing an outage?
To get notified of any status changes to Fourth, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Fourth every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here