Fourth Outage History

Started Oct 10, 2026, 07:26 PM UTC· resolved Oct 13, 2026, 08:03 AM UTC

1. investigating Oct 10, 2026, 07:26 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. resolved Oct 13, 2026, 08:03 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2026, 04:23 PM UTC· resolved Oct 02, 2026, 04:05 PM UTC

1. investigating Oct 01, 2026, 04:23 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. investigating Oct 01, 2026, 04:48 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.

3. investigating Oct 01, 2026, 05:18 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.

4. investigating Oct 01, 2026, 05:46 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

5. investigating Oct 01, 2026, 06:12 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

6. investigating Oct 01, 2026, 06:48 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

7. investigating Oct 01, 2026, 07:15 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

8. investigating Oct 01, 2026, 07: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

9. identified Oct 01, 2026, 08:15 PM UTC

   We have taken some steps to resolve and are beginning to see some signs of improvement. We are continuing to diligently work towards returning service to normal levels. 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.

10. monitoring Oct 01, 2026, 09:15 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.

11. resolved Oct 02, 2026, 04:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 09:22 AM UTC· resolved Sep 17, 2026, 11:01 AM UTC

1. investigating Sep 16, 2026, 09:22 AM UTC

   Good Morning, We have been made aware of an issue with our Single Sign On solution. Currently, users are seeing a "We are down for maintenance" message when accessing or using this solution. Our partner is aware of this and actively working to resolve. More updates will be provided as they become available.

2. investigating Sep 16, 2026, 10:17 AM UTC

   Our IDP provider has informed us of the following. We're no longer pursuing restarts as a path to remediation. Customers continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. More updates will be provided as they become available.

3. investigating Sep 16, 2026, 12:05 PM UTC

   Our IDP provider has informed us of the following. A fleetwide rollout is in progress and customers are starting to see their service return to normal. In parallel, we're working on a code-level permanent fix. The rollout is progressing region by region and we're seeing improvement. We don't have a confirmed time of completion. Customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation.

4. monitoring Sep 16, 2026, 02:50 PM UTC

   Our IDP provider have advised the following: We've completed the next phase of the rollout to the remaining impacted instances. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. Customers who are affected may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. Internally, our alerting is mostly stable and our OE team have not seen and endpoint down for over an hour. As such we will move into monitoring. This concludes the updates.

5. monitoring Sep 16, 2026, 02:52 PM UTC

   Our IDP provider have advised the following: We've completed the next phase of the rollout to the remaining impacted instances. We continue to manually restart ‌instances where the automated fix didn't fully resolve the issue. Customers who are affected may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation. As such we will move into monitoring. This concludes the updates.

6. resolved Sep 17, 2026, 11:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 12, 2026, 11:23 AM UTC· resolved Sep 12, 2026, 04:52 PM UTC

1. investigating Sep 12, 2026, 11:23 AM UTC

   We are aware of an issue with our People System that is impacting customers ability to access this system. In addition, we believe this is impacting associated services to Team Hours. We are continuing to investigate to determine the root cause of the issue. Status and updates will be provided as they become available. We apologise for this disruption to your service.

2. investigating Sep 12, 2026, 12:25 PM UTC

   We are aware of an issue with our People System that is impacting customers ability to access this system. In addition, we believe this is impacting associated services to Team Hours. We are continuing to investigate to determine the root cause of the issue. Status and updates will be provided as they become available. We apologise for this disruption to your service.

3. investigating Sep 12, 2026, 01:02 PM UTC

   We are aware of an issue with our People System that is impacting customers ability to access this system. In addition, we believe this is impacting associated services to Team Hours. We are continuing to investigate to determine the root cause of the issue. Status and updates will be provided as they become available. We apologise for this disruption to your service.

4. investigating Sep 12, 2026, 02:02 PM UTC

   We are aware of an issue with our People System that is impacting customers ability to access this system. In addition, we believe this is impacting associated services to Team Hours. We are continuing to investigate to determine the root cause of the issue. Status and updates will be provided as they become available. We apologise for this disruption to your service.

