Fourth 장애 기록

1. 2026년 9월 4일 PM 12:37 UTCinvestigating

   우리는 이메일 보내기 능력에 영향을 미치는 문제의 인식입니다. 08:00 UTC를 시작으로 Microsoft는 모든 M365 지역에 걸쳐 번거로운 이메일의 증가 된 볼륨을 유발하는 사건을 경험했습니다. 영향을받는 응답은 "451 4.7.500 서버 바쁜"로 돌아갑니다. 우리 팀은 적극적으로 상황을 모니터링하고 있습니다. 다른 이메일 공급자는 현재 영향을 미칩니다. 자주 묻는 질문 https://downdetector.co.uk/status/outlook/ 참고 사항: 이것은 영향을 미칠 수 있고 제한되지 않습니다. 이름 * 제품정보 Employee 업데이트 비밀번호 재설정. 우리는 강하게 고객이 그들의 가장 중요한 기능을 위한 그들의 DISASTER RECOVERY PROCEDURES를 부각하는 것을 고려하고 당신이 주문이 받은 경우에, 전화 접촉 추천됩니다. 더 많은 정보는 이용 가능합니다.

2. 2026년 9월 4일 PM 12:38 UTCidentified

   우리는 이메일 보내기 능력에 영향을 미치는 문제의 인식입니다. 08:00 UTC를 시작으로 Microsoft는 모든 M365 지역에 걸쳐 번거로운 이메일의 증가 된 볼륨을 유발하는 사건을 경험했습니다. 영향을받는 응답은 "451 4.7.500 서버 바쁜"로 돌아갑니다. 우리 팀은 적극적으로 상황을 모니터링하고 있습니다. 다른 이메일 공급자는 현재 영향을 미칩니다. 자주 묻는 질문 https://downdetector.co.uk/status/outlook/ 참고 사항: 이것은 영향을 미칠 수 있고 제한되지 않습니다. 이름 * 제품정보 Employee 업데이트 비밀번호 재설정. 우리는 강하게 고객이 그들의 가장 중요한 기능을 위한 그들의 DISASTER RECOVERY PROCEDURES를 부각하는 것을 고려하고 당신이 주문이 받은 경우에, 전화 접촉 추천됩니다. 더 많은 정보는 이용 가능합니다.

3. 2026년 9월 4일 PM 1:01 UTCidentified

   우리는 그들의 우편 공급자로 outlook.com/outlook365.com를 사용하는 고객에게 이메일을 전달하는 능력에 영향을 미치는 문제의 인식입니다. 08:00 UTC를 시작으로 Microsoft는 모든 M365 지역에 걸쳐 번거로운 이메일의 증가 된 볼륨을 유발하는 사건을 경험했습니다. 영향을받는 응답은 "451 4.7.500 서버 바쁜"로 돌아갑니다. 우리 팀은 적극적으로 상황을 모니터링하고 있습니다. 다른 이메일 공급자는 현재 영향을 미칩니다. 자주 묻는 질문 https://downdetector.co.uk/status/outlook/ 참고 사항: 이것은 영향을 미칠 수 있고 제한되지 않습니다. 이름 * 제품정보 Employee 업데이트 비밀번호 재설정. 우리는 강하게 고객이 그들의 가장 중요한 기능을 위한 그들의 DISASTER RECOVERY PROCEDURES를 부각하는 것을 고려하고 당신이 주문이 받은 경우에, 전화 접촉 추천됩니다. 더 많은 정보는 이용 가능합니다.

4. 2026년 9월 4일 PM 1:58 UTCidentified

   우리는 상황과 이메일의 점차 개선을보고 시작합니다. 참고, 그것은 처리하는 메시지의 backlog에 대한 몇 시간을 가지고 우리는이 단계에서 해결의 공식 알림을받지 않았다. 더 많은 업데이트가 제공 될 것입니다.

