История сбоев Fourth

1. 4 сентября 2026 г. в 12:37 UTCinvestigating

   Мы знаем о проблеме, которая влияет на нашу способность отправлять электронные письма. Начиная примерно с 08:00 UTC, Microsoft начала испытывать инцидент, вызвавший увеличение объема отложенных электронных писем во всех регионах M365. Затронутые ответы возвращают "451 4.7.500 Сервер занят". Наши команды активно следят за ситуацией. Никакие другие поставщики электронной почты в настоящее время не затронуты. Пожалуйста, смотрите также https://downdetector.co.uk/status/outlook/ Пожалуйста, обратите внимание: Это может повлиять и не ограничивается Заказы Доклады Обновления сотрудников Сброс пароля. Мы настоятельно рекомендуем клиентам рассмотреть возможность использования своих процедур DISASTER RECOVERY для своих наиболее важных функций, и если вам необходимо обеспечить получение заказов, рекомендуется связаться по телефону. Более подробная информация будет предоставлена по мере ее поступления.

2. 4 сентября 2026 г. в 12:38 UTCidentified

   Мы знаем о проблеме, которая влияет на нашу способность отправлять электронные письма. Начиная примерно с 08:00 UTC, Microsoft начала испытывать инцидент, вызвавший увеличение объема отложенных электронных писем во всех регионах M365. Затронутые ответы возвращают "451 4.7.500 Сервер занят". Наши команды активно следят за ситуацией. Никакие другие поставщики электронной почты в настоящее время не затронуты. Пожалуйста, смотрите также https://downdetector.co.uk/status/outlook/ Пожалуйста, обратите внимание: Это может повлиять и не ограничивается Заказы Доклады Обновления сотрудников Сброс пароля. Мы настоятельно рекомендуем клиентам рассмотреть возможность использования своих процедур DISASTER RECOVERY для своих наиболее важных функций, и если вам необходимо обеспечить получение заказов, рекомендуется связаться по телефону. Более подробная информация будет предоставлена по мере ее поступления.

3. 4 сентября 2026 г. в 13:01 UTCidentified

   Мы знаем о проблеме, которая влияет на нашу способность доставлять электронные письма клиентам, которые используют outlook.com / outlook365.com в качестве своего почтового провайдера. Начиная примерно с 08:00 UTC, Microsoft начала испытывать инцидент, вызвавший увеличение объема отложенных электронных писем во всех регионах M365. Затронутые ответы возвращают "451 4.7.500 Сервер занят". Наши команды активно следят за ситуацией. Никакие другие поставщики электронной почты в настоящее время не затронуты. Пожалуйста, смотрите также https://downdetector.co.uk/status/outlook/ Пожалуйста, обратите внимание: Это может повлиять и не ограничивается Заказы Доклады Обновления сотрудников Сброс пароля. Мы настоятельно рекомендуем клиентам рассмотреть возможность использования своих процедур DISASTER RECOVERY для своих наиболее важных функций, и если вам необходимо обеспечить получение заказов, рекомендуется связаться по телефону. Более подробная информация будет предоставлена по мере ее поступления.

4. 4 сентября 2026 г. в 13:58 UTCidentified

   Мы видим постепенное улучшение ситуации, начинают появляться электронные письма. Пожалуйста, обратите внимание, что потребуется некоторое время для обработки сообщений, и мы не получили официального уведомления о разрешении на этом этапе. Дальнейшие обновления будут предоставляться по мере их поступления.

5. 4 сентября 2026 г. в 16:25 UTCresolved

   Microsoft через X заявила 12 минут назад: "Мы применили меры по смягчению последствий и подтвердили решение проблемы после продолжительного периода мониторинга. Дополнительная информация предоставляется в соответствии с EX1467029 в административном центре". Дальнейших обновлений не будет.

Автоматический перевод официального обновления инцидента.

1. 3 сентября 2026 г. в 17:22 UTCinvestigating

   Мы знаем о проблеме, затрагивающей деятельность Fuego и Mastercards. Доступ к заработанной заработной плате (EWA), выплаты чаевых (TPO) и переводы с карты Fuego могут быть затронуты. Если у вас возникли какие-либо проблемы, попробуйте использовать альтернативный способ оплаты за этот вид деятельности. В настоящее время мы общаемся с нашим банковским партнером в попытке решить эту проблему как можно быстрее и будем обновлять этот статус, как только появится дополнительная информация.

2. 3 сентября 2026 г. в 17:24 UTCinvestigating

   Мы знаем о проблеме, затрагивающей деятельность Fuego и Mastercards. Доступ к заработанной заработной плате (EWA), выплаты чаевых (TPO) и переводы в MasterCard могут быть затронуты. Если у вас возникли какие-либо проблемы, попробуйте использовать альтернативный способ оплаты за этот вид деятельности. В настоящее время мы общаемся с нашим банковским партнером в попытке решить эту проблему как можно быстрее и будем обновлять этот статус, как только появится дополнительная информация.