5. monitoring Sep 12, 2026, 02:37 PM UTC

   Our teams have implemented a solution and are seeing signs of recovery We are confident the actions taken have resolved the issue. Monitoring of the People System and Team Hours will continue to ensure full stability. Thank you for your patience and will confirm once the incident is fully resolved.

6. resolved Sep 12, 2026, 04:52 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 as soon as possible. We greatly apologise for this disruption.

Read the full incident report →

Started Sep 04, 2026, 12:37 PM UTC· resolved Sep 04, 2026, 04:25 PM UTC

1. investigating Sep 04, 2026, 12:37 PM UTC

   We are aware of an issue that is impacting our ability to send emails. Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. No other email providers are currently affected. Please also see https://downdetector.co.uk/status/outlook/ PLEASE NOTE: This could impact and is not limited to Orders Reports Employee updates Password resets. We strongly suggest that customers consider invoking their DISASTER RECOVERY PROCEDURES for their most important functions and if you need to ensure orders are received, telephone contact is recommended. More information will be provided as it becomes available.

2. identified Sep 04, 2026, 12:38 PM UTC

   We are aware of an issue that is impacting our ability to send emails. Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. No other email providers are currently affected. Please also see https://downdetector.co.uk/status/outlook/ PLEASE NOTE: This could impact and is not limited to Orders Reports Employee updates Password resets. We strongly suggest that customers consider invoking their DISASTER RECOVERY PROCEDURES for their most important functions and if you need to ensure orders are received, telephone contact is recommended. More information will be provided as it becomes available.

3. identified Sep 04, 2026, 01:01 PM UTC

   We are aware of an issue that is impacting our ability to deliver emails to customers that use outlook.com / outlook365.com as their mail provider. Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. No other email providers are currently affected. Please also see https://downdetector.co.uk/status/outlook/ PLEASE NOTE: This could impact and is not limited to Orders Reports Employee updates Password resets. We strongly suggest that customers consider invoking their DISASTER RECOVERY PROCEDURES for their most important functions and if you need to ensure orders are received, telephone contact is recommended. More information will be provided as it becomes available.

4. identified Sep 04, 2026, 01:58 PM UTC

   We are starting to see a gradual improvement in the situation and emails are starting to appear. Please note, it will take some time for the backlog of messages to process and we have received no formal notification of resolution at this stage. Further updates will be provided as they become available.

5. resolved Sep 04, 2026, 04:25 PM UTC

   Microsoft, via X, stated 12 minutes ago, "We've applied the mitigations and confirmed the issue resolved after an extended period of monitoring. Further information is provided under EX1467029 in the admin center" No further updates will be provided.

Read the full incident report →

Started Sep 03, 2026, 05:22 PM UTC· resolved Sep 04, 2026, 06:51 AM UTC

1. investigating Sep 03, 2026, 05:22 PM UTC

   We are aware of an issue affecting Fuego activity and Mastercards. 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.

2. investigating Sep 03, 2026, 05:24 PM UTC

   We are aware of an issue affecting Fuego activity and Mastercards. Earned wage access (EWA) draws, tip payouts (TPO) and transfers to MasterCard 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.

3. investigating Sep 03, 2026, 06:17 PM UTC

   UPDATE: We are aware of an issue affecting Fuego activity. Earned wage access (EWA) draws, tip payouts (TPO) and transfers from the Fuego Card to payment cards are currently unavailable. Transfers to bank accounts and other transaction types are currently unaffected. 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.

4. investigating Sep 03, 2026, 06:36 PM UTC

   UPDATE: We are aware of an issue affecting Fuego activity. Earned wage access (EWA) draws and transfers from the Fuego Card to payment cards are currently unavailable. Transfers to bank accounts and other transaction types are currently unaffected. 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.

5. investigating Sep 03, 2026, 06:49 PM UTC

   UPDATE: We are aware of an issue affecting Fuego activity. Earned wage access (EWA) draws, tip payouts (TPO) and transfers from the Fuego Card to payment cards may be affected. Transfers to bank accounts and other transaction types are currently unaffected. 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.

