Historial de interrupciones de Fourth

1. 4 de septiembre de 2026 a las 12:37 UTCinvestigating

   Somos conscientes de un problema que está impactando nuestra capacidad de enviar correos electrónicos. A partir de las 08:00 UTC, Microsoft comenzó a experimentar un incidente causando un mayor volumen de correos electrónicos diferidos en todas las regiones de M365. Las respuestas afectadas están volviendo "451 4.7.500 Server ocupado". Nuestros equipos están monitoreando activamente la situación. Ningún otro proveedor de correo electrónico está afectado actualmente. Por favor vea también https://downdetector.co.uk/status/outlook/ Por favor note: Esto podría afectar y no limitarse a Órdenes Informes Actualizaciones de los empleados restablecimiento de contraseña. Sugerimos encarecidamente que los clientes consideren la posibilidad de invocar sus PROCEDIMIENTOS DE RECURSOS DESASTRES para sus funciones más importantes y si necesita asegurarse de recibir pedidos, se recomienda el contacto telefónico. Se proporcionará más información cuando esté disponible.

2. 4 de septiembre de 2026 a las 12:38 UTCidentified

   Somos conscientes de un problema que está impactando nuestra capacidad de enviar correos electrónicos. A partir de las 08:00 UTC, Microsoft comenzó a experimentar un incidente causando un mayor volumen de correos electrónicos diferidos en todas las regiones de M365. Las respuestas afectadas están volviendo "451 4.7.500 Server ocupado". Nuestros equipos están monitoreando activamente la situación. Ningún otro proveedor de correo electrónico está afectado actualmente. Por favor vea también https://downdetector.co.uk/status/outlook/ Por favor note: Esto podría afectar y no limitarse a Órdenes Informes Actualizaciones de los empleados restablecimiento de contraseña. Sugerimos encarecidamente que los clientes consideren la posibilidad de invocar sus PROCEDIMIENTOS DE RECURSOS DESASTRES para sus funciones más importantes y si necesita asegurarse de recibir pedidos, se recomienda el contacto telefónico. Se proporcionará más información cuando esté disponible.

3. 4 de septiembre de 2026 a las 13:01 UTCidentified

   Somos conscientes de un problema que está impactando nuestra capacidad de entregar correos electrónicos a clientes que utilizan Outlook.com / Outlook365.com como su proveedor de correo. A partir de las 08:00 UTC, Microsoft comenzó a experimentar un incidente causando un mayor volumen de correos electrónicos diferidos en todas las regiones de M365. Las respuestas afectadas están volviendo "451 4.7.500 Server ocupado". Nuestros equipos están monitoreando activamente la situación. Ningún otro proveedor de correo electrónico está afectado actualmente. Por favor vea también https://downdetector.co.uk/status/outlook/ Por favor note: Esto podría afectar y no limitarse a Órdenes Informes Actualizaciones de los empleados restablecimiento de contraseña. Sugerimos encarecidamente que los clientes consideren la posibilidad de invocar sus PROCEDIMIENTOS DE RECURSOS DESASTRES para sus funciones más importantes y si necesita asegurarse de recibir pedidos, se recomienda el contacto telefónico. Se proporcionará más información cuando esté disponible.

4. 4 de septiembre de 2026 a las 13:58 UTCidentified

   Estamos empezando a ver una mejora gradual en la situación y los correos electrónicos están empezando a aparecer. Tenga en cuenta que tardará algún tiempo en procesar el atraso de los mensajes y no hemos recibido ninguna notificación formal de resolución en esta etapa. Se proporcionarán más actualizaciones cuando estén disponibles.

5. 4 de septiembre de 2026 a las 16:25 UTCresolved

   Microsoft, via X, declaró hace 12 minutos, "Hemos aplicado las atenuaciones y confirmado el problema resuelto después de un largo período de monitoreo. Más información se proporciona bajo EX1467029 en el centro de administración" No se proporcionarán más actualizaciones.

Traducido automáticamente desde la actualización oficial del incidente.

1. 3 de septiembre de 2026 a las 17:22 UTCinvestigating

   Somos conscientes de un problema que afecta a la actividad Fuego y Mastercards. Los sorteos de acceso salarial (EWA) y las transferencias de la tarjeta de fuego podrían ser impactados. Si usted está experimentando cualquier problema por favor trate de utilizar un método alternativo de pago para este tipo de actividad. Actualmente estamos en comunicación con nuestro socio bancario en un intento de resolver esto lo antes posible y mantendremos este estado actualizado tan pronto como haya más información disponible.