5. 2026년 9월 4일 PM 4:25 UTCresolved

   Microsoft, X를 통해, 12 분 전에 명시, "우리는 완화를 적용하고 감시의 장시간 기간 후에 해결된 문제점을 확인했습니다. 더 많은 정보는 관리자 센터에서 EX1467029 아래에 제공됩니다" 더 이상 업데이트가 제공되지 않습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 3일 PM 5:22 UTCinvestigating

   우리는 Fuego 활동과 Mastercards에 영향을 미치는 문제의 인식입니다. 수입된 임금 접근 (EWA) 끌기, 끝 지불금 (TPO) 및 Fuego 카드에서 이동은 충격적일 수 있었습니다. 어떤 문제가 발생하면이 유형의 활동에 대한 지불의 대체 방법을 사용해보십시오. 우리는 현재 가능한 한 빨리 해결하려고 시도에 우리의 은행 파트너와 통신하고이 상태가 가능한 한 빨리 업데이트 될 것입니다.

2. 2026년 9월 3일 PM 5:24 UTCinvestigating

   우리는 Fuego 활동과 Mastercards에 영향을 미치는 문제의 인식입니다. 수입된 임금 접근 (EWA) 끌기, 팁 지급 (TPO) 및 마스터 카드로 전송은 영향을 미칠 수 있습니다. 어떤 문제가 발생하면이 유형의 활동에 대한 지불의 대체 방법을 사용해보십시오. 우리는 현재 가능한 한 빨리 해결하려고 시도에 우리의 은행 파트너와 통신하고이 상태가 가능한 한 빨리 업데이트 될 것입니다.

3. 2026년 9월 3일 PM 6:17 UTCinvestigating

   UPDATE: 우리는 Fuego 활동에 영향을 미치는 문제의 인식입니다. 수입된 임금 접근 (EWA) 끌기, 팁 지급 (TPO) 및 Fuego 카드에서 지불 카드로 전송은 현재 사용할 수 없습니다. 은행 계좌로 송금하고 다른 거래 유형은 현재 공개되지 않습니다. 우리는 현재 가능한 한 빨리 해결하려고 시도에 우리의 은행 파트너와 통신하고이 상태가 가능한 한 빨리 업데이트 될 것입니다.

4. 2026년 9월 3일 PM 6:36 UTCinvestigating

   UPDATE: 우리는 Fuego 활동에 영향을 미치는 문제의 인식입니다. 수입된 임금 접근 (EWA)는 Fuego 카드에서 지불 카드에 지불하고 이동은 현재 사용할 수 없습니다. 은행 계좌로 송금하고 다른 거래 유형은 현재 공개되지 않습니다. 우리는 현재 가능한 한 빨리 해결하려고 시도에 우리의 은행 파트너와 통신하고이 상태가 가능한 한 빨리 업데이트 될 것입니다.

5. 2026년 9월 3일 PM 6:49 UTCinvestigating

   UPDATE: 우리는 Fuego 활동에 영향을 미치는 문제의 인식입니다. 수입된 임금 접근 (EWA) 끌기, 끝 지불금 (TPO) 및 Fuego 카드에서 지불 카드에 이동은 영향을 미칠지도 모릅니다. 은행 계좌로 송금하고 다른 거래 유형은 현재 공개되지 않습니다. 우리는 현재 가능한 한 빨리 해결하려고 시도에 우리의 은행 파트너와 통신하고이 상태가 가능한 한 빨리 업데이트 될 것입니다.

6. 2026년 9월 4일 AM 6:51 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 21일 PM 3:42 UTCinvestigating

   우리는 우리의 고객의 일부에 영향을 미칠 수있는 중요한 사건의 인식입니다. 이 사건은 현재 문제의 뿌리 원인을 결정하기 위해 조사됩니다. 상태 및 업데이트는 사건이 해결 될 때까지 30 분마다 계속됩니다. 우리는 당신의 서비스에 이 붕괴를 위해 사과합니다.