6. resolved Sep 04, 2026, 06:51 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 21, 2026, 03:42 PM UTC· resolved Aug 21, 2026, 05:06 PM UTC

1. investigating Aug 21, 2026, 03:42 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. monitoring Aug 21, 2026, 04:15 PM UTC

   We are observing signs of recovery and are monitoring the situation closely. A further update will be posted once the issue is fully resolved. We apologise for any disruption to your service.

3. resolved Aug 21, 2026, 05:06 PM UTC

   We are confident that the issue has been resolved and customers are now able to login to People System. We apologise for this disruption to your service.

Read the full incident report →

Started Aug 13, 2026, 01:21 PM UTC· resolved Aug 16, 2026, 06:25 PM UTC

1. investigating Aug 13, 2026, 01:21 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. investigating Aug 13, 2026, 01:51 PM UTC

   We are starting to see early signs of recovery and customers may be able to now access the system. We will provide further updates as they become available. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

3. monitoring Aug 13, 2026, 02:06 PM UTC

   We believe that the issue has been resolved and customers are now able to login to Inventory. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

4. resolved Aug 16, 2026, 06:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 04:58 PM UTC· resolved Jun 05, 2026, 11:43 AM UTC

1. investigating May 28, 2026, 04:58 PM UTC

   We are aware of a critical incident that may be affecting some of our customers using our Single Sign On platform. When trying to login, users are met with errors. This will also impact our customer's ability to access connected apps. 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. investigating May 28, 2026, 05:31 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 May 28, 2026, 05:57 PM UTC

   We are exploring multiple avenues of investigation and are seeing signs of recovery We are continuing to work towards identifying the root cause. 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 May 28, 2026, 06:31 PM UTC

   We are confident the issue is no longer present and that customers are now able to login successfully. We are continuing to provide an extended period of monitoring to confirm success. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

5. resolved Jun 05, 2026, 11:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2026, 07:44 AM UTC· resolved May 11, 2026, 01:34 PM UTC

1. investigating May 07, 2026, 07:44 AM UTC

   We are aware of a critical incident that may be affecting some of our customers using Macromatix in the EMEA region. 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 May 07, 2026, 08:12 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.

3. identified May 07, 2026, 08:41 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.

4. identified May 07, 2026, 09:15 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.

5. identified May 07, 2026, 09:49 AM UTC

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

6. identified May 07, 2026, 10:18 AM UTC

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

7. identified May 07, 2026, 10:44 AM UTC

   We have been able to identify the cause of this incident and are 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. We deeply apologise for this disruption.

8. identified May 07, 2026, 11:17 AM UTC

   We believe we have isolated the root cause of the issue affecting MX Services in the EMEA region. The issue has been narrowed down to an internal network issue. We are working on restoring services through multiple paths. We will continue to provide updates here every 30 minutes or less until full service has been restored. We deeply apologise for this disruption.

9. identified May 07, 2026, 11:47 AM UTC

   We believe we have isolated the root cause of the issue affecting MX Services in the EMEA region. The issue has been narrowed down to an internal network issue. We are working on restoring services through multiple paths. We will continue to provide updates here every 30 minutes or less until full service has been restored. We deeply apologise for this disruption.

10. identified May 07, 2026, 12:17 PM UTC

    We believe we have isolated the root cause of the issue affecting MX Services in the EMEA region. The issue has been narrowed down to an internal network issue. We are working on restoring services through multiple paths. We will continue to provide updates here every 30 minutes or less until full service has been restored. We deeply apologise for this disruption.

11. identified May 07, 2026, 01:49 PM UTC

    We believe we have isolated the root cause of the issue affecting MX Services in the EMEA region. The issue has been narrowed down to an internal network issue. We are working on restoring services through multiple paths. We will continue to provide updates here every 30 minutes or less until full service has been restored. We deeply apologise for this disruption.

