Cronologia delle interruzioni di Fourth

1. 4 settembre 2026 alle ore 12:37 UTCinvestigating

   Siamo consapevoli di un problema che sta influenzando la nostra capacità di inviare e-mail. A partire dalle 08:00 UTC, Microsoft ha iniziato a sperimentare un incidente causando un aumento del volume di e-mail differite in tutte le regioni M365. Le risposte interessate stanno ritornando "451 4.7.500 Server occupato". I nostri team stanno monitorando attivamente la situazione. Nessun altro provider di posta elettronica sono attualmente interessati. Si prega di vedere anche https://downdetector.co.uk/status/outlook/ ATTENZIONE: Questo potrebbe influenzare e non è limitato Ordini Relazioni Aggiornamenti dei dipendenti Reimposta la password. Suggeriamo vivamente che i clienti considerino invocare i loro PROCEDURE DISASTER RECOVERY per le loro funzioni più importanti e se è necessario garantire gli ordini sono ricevuti, il contatto telefonico è raccomandato. Ulteriori informazioni saranno fornite come diventa disponibile.

2. 4 settembre 2026 alle ore 12:38 UTCidentified

   Siamo consapevoli di un problema che sta influenzando la nostra capacità di inviare e-mail. A partire dalle 08:00 UTC, Microsoft ha iniziato a sperimentare un incidente causando un aumento del volume di e-mail differite in tutte le regioni M365. Le risposte interessate stanno ritornando "451 4.7.500 Server occupato". I nostri team stanno monitorando attivamente la situazione. Nessun altro provider di posta elettronica sono attualmente interessati. Si prega di vedere anche https://downdetector.co.uk/status/outlook/ ATTENZIONE: Questo potrebbe influenzare e non è limitato Ordini Relazioni Aggiornamenti dei dipendenti Reimposta la password. Suggeriamo vivamente che i clienti considerino invocare i loro PROCEDURE DISASTER RECOVERY per le loro funzioni più importanti e se è necessario garantire gli ordini sono ricevuti, il contatto telefonico è raccomandato. Ulteriori informazioni saranno fornite come diventa disponibile.

3. 4 settembre 2026 alle ore 13:01 UTCidentified

   Siamo consapevoli di un problema che sta influenzando la nostra capacità di fornire e-mail ai clienti che utilizzano Outlook.com / Outlook365.com come loro fornitore di posta. A partire dalle 08:00 UTC, Microsoft ha iniziato a sperimentare un incidente causando un aumento del volume di e-mail differite in tutte le regioni M365. Le risposte interessate stanno ritornando "451 4.7.500 Server occupato". I nostri team stanno monitorando attivamente la situazione. Nessun altro provider di posta elettronica sono attualmente interessati. Si prega di vedere anche https://downdetector.co.uk/status/outlook/ ATTENZIONE: Questo potrebbe influenzare e non è limitato Ordini Relazioni Aggiornamenti dei dipendenti Reimposta la password. Suggeriamo vivamente che i clienti considerino invocare i loro PROCEDURE DISASTER RECOVERY per le loro funzioni più importanti e se è necessario garantire gli ordini sono ricevuti, il contatto telefonico è raccomandato. Ulteriori informazioni saranno fornite come diventa disponibile.

4. 4 settembre 2026 alle ore 13:58 UTCidentified

   Stiamo iniziando a vedere un progressivo miglioramento della situazione e le e-mail stanno cominciando a comparire. Si prega di notare, ci vorrà del tempo per il backlog dei messaggi da elaborare e non abbiamo ricevuto alcuna notifica formale di risoluzione in questa fase. Ulteriori aggiornamenti saranno forniti come diventano disponibili.