2. 3 de septiembre de 2026 a las 17:24 UTCinvestigating

   Somos conscientes de un problema que afecta a la actividad Fuego y Mastercards. Los sorteos de acceso salarial (EWA), los pagos de propinas (TPO) y las transferencias a MasterCard podrían ser impactados. Si usted está experimentando cualquier problema por favor trate de utilizar un método alternativo de pago para este tipo de actividad. Actualmente estamos en comunicación con nuestro socio bancario en un intento de resolver esto lo antes posible y mantendremos este estado actualizado tan pronto como haya más información disponible.

3. 3 de septiembre de 2026 a las 18:17 UTCinvestigating

   UPDATE: Somos conscientes de un problema que afecta a la actividad Fuego. Los sorteos de acceso salarial (EWA), los pagos de punta (TPO) y las transferencias de la Tarjeta de Fuego a tarjetas de pago son actualmente indisponibles. Actualmente no se afectan las transferencias a cuentas bancarias y otros tipos de transacciones. Actualmente estamos en comunicación con nuestro socio bancario en un intento de resolver esto lo antes posible y mantendremos este estado actualizado tan pronto como haya más información disponible.

4. 3 de septiembre de 2026 a las 18:36 UTCinvestigating

   UPDATE: Somos conscientes de un problema que afecta a la actividad Fuego. Los sorteos y las transferencias de la Tarjeta de Fuego a las tarjetas de pago actualmente no están disponibles. Actualmente no se afectan las transferencias a cuentas bancarias y otros tipos de transacciones. Actualmente estamos en comunicación con nuestro socio bancario en un intento de resolver esto lo antes posible y mantendremos este estado actualizado tan pronto como haya más información disponible.

5. 3 de septiembre de 2026 a las 18:49 UTCinvestigating

   UPDATE: Somos conscientes de un problema que afecta a la actividad Fuego. Los sorteos de acceso salarial (EWA), los pagos de punta (TPO) y las transferencias de la Tarjeta de Fuego a tarjetas de pago pueden verse afectados. Actualmente no se afectan las transferencias a cuentas bancarias y otros tipos de transacciones. Actualmente estamos en comunicación con nuestro socio bancario en un intento de resolver esto lo antes posible y mantendremos este estado actualizado tan pronto como haya más información disponible.

6. 4 de septiembre de 2026 a las 6:51 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de agosto de 2026 a las 15:42 UTCinvestigating

   Somos conscientes de un incidente crítico que puede afectar a algunos de nuestros clientes. This is incident is currently being investigated to determine the root cause of the issue. El estado y las actualizaciones continuarán aquí cada 30 minutos hasta que se haya resuelto el incidente. Nos disculpamos por esta interrupción a su servicio.

2. 21 de agosto de 2026 a las 16:15 UTCmonitoring

   Estamos observando señales de recuperación y estamos monitoreando la situación de cerca. Una nueva actualización se publicará una vez que la cuestión se resuelva completamente. Nos disculpamos por cualquier perturbación a su servicio.

3. 21 de agosto de 2026 a las 17:06 UTCresolved

   Confiamos en que el tema ha sido resuelto y los clientes ahora pueden acceder a People System. Nos disculpamos por esta interrupción a su servicio.

Traducido automáticamente desde la actualización oficial del incidente.

1. 13 de agosto de 2026 a las 13:21 UTCinvestigating

   Somos conscientes de un incidente crítico que puede afectar a algunos de nuestros clientes. This is incident is currently being investigated to determine the root cause of the issue. El estado y las actualizaciones continuarán aquí cada 30 minutos hasta que se haya resuelto el incidente. Nos disculpamos por esta interrupción a su servicio.

2. 13 de agosto de 2026 a las 13:51 UTCinvestigating

   Estamos empezando a ver señales tempranas de recuperación y los clientes pueden acceder ahora al sistema. Proporcionaremos más actualizaciones a medida que estén disponibles. El estado y las actualizaciones continuarán aquí cada 30 minutos hasta que se haya resuelto el incidente. Nos disculpamos por esta interrupción a su servicio.

3. 13 de agosto de 2026 a las 14:06 UTCmonitoring

   Creemos que el problema ha sido resuelto y los clientes ahora son capaces de acceder a Inventory. La próxima actualización se proporcionará una vez confirmada la resolución. Nos disculpamos por esta interrupción a su servicio.

4. 16 de agosto de 2026 a las 18:25 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de mayo de 2026 a las 16: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. 28 de mayo de 2026 a las 17: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. 28 de mayo de 2026 a las 17: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. 28 de mayo de 2026 a las 18: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. 5 de junio de 2026 a las 11:43 UTCresolved

   This incident has been resolved.