12. monitoring May 07, 2026, 02:25 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.

13. resolved May 11, 2026, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Apr 15, 2026, 09:43 AM UTC· resolved Apr 16, 2026, 11:43 AM UTC

1. identified Apr 15, 2026, 09:43 AM UTC

   We understand that customers are experiencing issues raising tickets to us through our Customer Success Portal. The issue has been identified and we are currently working to restore access. Further updates will be provided as the situation progresses. In the meantime, we kindly ask that you contact Fourth using the number most relevant to your query using the link below https://uk.fourth.com/support/customer-support PLEASE NOTE: We also ask that you do not attempt to contact us via email as those methods have been retired and are not monitored, thank you.

2. monitoring Apr 15, 2026, 10:00 AM UTC

   UPDATE: We can confirm that a fix has been implemented and the Customer Success Portal is now functioning as expected. Should you continue to experience issues raising tickets via the Customer Success Portal, please call and let us know. We sincerely apologise for the inconvenience this has caused.

3. resolved Apr 16, 2026, 11:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 06, 2026, 09:11 PM UTC· resolved Aug 13, 2026, 02:30 PM UTC

1. monitoring Mar 06, 2026, 09:11 PM UTC

   On March 9, Fourth will implement an update to the Customer Success Portal in alignment with enhanced security requirements. Users will be required to log in before submitting a support ticket. There is no expected impact to service availability or performance. Support continues to operate normally; only the login requirement for submitting a ticket is changing. For more details — including what this means for your experience and how to create or access your portal account — please see our announcement here: Zendesk Security Update: Sign-in Now Required for Support Requests https://help.hotschedules.com/hc/en-us/articles/44077614528909-Zendesk-Security-Update-Sign-in-Now-Required-for-Support-Requests

2. resolved Aug 13, 2026, 02:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 13, 2025, 12:14 PM UTC· resolved Nov 14, 2025, 10:46 AM UTC

1. investigating Nov 13, 2025, 12:14 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. monitoring Nov 13, 2025, 12:22 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.

3. resolved Nov 14, 2025, 10:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 04:10 PM UTC· resolved Oct 30, 2025, 09:00 AM UTC

1. investigating Oct 29, 2025, 04:10 PM UTC

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being verified to ascertain impact. 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 29, 2025, 04:14 PM UTC

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being verified to ascertain impact. Status and updates will continue here every 30 minutes until the incident has been resolved.

3. investigating Oct 29, 2025, 04:32 PM UTC

   We are aware of a critical incident that may be affecting some of our customers. All indicators currently suggest there is widespread issue with Microsoft services. 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 29, 2025, 04:41 PM UTC

   UPDATE: Our investigation has confirmed issue experienced to Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status We will provide further information when this becomes available.

5. investigating Oct 29, 2025, 05:04 PM UTC

   Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status Microsoft have advised: We are actively assessing failover options of internal services from our AFD infrastructure. Our investigation into the contributing factors and additional recovery workstreams continues. More information will be provided within 60 minutes or sooner. We will provide further information when this becomes available.

6. investigating Oct 29, 2025, 05:22 PM UTC

   UPDATE from Microsoft: Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status Microsoft have advised: We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. Fourth are actively exploring options to mitigate this issue and restore services to customers. An update will be provided when we have further information.

7. investigating Oct 29, 2025, 05:51 PM UTC

   Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status Microsoft have advised: We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery. Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace). We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. In addition, Fourth are actively exploring options to mitigate this issue and restore services to customers. An update will be provided when we have further information.

8. investigating Oct 29, 2025, 07:19 PM UTC

   Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft. We are seeing intermittent signs of recovery. Fourth are actively exploring options to mitigate this issue and restore services to customers. An update will be provided when we have further information.

9. identified Oct 29, 2025, 08:58 PM UTC

   We are able to confirm that we are seeing significant improvements in accessing our solutions, however we do believe that customers may still experience intermittent issues. We will continue to monitor and provide further updates as the situation evolves. A further update will be provided when we have more information.