5. 4 settembre 2026 alle ore 16:25 UTCresolved

   Microsoft, via X, ha dichiarato 12 minuti fa, "Abbiamo applicato le mitigazioni e confermato il problema risolto dopo un lungo periodo di monitoraggio. Ulteriori informazioni sono fornite sotto EX1467029 nel centro di amministrazione" Non verranno forniti ulteriori aggiornamenti.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 3 settembre 2026 alle ore 17:22 UTCinvestigating

   Siamo consapevoli di un problema che riguarda l'attività di Fuego e Mastercards. L'accesso al salario accumulato (EWA) estrae, i pagamenti di punta (TPO) e i trasferimenti dalla scheda Fuego potrebbero essere influenzati. Se si verificano problemi si prega di provare a utilizzare un metodo alternativo di pagamento per questo tipo di attività. Siamo attualmente in comunicazione con il nostro partner bancario nel tentativo di risolvere questo problema il più rapidamente possibile e conserveremo questo stato aggiornato non appena ci sono più informazioni disponibili.

2. 3 settembre 2026 alle ore 17:24 UTCinvestigating

   Siamo consapevoli di un problema che riguarda l'attività di Fuego e Mastercards. L'accesso al salario accumulato (EWA) estrae, pagamenti di punta (TPO) e trasferimenti a MasterCard potrebbero essere influenzati. Se si verificano problemi si prega di provare a utilizzare un metodo alternativo di pagamento per questo tipo di attività. Siamo attualmente in comunicazione con il nostro partner bancario nel tentativo di risolvere questo problema il più rapidamente possibile e conserveremo questo stato aggiornato non appena ci sono più informazioni disponibili.

3. 3 settembre 2026 alle ore 18:17 UTCinvestigating

   UPDATE: Siamo consapevoli di un problema che riguarda l'attività di Fuego. L'accesso al salario accumulato (EWA) estrae, i pagamenti di punta (TPO) e i trasferimenti dalla Carta di Fuego a carte di pagamento non sono attualmente disponibili. I trasferimenti a conti bancari e altri tipi di transazioni sono attualmente inalterati. Siamo attualmente in comunicazione con il nostro partner bancario nel tentativo di risolvere questo problema il più rapidamente possibile e conserveremo questo stato aggiornato non appena ci sono più informazioni disponibili.

4. 3 settembre 2026 alle ore 18:36 UTCinvestigating

   UPDATE: Siamo consapevoli di un problema che riguarda l'attività di Fuego. Attualmente non sono disponibili estrazioni e trasferimenti dalla Carta di Fuego a carte di pagamento. I trasferimenti a conti bancari e altri tipi di transazioni sono attualmente inalterati. Siamo attualmente in comunicazione con il nostro partner bancario nel tentativo di risolvere questo problema il più rapidamente possibile e conserveremo questo stato aggiornato non appena ci sono più informazioni disponibili.

5. 3 settembre 2026 alle ore 18:49 UTCinvestigating

   UPDATE: Siamo consapevoli di un problema che riguarda l'attività di Fuego. L'accesso al salario accumulato (EWA) estrae, i pagamenti di punta (TPO) e i trasferimenti dalla Carta di Fuego a carte di pagamento possono essere colpiti. I trasferimenti a conti bancari e altri tipi di transazioni sono attualmente inalterati. Siamo attualmente in comunicazione con il nostro partner bancario nel tentativo di risolvere questo problema il più rapidamente possibile e conserveremo questo stato aggiornato non appena ci sono più informazioni disponibili.

6. 4 settembre 2026 alle ore 06:51 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 21 agosto 2026 alle ore 15:42 UTCinvestigating

   Siamo consapevoli di un incidente critico che potrebbe interessare alcuni dei nostri clienti. Questo incidente è attualmente in corso di indagine per determinare la causa principale del problema. Stato e aggiornamenti continueranno qui ogni 30 minuti fino a quando l'incidente non sarà risolto. Ci scusiamo per questo disturbo al vostro servizio.