3. 3 сентября 2026 г. в 18:17 UTCinvestigating

   Обновление: Нам известно о проблеме, затрагивающей деятельность Fuego. Доступ к заработанной заработной плате (EWA), выплаты чаевых (TPO) и переводы с карты Fuego на платежные карты в настоящее время недоступны. Переводы на банковские счета и другие виды транзакций в настоящее время не затрагиваются. В настоящее время мы общаемся с нашим банковским партнером в попытке решить эту проблему как можно быстрее и будем обновлять этот статус, как только появится дополнительная информация.

4. 3 сентября 2026 г. в 18:36 UTCinvestigating

   Обновление: Нам известно о проблеме, затрагивающей деятельность Fuego. Доступ к заработанной заработной плате (EWA) и переводы с карты Fuego на платежные карты в настоящее время недоступны. Переводы на банковские счета и другие виды транзакций в настоящее время не затрагиваются. В настоящее время мы общаемся с нашим банковским партнером в попытке решить эту проблему как можно быстрее и будем обновлять этот статус, как только появится дополнительная информация.

5. 3 сентября 2026 г. в 18:49 UTCinvestigating

   Обновление: Нам известно о проблеме, затрагивающей деятельность Fuego. Доступ к заработанной заработной плате (EWA), выплаты чаевых (TPO) и переводы с карты Fuego на платежные карты могут быть затронуты. Переводы на банковские счета и другие виды транзакций в настоящее время не затрагиваются. В настоящее время мы общаемся с нашим банковским партнером в попытке решить эту проблему как можно быстрее и будем обновлять этот статус, как только появится дополнительная информация.

6. 4 сентября 2026 г. в 06:51 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 21 августа 2026 г. в 15:42 UTCinvestigating

   Мы знаем о критическом инциденте, который может повлиять на некоторых наших клиентов. Этот инцидент в настоящее время расследуется, чтобы определить первопричину проблемы. Статус и обновления будут продолжаться здесь каждые 30 минут, пока инцидент не будет разрешен. Мы приносим извинения за этот сбой в вашей работе.

2. 21 августа 2026 г. в 16:15 UTCmonitoring

   Мы наблюдаем признаки восстановления и внимательно следим за ситуацией. Дальнейшее обновление будет опубликовано, как только проблема будет полностью решена. Мы приносим извинения за любые нарушения в работе вашего сервиса.

3. 21 августа 2026 г. в 17:06 UTCresolved

   Мы уверены, что проблема решена, и клиенты теперь могут войти в систему. Мы приносим извинения за этот сбой в вашей работе.

Автоматический перевод официального обновления инцидента.

1. 13 августа 2026 г. в 13:21 UTCinvestigating

   Мы знаем о критическом инциденте, который может повлиять на некоторых наших клиентов. Этот инцидент в настоящее время расследуется, чтобы определить первопричину проблемы. Статус и обновления будут продолжаться здесь каждые 30 минут, пока инцидент не будет разрешен. Мы приносим извинения за этот сбой в вашей работе.

2. 13 августа 2026 г. в 13:51 UTCinvestigating

   Мы начинаем видеть ранние признаки восстановления, и клиенты могут получить доступ к системе. Мы предоставим дополнительные обновления по мере их появления. Статус и обновления будут продолжаться здесь каждые 30 минут, пока инцидент не будет разрешен. Мы приносим извинения за этот сбой в вашей работе.

3. 13 августа 2026 г. в 14:06 UTCmonitoring

   Мы считаем, что проблема решена, и клиенты теперь могут войти в систему. Следующее обновление будет представлено после подтверждения резолюции. Мы приносим извинения за этот сбой в вашей работе.

4. 16 августа 2026 г. в 18:25 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 28 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 июня 2026 г. в 11:43 UTCresolved

   This incident has been resolved.

1. 7 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 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 мая 2026 г. в 13:34 UTCresolved

   This incident has been resolved.

1. 15 апреля 2026 г. в 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 апреля 2026 г. в 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 апреля 2026 г. в 11:43 UTCresolved

   This incident has been resolved.

1. 6 марта 2026 г. в 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 августа 2026 г. в 14:30 UTCresolved

   This incident has been resolved.

1. 13 ноября 2025 г. в 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 ноября 2025 г. в 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 ноября 2025 г. в 10:46 UTCresolved

   This incident has been resolved.

1. 29 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 17:32 UTCresolved

   This incident has been resolved.

1. 20 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 08:04 UTCresolved

   This incident has been resolved.

1. 9 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 сентября 2025 г. в 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 сентября 2025 г. в 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 сентября 2025 г. в 08:00 UTCresolved

   This incident has been resolved.

1. 21 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 мая 2025 г. в 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 января 2025 г. в 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 января 2025 г. в 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 января 2025 г. в 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 ноября 2024 г. в 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 ноября 2024 г. в 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 ноября 2024 г. в 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 ноября 2024 г. в 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 ноября 2024 г. в 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 ноября 2024 г. в 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 ноября 2024 г. в 01:19 UTCidentified

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

4. 13 ноября 2024 г. в 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 ноября 2024 г. в 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 октября 2024 г. в 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 октября 2024 г. в 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 октября 2024 г. в 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 октября 2024 г. в 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 октября 2024 г. в 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.