10. monitoring Oct 29, 2025, 10:48 PM UTC

    We have continued to see an improvement across the Fourth suite of products and believe that overall they are in a stable condition. Remedial actions undertaken by Microsoft may still have a small impact, but we firmly believe the situation will improve even further over the next hour. We will continue to monitor throughout the evening and pending any further information, this Incident will be resolved at the start of the day tomorrow. Thank you for your understanding.

11. resolved Oct 30, 2025, 09:00 AM UTC

    Hello, We can confirm that our affected solutions have remained stable for the period since the last update. As such we consider this incident as resolved. Thank you.

Read the full incident report →

Started Oct 25, 2025, 06:37 AM UTC· resolved Oct 31, 2025, 05:32 PM UTC

1. monitoring Oct 25, 2025, 06:37 AM UTC

   As part of our ongoing commitment to security, Fourth is implementing a mandatory password reset for users of the Fourth Single Sign-On (SSO) platform. The next time you log in, you’ll be prompted to reset your password. Simply select “Forgot username or password” and follow the instructions to create a new one. This is a planned update — no action is required until your next login.

2. monitoring Oct 27, 2025, 09:45 AM UTC

   As part of our ongoing commitment to security, Fourth is implementing a mandatory password reset for users of the Fourth Single Sign-On (SSO) platform. The next time you log in, you will be informed your credentials are incorrect. Simply select “Forgot username or password” and follow the instructions to create a new one. This is a planned update — no action is required until your next login.

3. resolved Oct 31, 2025, 05:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:19 AM UTC· resolved Oct 21, 2025, 08:04 AM UTC

1. investigating Oct 20, 2025, 09:19 AM UTC

   Dear Customer, There is currently an issue with Amazon Web Services which is affecting a large portion of the internet. As a leading SaaS provider, we are currently working diligently to ascertain real time impact on services we provide. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status

2. investigating Oct 20, 2025, 09:44 AM UTC

   Dear Customer, UPDATE FROM AWS: Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth is continuing to investigate real time impact on our valued customers.

3. investigating Oct 20, 2025, 10:07 AM UTC

   Dear Customer, UPDATE FROM AWS: Oct 20 3:03 AM PDT We continue to observe recovery across most of the affected AWS Services. We can confirm global services and features that rely on US-EAST-1 have also recovered. We continue to work towards full resolution and will provide updates as we have more information to share. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth is continuing to investigate real time impact on our valued customers.

4. investigating Oct 20, 2025, 10:43 AM UTC

   UPDATE FROM AWS: Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution. Additionally, some services are continuing to work through a backlog of events such as Cloudtrail and Lambda. While most operations are recovered, requests to launch new EC2 instances (or services that launch EC2 instances such as ECS) in the US-EAST-1 Region are still experiencing increased error rates. We continue to work toward full resolution. If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches. We will provide an update by 4:15 AM, or sooner if we have additional information to share. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth is continuing to investigate real time impact on our valued customers.

5. monitoring Oct 20, 2025, 11:11 AM UTC

   UPDATE FROM AWS: Oct 20 4:08 AM PDT We are continuing to work towards full recovery for EC2 launch errors, which may manifest as an Insufficient Capacity Error. Additionally, we continue to work toward mitigation for elevated polling delays for Lambda, specifically for Lambda Event Source Mappings for SQS. We will provide an update by 5:00 AM PDT. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth will continue to monitor and mitigate any impact on our valued customers.

6. resolved Oct 21, 2025, 08:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2025, 09:27 AM UTC· resolved Oct 10, 2025, 09:04 AM UTC

1. investigating Oct 09, 2025, 09:27 AM UTC

   Good Morning, We are currently aware that some customers are experiencing intermittent issues when attempting to access their mobile solutions through Single Sign On We are currently working to resolve this issue. The next update will be provided in 30 minutes.

2. investigating Oct 09, 2025, 09:50 AM UTC

   We are aware an investigating intermitent issues with accessing Fourth Services via SSO in EMEA. Our Technical team are working with our Cloud Infrastructure partner to determine the root cause and fix. We apologies for the disruption to your service.