2. 21 agosto 2026 alle ore 16:15 UTCmonitoring

   Stiamo osservando segni di recupero e stiamo monitorando la situazione da vicino. Un ulteriore aggiornamento sarà pubblicato una volta che il problema è completamente risolto. Ci scusiamo per qualsiasi disturbo al vostro servizio.

3. 21 agosto 2026 alle ore 17:06 UTCresolved

   Siamo sicuri che il problema è stato risolto e i clienti sono ora in grado di accedere a People System. Ci scusiamo per questo disturbo al vostro servizio.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 agosto 2026 alle ore 13:21 UTCinvestigating

   Siamo consapevoli di un incidente critico che potrebbe interessare alcuni dei nostri clienti. Questo incidente è attualmente in corso di indagine per determinare la causa principale del problema. Stato e aggiornamenti continueranno qui ogni 30 minuti fino a quando l'incidente non sarà risolto. Ci scusiamo per questo disturbo al vostro servizio.

2. 13 agosto 2026 alle ore 13:51 UTCinvestigating

   Stiamo iniziando a vedere i primi segni di recupero e i clienti possono essere in grado di accedere ora al sistema. Forniremo ulteriori aggiornamenti mentre diventano disponibili. Stato e aggiornamenti continueranno qui ogni 30 minuti fino a quando l'incidente non sarà risolto. Ci scusiamo per questo disturbo al vostro servizio.

3. 13 agosto 2026 alle ore 14:06 UTCmonitoring

   Crediamo che il problema sia stato risolto e i clienti sono ora in grado di accedere a Inventory. Il prossimo aggiornamento sarà fornito alla conferma della risoluzione. Ci scusiamo per questo disturbo al vostro servizio.

4. 16 agosto 2026 alle ore 18:25 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 giugno 2026 alle ore 11:43 UTCresolved

   This incident has been resolved.

1. 7 maggio 2026 alle ore 07: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 maggio 2026 alle ore 09: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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 13:34 UTCresolved

   This incident has been resolved.

1. 15 aprile 2026 alle ore 09: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 aprile 2026 alle ore 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 aprile 2026 alle ore 11:43 UTCresolved

   This incident has been resolved.

1. 6 marzo 2026 alle ore 21: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. 13 agosto 2026 alle ore 14:30 UTCresolved

   This incident has been resolved.

1. 13 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 10:46 UTCresolved

   This incident has been resolved.

1. 29 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 09: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 ottobre 2025 alle ore 06: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 ottobre 2025 alle ore 09: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 ottobre 2025 alle ore 17:32 UTCresolved

   This incident has been resolved.

1. 20 ottobre 2025 alle ore 09: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 ottobre 2025 alle ore 09: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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 08:04 UTCresolved

   This incident has been resolved.

1. 9 ottobre 2025 alle ore 09: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 ottobre 2025 alle ore 09: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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 09: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 settembre 2025 alle ore 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 settembre 2025 alle ore 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 settembre 2025 alle ore 08:00 UTCresolved

   This incident has been resolved.

1. 21 maggio 2025 alle ore 09: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 maggio 2025 alle ore 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 maggio 2025 alle ore 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 maggio 2025 alle ore 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 maggio 2025 alle ore 08: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 maggio 2025 alle ore 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 maggio 2025 alle ore 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 maggio 2025 alle ore 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 maggio 2025 alle ore 06: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 maggio 2025 alle ore 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 maggio 2025 alle ore 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 maggio 2025 alle ore 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 gennaio 2025 alle ore 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 gennaio 2025 alle ore 09: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 gennaio 2025 alle ore 09: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 novembre 2024 alle ore 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 novembre 2024 alle ore 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 novembre 2024 alle ore 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 novembre 2024 alle ore 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 novembre 2024 alle ore 01: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 novembre 2024 alle ore 01: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 novembre 2024 alle ore 01:19 UTCidentified

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

4. 13 novembre 2024 alle ore 01: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 novembre 2024 alle ore 01: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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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 ottobre 2024 alle ore 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.