Fourth experienced a critical incident on May 7, 2026 affecting Macromatix Core, lasting 4d 5h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.