3. investigating Oct 09, 2025, 10:02 AM UTC

   We are aware of intermitent issues with accessing Fourth Services via SSO in EMEA. Our Cloud Infrastructure partner has confirmed they are experiencing issues with their Content Delivery Network (CDN), which is affecting Fourth and the wider user base. Further updates will be provided, when we get more information. We apologies for the disruption to your service.

4. investigating Oct 09, 2025, 10:08 AM UTC

   UPDATE: We can confirm that the issue being experienced lies with Microsoft services as show here: https://azure.status.microsoft/en-gb/status We are continuously monitoring affected services for signs of recovery. Further updates will be provided, when we get more information. We apologies for the disruption to your service.

5. investigating Oct 09, 2025, 10:34 AM UTC

   We can confirm that the issue being experienced lies with Microsoft services as show here: https://azure.status.microsoft/en-gb/status We are continuously monitoring affected services for signs of recovery. Further updates will be provided, when we get more information. We apologies for the disruption to your service.

6. identified Oct 09, 2025, 11:03 AM UTC

   UPDATE: Microsoft are reporting an improved situation, which should go some way to resolving the issues withing 90 minutes. Fourth are continuing to monitor our services and solutions and will advise when we see an improvement. For Microsoft real-time updates, please see; https://azure.status.microsoft/en-gb/status An update will be provided in the next 30 minutes. We sincerely apologise for the disruption this has caused.

7. identified Oct 09, 2025, 11:35 AM UTC

   UPDATE: Microsoft are reporting an improved situation, which should go some way to resolving the issues withing 90 minutes. Fourth are continuing to monitor our services and solutions and will advise when we see an improvement. For Microsoft real-time updates, please see; https://azure.status.microsoft/en-gb/status An update will be provided in the next 30 minutes. We sincerely apologise for the disruption this has caused.

8. monitoring Oct 09, 2025, 12:03 PM UTC

   Our testing shows we are able to gain access through Single Sign On and therefore we believe this issue has been resolved. We will continue to monitor https://azure.status.microsoft/en-gb/status And provide further updates if required.

9. resolved Oct 10, 2025, 09:04 AM UTC

   Good Morning, After reviewing the below, we are confident the issues experienced by Microsoft have been resolved and all services provided by Fourth are no longer impacted. https://azure.status.microsoft/en-gb/status We apologise for the disruption this has caused.

Read the full incident report →

Started Sep 11, 2025, 12:59 PM UTC· resolved Sep 30, 2025, 08:00 AM UTC

1. monitoring Sep 11, 2025, 12:59 PM UTC

   We are aware of connectivity issues affecting customers in the Middle East region. This is related to a major subsea cable cut in the Red Sea, which is impacting internet traffic across several providers in the area. Some customers may experience slow response times or intermittent access to Fourth solutions. Our infrastructure and services are fully operational — the disruption is due to external internet routing issues outside of our control.

2. monitoring Sep 11, 2025, 03:50 PM UTC

   We are aware of connectivity issues affecting customers in the Middle East region. This is related to a major subsea cable cut in the Red Sea, which is impacting internet traffic across several providers in the area. For further information relating to this incident, please see the below article; https://gulfnews.com/technology/red-sea-cable-chaos-why-the-internet-didnt-go-dark-1.500263896 Some customers may experience slow response times or intermittent access to Fourth solutions. Our infrastructure and services are fully operational — the disruption is due to external internet routing issues outside of our control. We will continue to monitor and provide an update when this situation improves.

3. resolved Sep 30, 2025, 08:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2025, 09:04 AM UTC· resolved May 22, 2025, 08:56 AM UTC

1. investigating May 21, 2025, 09:04 AM UTC

   We are aware of a situation where some customers are experiencing delays and timeouts when accessing our mobile apps. 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.

2. identified May 21, 2025, 09:21 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 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

3. identified May 21, 2025, 10:05 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 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