2. 2026년 8월 21일 PM 4:15 UTCmonitoring

   우리는 복구 표지판을 관찰하고 상황을 밀접하게 감시하고 있습니다. 더 업데이트는 문제가 완전히 해결되면 게시됩니다. 우리는 당신의 서비스에 어떤 혼란든지를 위해 apologise.

3. 2026년 8월 21일 PM 5:06 UTCresolved

   우리는 문제가 해결되고 고객이 People System에 로그인 할 수 있다고 확신합니다. 우리는 당신의 서비스에 이 붕괴를 위해 사과합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 13일 PM 1:21 UTCinvestigating

   우리는 우리의 고객의 일부에 영향을 미칠 수있는 중요한 사건의 인식입니다. 이 사건은 현재 문제의 뿌리 원인을 결정하기 위해 조사됩니다. 상태 및 업데이트는 사건이 해결 될 때까지 30 분마다 계속됩니다. 우리는 당신의 서비스에 이 붕괴를 위해 사과합니다.

2. 2026년 8월 13일 PM 1:51 UTCinvestigating

   우리는 복구 및 고객의 초기 징후를 볼 시작은 이제 시스템에 액세스 할 수 있습니다. 우리는 더 많은 업데이트를 제공 할 것입니다. 상태 및 업데이트는 사건이 해결 될 때까지 30 분마다 계속됩니다. 우리는 당신의 서비스에 이 붕괴를 위해 사과합니다.

3. 2026년 8월 13일 PM 2:06 UTCmonitoring

   우리는 문제가 해결되고 고객이 Inventory에 로그인 할 수 있다고 생각합니다. 다음 업데이트는 해상도 확인시 제공됩니다. 우리는 당신의 서비스에 이 붕괴를 위해 사과합니다.

4. 2026년 8월 16일 PM 6:25 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 28일 PM 4:58 UTCinvestigating

   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. 2026년 5월 28일 PM 5:31 UTCinvestigating

   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. 2026년 5월 28일 PM 5:57 UTCinvestigating

   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. 2026년 5월 28일 PM 6:31 UTCmonitoring

   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. 2026년 6월 5일 AM 11:43 UTCresolved

   This incident has been resolved.

1. 2026년 5월 7일 AM 7:44 UTCinvestigating

   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. 2026년 5월 7일 AM 9:15 UTCidentified

   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. 2026년 5월 7일 AM 10:18 UTCidentified

   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.

4. 2026년 5월 7일 AM 10:44 UTCidentified

   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.

5. 2026년 5월 7일 PM 1:49 UTCidentified

   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.

6. 2026년 5월 7일 PM 2:25 UTCmonitoring

   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.

7. 2026년 5월 11일 PM 1:34 UTCresolved

   This incident has been resolved.

1. 2026년 4월 15일 AM 9:43 UTCidentified

   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. 2026년 4월 15일 AM 10:00 UTCmonitoring

   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. 2026년 4월 16일 AM 11:43 UTCresolved

   This incident has been resolved.

1. 2026년 3월 6일 PM 9:11 UTCmonitoring

   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. 2026년 8월 13일 PM 2:30 UTCresolved

   This incident has been resolved.

1. 2025년 11월 13일 PM 12:14 UTCinvestigating

   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. 2025년 11월 13일 PM 12:22 UTCmonitoring

   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. 2025년 11월 14일 AM 10:46 UTCresolved

   This incident has been resolved.

1. 2025년 10월 29일 PM 4:10 UTCinvestigating

   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. 2025년 10월 29일 PM 4:14 UTCinvestigating

   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. 2025년 10월 29일 PM 4:32 UTCinvestigating

   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. 2025년 10월 29일 PM 4:41 UTCinvestigating

   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. 2025년 10월 29일 PM 5:04 UTCinvestigating

   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. 2025년 10월 29일 PM 5:22 UTCinvestigating

   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. 2025년 10월 29일 PM 5:51 UTCinvestigating

   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. 2025년 10월 29일 PM 7:19 UTCinvestigating

   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. 2025년 10월 29일 PM 8:58 UTCidentified

   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. 2025년 10월 29일 PM 10:48 UTCmonitoring

    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. 2025년 10월 30일 AM 9:00 UTCresolved

    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.