1. 7 de mayo de 2026 a las 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. 7 de mayo de 2026 a las 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. 7 de mayo de 2026 a las 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. 7 de mayo de 2026 a las 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. 7 de mayo de 2026 a las 13: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. 7 de mayo de 2026 a las 14: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. 11 de mayo de 2026 a las 13:34 UTCresolved

   This incident has been resolved.

1. 15 de abril de 2026 a las 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. 15 de abril de 2026 a las 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. 16 de abril de 2026 a las 11:43 UTCresolved

   This incident has been resolved.

1. 6 de marzo de 2026 a las 21:11 UTCmonitoring

   El 9 de marzo, Cuarto implementará una actualización al Portal de Éxito al Cliente en alineación con requisitos de seguridad mejorados. Los usuarios deberán iniciar sesión antes de enviar un ticket de soporte. No hay ningún impacto esperado para la disponibilidad de servicios o el rendimiento. El soporte continúa operando normalmente; sólo el requisito de inicio de sesión para enviar un ticket está cambiando. Para más detalles, incluyendo lo que esto significa para su experiencia y cómo crear o acceder a su cuenta de portal, consulte nuestro anuncio aquí: Zendesk Security Update: Inicie sesión ahora requerida para recibir solicitudes de soporte https://help.hotschedules.com/hc/en-us/articles/44077614528909-Zendesk-Security-Update-Sign-In-Now-Required-for-Support-Requests

2. 13 de agosto de 2026 a las 14:30 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 13 de noviembre de 2025 a las 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. 13 de noviembre de 2025 a las 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. 14 de noviembre de 2025 a las 10:46 UTCresolved

   This incident has been resolved.

1. 29 de octubre de 2025 a las 16: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. 29 de octubre de 2025 a las 16: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. 29 de octubre de 2025 a las 16: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. 29 de octubre de 2025 a las 16: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. 29 de octubre de 2025 a las 17: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. 29 de octubre de 2025 a las 17: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. 29 de octubre de 2025 a las 17: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. 29 de octubre de 2025 a las 19: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. 29 de octubre de 2025 a las 20: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. 29 de octubre de 2025 a las 22: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. 30 de octubre de 2025 a las 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. 25 de octubre de 2025 a las 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. 27 de octubre de 2025 a las 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. 31 de octubre de 2025 a las 17:32 UTCresolved

   This incident has been resolved.

1. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 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. 20 de octubre de 2025 a las 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. 21 de octubre de 2025 a las 8:04 UTCresolved

   This incident has been resolved.

1. 9 de octubre de 2025 a las 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. 9 de octubre de 2025 a las 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. 9 de octubre de 2025 a las 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. 9 de octubre de 2025 a las 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. 9 de octubre de 2025 a las 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. 9 de octubre de 2025 a las 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. 9 de octubre de 2025 a las 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. 10 de octubre de 2025 a las 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. 11 de septiembre de 2025 a las 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. 11 de septiembre de 2025 a las 15: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. 30 de septiembre de 2025 a las 8:00 UTCresolved

   This incident has been resolved.

1. 21 de mayo de 2025 a las 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. 21 de mayo de 2025 a las 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. 21 de mayo de 2025 a las 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. 21 de mayo de 2025 a las 13: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. 22 de mayo de 2025 a las 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. 11 de mayo de 2025 a las 17: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. 11 de mayo de 2025 a las 18: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. 11 de mayo de 2025 a las 19: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. 12 de mayo de 2025 a las 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. 12 de mayo de 2025 a las 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. 12 de mayo de 2025 a las 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. 12 de mayo de 2025 a las 16: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. 2 de enero de 2025 a las 17: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. 3 de enero de 2025 a las 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. 7 de enero de 2025 a las 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. 15 de noviembre de 2024 a las 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. 15 de noviembre de 2024 a las 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. 15 de noviembre de 2024 a las 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. 15 de noviembre de 2024 a las 17: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. 13 de noviembre de 2024 a las 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. 13 de noviembre de 2024 a las 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. 13 de noviembre de 2024 a las 1:19 UTCidentified

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

4. 13 de noviembre de 2024 a las 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. 13 de noviembre de 2024 a las 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. 28 de octubre de 2024 a las 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. 28 de octubre de 2024 a las 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. 28 de octubre de 2024 a las 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. 28 de octubre de 2024 a las 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. 30 de octubre de 2024 a las 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.