4. investigating May 21, 2025, 11:22 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. Status and updates will continue here every 60 minutes until the incident has been resolved. We apologise for this disruption to your service.

5. monitoring May 21, 2025, 01:02 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.

6. resolved May 22, 2025, 08:56 AM UTC

   We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage. We greatly apologise for this disruption.

Read the full incident report →

Started May 11, 2025, 05:53 PM UTC· resolved May 12, 2025, 04:06 PM UTC

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.

15. 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.

16. 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.

17. 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.

18. 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.

19. 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.

20. 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.

21. 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.

22. 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.

23. 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.

Read the full incident report →

Started Jan 02, 2025, 05:27 PM UTC· resolved Jan 07, 2025, 09:20 AM UTC

1. investigating Jan 02, 2025, 05:27 PM UTC

   We are aware that some customers are currently experiencing latency when logging in to Single Sign On and using connected applications. Our teams have been actively working throughout the day to address this issue, and investigations are progressing. Testing confirms that all applications remain operational, though performance may be slower than usual. We apologise for the inconvenience caused and assure you that we are prioritising a swift resolution. Further updates will be provided as soon as we have additional information.

2. monitoring Jan 03, 2025, 09:38 AM UTC

   This morning our development team have implemented a fix and the result of this is is an immediate improvement in log in and response times. We are confident that this issue has now been resolved but if you continue to see issues, please let us know. We sincerely apologise for the inconvenience this has caused.

3. resolved Jan 07, 2025, 09:20 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 →

Started Nov 15, 2024, 10:16 AM UTC· resolved Nov 15, 2024, 05:42 PM UTC

1. investigating Nov 15, 2024, 10:16 AM UTC

   Dear Customer, We have been made aware of a critical incident affecting some customers. Salesforce is currently investigating the root cause of the issue. You can find updates at the following link: https://status.salesforce.com/incidents/13457 We apologise for this disruption to your service. The next update will be shared once we have more significant information.

2. identified Nov 15, 2024, 10:53 AM UTC

   Salesforce has been able to identify the cause of this incident and is currently working towards finding an appropriate resolution. You can find updates at the following link: https://status.salesforce.com/incidents/13457 We apologise for this disruption to your service. The next update will be shared once we have more significant information.

3. monitoring Nov 15, 2024, 12:28 PM UTC

   Salesforce has now implemented a solution and is currently monitoring for completeness. The team is seeing positive results after completing the rollback. Due to the scale of the issue, the rollback is being implemented in stages. Affected customers should notice improved performance as each rollback is completed. We apologise for this disruption to your service.

4. resolved Nov 15, 2024, 05:42 PM UTC

   We are confident that the fix applied by Salesforce, along with internal monitoring this afternoon, has resolved the incident. This will conclude the updates to the status page regarding this outage however a formal Incident Report will be posted here within the next 5 business days. We greatly apologise for this disruption.

Read the full incident report →

Started Nov 13, 2024, 01:01 AM UTC· resolved Nov 13, 2024, 01:45 AM UTC

1. investigating Nov 13, 2024, 01:01 AM 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 apologize for this disruption to your service.

2. identified Nov 13, 2024, 01:17 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 apologize for this disruption.

3. identified Nov 13, 2024, 01:19 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Nov 13, 2024, 01:30 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 apologize for this disruption to your service.

5. resolved Nov 13, 2024, 01:45 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 apologize for this disruption.

Read the full incident report →

Started Oct 28, 2024, 10:46 AM UTC· resolved Oct 30, 2024, 11:17 AM UTC

1. investigating Oct 28, 2024, 10:46 AM 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 Oct 28, 2024, 11:08 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.

3. identified Oct 28, 2024, 11:49 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.

4. identified Oct 28, 2024, 12:14 PM UTC

   UPDATE: Should you continue to experience difficulties accessing through a browser, we can confirm that customers accessing Single Sign On through mobile devices can do so successfully. 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.

5. monitoring Oct 28, 2024, 12:35 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.

6. resolved Oct 30, 2024, 11:17 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 →