1. 2025년 10월 25일 AM 6:37 UTCmonitoring

   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. 2025년 10월 27일 AM 9:45 UTCmonitoring

   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. 2025년 10월 31일 PM 5:32 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 AM 9:19 UTCinvestigating

   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. 2025년 10월 20일 AM 9:44 UTCinvestigating

   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. 2025년 10월 20일 AM 10:07 UTCinvestigating

   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. 2025년 10월 20일 AM 10:43 UTCinvestigating

   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. 2025년 10월 20일 AM 11:11 UTCmonitoring

   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. 2025년 10월 21일 AM 8:04 UTCresolved

   This incident has been resolved.

1. 2025년 10월 9일 AM 9:27 UTCinvestigating

   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. 2025년 10월 9일 AM 9:50 UTCinvestigating

   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. 2025년 10월 9일 AM 10:02 UTCinvestigating

   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. 2025년 10월 9일 AM 10:08 UTCinvestigating

   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. 2025년 10월 9일 AM 10:34 UTCinvestigating

   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. 2025년 10월 9일 AM 11:35 UTCidentified

   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. 2025년 10월 9일 PM 12:03 UTCmonitoring

   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.

8. 2025년 10월 10일 AM 9:04 UTCresolved

   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.

1. 2025년 9월 11일 PM 12:59 UTCmonitoring

   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. 2025년 9월 11일 PM 3:50 UTCmonitoring

   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. 2025년 9월 30일 AM 8:00 UTCresolved

   This incident has been resolved.

1. 2025년 5월 21일 AM 9:04 UTCinvestigating

   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. 2025년 5월 21일 AM 10:05 UTCidentified

   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. 2025년 5월 21일 AM 11:22 UTCinvestigating

   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.

4. 2025년 5월 21일 PM 1:02 UTCmonitoring

   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. 2025년 5월 22일 AM 8:56 UTCresolved

   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.

1. 2025년 5월 11일 PM 5:53 UTCinvestigating

   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. 2025년 5월 11일 PM 6:45 UTCinvestigating

   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. 2025년 5월 11일 PM 7:20 UTCmonitoring

   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.

4. 2025년 5월 12일 AM 6:30 UTCidentified

   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. 2025년 5월 12일 AM 10:01 UTCidentified

   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.

6. 2025년 5월 12일 AM 10:38 UTCmonitoring

   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.

7. 2025년 5월 12일 PM 4:06 UTCresolved

   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.

1. 2025년 1월 2일 PM 5:27 UTCinvestigating

   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. 2025년 1월 3일 AM 9:38 UTCmonitoring

   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. 2025년 1월 7일 AM 9:20 UTCresolved

   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.

1. 2024년 11월 15일 AM 10:16 UTCinvestigating

   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. 2024년 11월 15일 AM 10:53 UTCidentified

   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. 2024년 11월 15일 PM 12:28 UTCmonitoring

   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. 2024년 11월 15일 PM 5:42 UTCresolved

   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.

1. 2024년 11월 13일 AM 1:01 UTCinvestigating

   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. 2024년 11월 13일 AM 1:17 UTCidentified

   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. 2024년 11월 13일 AM 1:19 UTCidentified

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

4. 2024년 11월 13일 AM 1:30 UTCmonitoring

   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. 2024년 11월 13일 AM 1:45 UTCresolved

   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.

1. 2024년 10월 28일 AM 10:46 UTCinvestigating

   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. 2024년 10월 28일 AM 11:49 UTCidentified

   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. 2024년 10월 28일 PM 12:14 UTCidentified

   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.

4. 2024년 10월 28일 PM 12:35 UTCmonitoring

   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. 2024년 10월 30일 AM 11:17 UTCresolved

   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.