Is Fourth down?
Last checked 1m agoNo incidents right now.
Fourth is operational right now. Last checked 1m ago; the most recent incident resolved 5d ago.
Real-time Fourth status, recent outages, and incident history — pulled directly from Fourth's official status page at https://status.fourth.com every 5 minutes. Pingoru tracks 54 Fourth services and has captured 50 incidents in the last 90 days (97.39% uptime). Get email, Slack, Discord, or webhook alerts the moment Fourth reports a new incident — free for 5 monitors, no credit card.
Active incident 1
-
Timeline · 1 update
- 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
Latest: 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 su…
-
Recent outages & incidents
Past 90 days- EngageMobile AppsInventory (Stock R9)Ordering (Marketplace)Fourth Platform & Single Sign On
Timeline · 5 updates
- 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.
- 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.
- 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.
- 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.
- resolved · Jun 05, 2026, 11:43 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Macromatix Core
Timeline · 13 updates
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- resolved · May 11, 2026, 01:34 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- AnalyticsPhone SystemHotSchedules Web ApplicationInventoryApplicant Tracking System (ATS)Help Centre & ChatHotSchedules Mobile ApplicationPurchasing & Inventory (Adaco)EngageRecipe & Menu Engineering (Starchef)
Timeline · 3 updates
- 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.
- 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.
- resolved · Apr 16, 2026, 11:43 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Fourth outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Fourth outage history →Or sign up free to get alerts when Fourth breaks · 10 free monitors · No credit card
- Started May 28, 2026, 04:58 PM UTC · Resolved Jun 05, 2026, 11:43 AM UTC · 7d 18h
- P1 - Macromatix - Unable to Login ResolvedStarted May 07, 2026, 07:44 AM UTC · Resolved May 11, 2026, 01:34 PM UTC · 4d 5h
- Started Apr 15, 2026, 09:43 AM UTC · Resolved Apr 16, 2026, 11:43 AM UTC · 1d 1h