Fourth 中断历史

1. 2026年9月4日 UTC 12:37investigating

   我们知道一个影响我们发送电子邮件能力的问题。 从协调世界时8:00左右开始,微软开始经历一起事件,导致所有M365地区延期的电子邮件量增加. 受影响反应回"451 4.7.500服务器忙". 我们的小组正在积极监测局势。 目前没有其他电子邮件提供者受到影响 。 请参看 https://downdetector.co.uk/status/outlook/ 页面存档备份,存于互联网档案馆. 请注意: 这可能产生影响,而且不限于: 命令 报告 雇员最新情况 密码重置 。 我们强烈建议,客户考虑为其最重要的职能而援引其信息系统程序,如果需要确保收到订单,则建议电话联系。 将随时提供更多信息.

2. 2026年9月4日 UTC 12:38identified

   我们知道一个影响我们发送电子邮件能力的问题。 从协调世界时8:00左右开始,微软开始经历一起事件,导致所有M365地区延期的电子邮件量增加. 受影响反应回"451 4.7.500服务器忙". 我们的小组正在积极监测局势。 目前没有其他电子邮件提供者受到影响 。 请参看 https://downdetector.co.uk/status/outlook/ 页面存档备份,存于互联网档案馆. 请注意: 这可能产生影响,而且不限于: 命令 报告 雇员最新情况 密码重置 。 我们强烈建议,客户考虑为其最重要的职能而援引其信息系统程序,如果需要确保收到订单,则建议电话联系。 将随时提供更多信息.

3. 2026年9月4日 UTC 13:01identified

   我们意识到,一个影响我们向客户发送电子邮件的能力的问题,这些客户使用Overview.com/Overview365.com作为邮件供应商。 从协调世界时8:00左右开始,微软开始经历一起事件,导致所有M365地区延期的电子邮件量增加. 受影响反应回"451 4.7.500服务器忙". 我们的小组正在积极监测局势。 目前没有其他电子邮件提供者受到影响 。 请参看 https://downdetector.co.uk/status/outlook/ 页面存档备份,存于互联网档案馆. 请注意: 这可能产生影响,而且不限于: 命令 报告 雇员最新情况 密码重置 。 我们强烈建议,客户考虑为其最重要的职能而援引其信息系统程序,如果需要确保收到订单,则建议电话联系。 将随时提供更多信息.

4. 2026年9月4日 UTC 13:58identified

   我们开始看到局势逐步改善,电子邮件也开始出现。 请注意,处理积压的信息需要一段时间,目前我们没有收到正式的解决通知。 进一步的最新情况将随时提供.

5. 2026年9月4日 UTC 16:25resolved

   微软通过X,12分钟前说, "我们应用了缓解措施,确认了这个问题在经过了很长一段时间的监测后得到解决. 更多信息见行政中心EX1467029。 将不提供进一步的最新资料.

自动翻译自官方事件更新。

1. 2026年9月3日 UTC 17:22investigating

   我们知道一个影响佛戈活动和万事达卡的问题。 收入工资的获取(EWA)提取、小费支付(TPO)和火地卡的转账可能受到影响。 如果您遇到任何问题, 请尝试对此类活动使用替代付费方式 。 我们目前正在与我们的银行伙伴进行沟通,以尽快解决这一问题,并将在获得更多信息后立即更新这一状况.

2. 2026年9月3日 UTC 17:24investigating

   我们知道一个影响佛戈活动和万事达卡的问题。 收入工资的获取(EWA)提取、小费支付(TPO)和转至万事达卡可能受到影响。 如果您遇到任何问题, 请尝试对此类活动使用替代付费方式 。 我们目前正在与我们的银行伙伴进行沟通,以尽快解决这一问题,并将在获得更多信息后立即更新这一状况.

3. 2026年9月3日 UTC 18:17investigating

   最新消息:我们意识到一个影响火地行动的问题。 目前,没有收入工资的领取、小费支付和从火地卡转入支付卡。 转入银行账户和其他交易类别的款项目前未受影响。 我们目前正在与我们的银行伙伴进行沟通,以尽快解决这一问题,并将在获得更多信息后立即更新这一状况.

4. 2026年9月3日 UTC 18:36investigating

   最新消息:我们意识到一个影响火地行动的问题。 收入工资的获取(EWA)目前无法从火地卡中提取,也无法从支付卡中转账。 转入银行账户和其他交易类别的款项目前未受影响。 我们目前正在与我们的银行伙伴进行沟通,以尽快解决这一问题,并将在获得更多信息后立即更新这一状况.

5. 2026年9月3日 UTC 18:49investigating

   最新消息:我们意识到一个影响火地行动的问题。 收入工资的获取(EWA)提取,小费支付(TPO)和从"火地卡"转入支付卡可能会受到影响. 转入银行账户和其他交易类别的款项目前未受影响。 我们目前正在与我们的银行伙伴进行沟通,以尽快解决这一问题,并将在获得更多信息后立即更新这一状况.

6. 2026年9月4日 UTC 06:51resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月21日 UTC 15:42investigating

   我们知道,一个可能影响到我们一些客户的重大事件。 目前正在调查这一事件,以确定问题的根源。 现状和最新情况将每30分钟在这里继续,直到事件得到解决。 我们为你的服务中断而道歉.

2. 2026年8月21日 UTC 16:15monitoring

   我们正在观察恢复的迹象并密切监测局势。 一旦问题得到充分解决,将公布进一步的最新情况。 我们为你的服务受到任何干扰而道歉.

3. 2026年8月21日 UTC 17:06resolved

   我们相信这个问题已经解决,客户现在能够登录到People System. 我们为你的服务中断而道歉.

自动翻译自官方事件更新。

1. 2026年8月13日 UTC 13:21investigating

   我们知道,一个可能影响到我们一些客户的重大事件。 目前正在调查这一事件,以确定问题的根源。 现状和最新情况将每30分钟在这里继续,直到事件得到解决。 我们为你的服务中断而道歉.

2. 2026年8月13日 UTC 13:51investigating

   我们开始看到早期恢复的迹象,客户现在可能能够进入该系统。 一旦获得进一步的最新资料,我们将予以提供。 现状和最新情况将每30分钟在这里继续,直到事件得到解决。 我们为你的服务中断而道歉.

3. 2026年8月13日 UTC 14:06monitoring

   我们认为,这个问题已经解决,客户现在能够登录存货。 下一次更新将在决议确认后提供。 我们为你的服务中断而道歉.

4. 2026年8月16日 UTC 18:25resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年5月28日 UTC 16:58investigating

   We are aware of a critical incident that may be affecting some of our customers using our Single Sign On platform. When trying to login, users are met with errors. This will also impact our customer's ability to access connected apps. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2026年5月28日 UTC 17:31investigating

   We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

3. 2026年5月28日 UTC 17:57investigating

   We are exploring multiple avenues of investigation and are seeing signs of recovery We are continuing to work towards identifying the root cause. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

4. 2026年5月28日 UTC 18:31monitoring

   We are confident the issue is no longer present and that customers are now able to login successfully. We are continuing to provide an extended period of monitoring to confirm success. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

5. 2026年6月5日 UTC 11:43resolved

   This incident has been resolved.

1. 2026年5月7日 UTC 07:44investigating

   We are aware of a critical incident that may be affecting some of our customers using Macromatix in the EMEA region. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2026年5月7日 UTC 09:15identified

   We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

3. 2026年5月7日 UTC 10:18identified

   We have been able to identify the cause of this incident and are continuing to work towards finding an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

4. 2026年5月7日 UTC 10:44identified

   We have been able to identify the cause of this incident and are continuing to work towards finding an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. We deeply apologise for this disruption.

5. 2026年5月7日 UTC 13:49identified

   We believe we have isolated the root cause of the issue affecting MX Services in the EMEA region. The issue has been narrowed down to an internal network issue. We are working on restoring services through multiple paths. We will continue to provide updates here every 30 minutes or less until full service has been restored. We deeply apologise for this disruption.

6. 2026年5月7日 UTC 14:25monitoring

   We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

7. 2026年5月11日 UTC 13:34resolved

   This incident has been resolved.

1. 2026年4月15日 UTC 09:43identified

   We understand that customers are experiencing issues raising tickets to us through our Customer Success Portal. The issue has been identified and we are currently working to restore access. Further updates will be provided as the situation progresses. In the meantime, we kindly ask that you contact Fourth using the number most relevant to your query using the link below https://uk.fourth.com/support/customer-support PLEASE NOTE: We also ask that you do not attempt to contact us via email as those methods have been retired and are not monitored, thank you.

2. 2026年4月15日 UTC 10:00monitoring

   UPDATE: We can confirm that a fix has been implemented and the Customer Success Portal is now functioning as expected. Should you continue to experience issues raising tickets via the Customer Success Portal, please call and let us know. We sincerely apologise for the inconvenience this has caused.

3. 2026年4月16日 UTC 11:43resolved

   This incident has been resolved.

1. 2026年3月6日 UTC 21:11monitoring

   On March 9, Fourth will implement an update to the Customer Success Portal in alignment with enhanced security requirements. Users will be required to log in before submitting a support ticket. There is no expected impact to service availability or performance. Support continues to operate normally; only the login requirement for submitting a ticket is changing. For more details — including what this means for your experience and how to create or access your portal account — please see our announcement here: Zendesk Security Update: Sign-in Now Required for Support Requests https://help.hotschedules.com/hc/en-us/articles/44077614528909-Zendesk-Security-Update-Sign-in-Now-Required-for-Support-Requests

2. 2026年8月13日 UTC 14:30resolved

   This incident has been resolved.

1. 2025年11月13日 UTC 12:14investigating

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2025年11月13日 UTC 12:22monitoring

   We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

3. 2025年11月14日 UTC 10:46resolved

   This incident has been resolved.

1. 2025年10月29日 UTC 16:10investigating

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being verified to ascertain impact. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2025年10月29日 UTC 16:14investigating

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being verified to ascertain impact. Status and updates will continue here every 30 minutes until the incident has been resolved.

3. 2025年10月29日 UTC 16:32investigating

   We are aware of a critical incident that may be affecting some of our customers. All indicators currently suggest there is widespread issue with Microsoft services. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

4. 2025年10月29日 UTC 16:41investigating

   UPDATE: Our investigation has confirmed issue experienced to Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status We will provide further information when this becomes available.

5. 2025年10月29日 UTC 17:04investigating

   Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status Microsoft have advised: We are actively assessing failover options of internal services from our AFD infrastructure. Our investigation into the contributing factors and additional recovery workstreams continues. More information will be provided within 60 minutes or sooner. We will provide further information when this becomes available.

6. 2025年10月29日 UTC 17:22investigating

   UPDATE from Microsoft: Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status Microsoft have advised: We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. Fourth are actively exploring options to mitigate this issue and restore services to customers. An update will be provided when we have further information.

7. 2025年10月29日 UTC 17:51investigating

   Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft: https://azure.status.microsoft/en-gb/status Microsoft have advised: We are taking several concurrent actions: Firstly where we are blocking all changes to the AFD services, this includes customer configuration changes as well. At the same time, we are rolling back our AFD configuration to our last known good state. As we rollback we want to ensure that the problematic configuration doesn't re-initiate upon recovery. Customers may have experienced problems accessing the Azure management portal. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly, while all portal extensions are working correctly there may be a small number of endpoints that might have a problem loading (i.e. Marketplace). We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. In addition, Fourth are actively exploring options to mitigate this issue and restore services to customers. An update will be provided when we have further information.

8. 2025年10月29日 UTC 19:19investigating

   Our investigation has confirmed issue experienced by Fourth Services look to be related a Global Azure issue. This has been confirmed by Microsoft. We are seeing intermittent signs of recovery. Fourth are actively exploring options to mitigate this issue and restore services to customers. An update will be provided when we have further information.

9. 2025年10月29日 UTC 20:58identified

   We are able to confirm that we are seeing significant improvements in accessing our solutions, however we do believe that customers may still experience intermittent issues. We will continue to monitor and provide further updates as the situation evolves. A further update will be provided when we have more information.

10. 2025年10月29日 UTC 22:48monitoring

    We have continued to see an improvement across the Fourth suite of products and believe that overall they are in a stable condition. Remedial actions undertaken by Microsoft may still have a small impact, but we firmly believe the situation will improve even further over the next hour. We will continue to monitor throughout the evening and pending any further information, this Incident will be resolved at the start of the day tomorrow. Thank you for your understanding.

11. 2025年10月30日 UTC 09:00resolved

    Hello, We can confirm that our affected solutions have remained stable for the period since the last update. As such we consider this incident as resolved. Thank you.

1. 2025年10月25日 UTC 06:37monitoring

   As part of our ongoing commitment to security, Fourth is implementing a mandatory password reset for users of the Fourth Single Sign-On (SSO) platform. The next time you log in, you’ll be prompted to reset your password. Simply select “Forgot username or password” and follow the instructions to create a new one. This is a planned update — no action is required until your next login.

2. 2025年10月27日 UTC 09:45monitoring

   As part of our ongoing commitment to security, Fourth is implementing a mandatory password reset for users of the Fourth Single Sign-On (SSO) platform. The next time you log in, you will be informed your credentials are incorrect. Simply select “Forgot username or password” and follow the instructions to create a new one. This is a planned update — no action is required until your next login.

3. 2025年10月31日 UTC 17:32resolved

   This incident has been resolved.

1. 2025年10月20日 UTC 09:19investigating

   Dear Customer, There is currently an issue with Amazon Web Services which is affecting a large portion of the internet. As a leading SaaS provider, we are currently working diligently to ascertain real time impact on services we provide. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status

2. 2025年10月20日 UTC 09:44investigating

   Dear Customer, UPDATE FROM AWS: Oct 20 2:27 AM PDT We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth is continuing to investigate real time impact on our valued customers.

3. 2025年10月20日 UTC 10:07investigating

   Dear Customer, UPDATE FROM AWS: Oct 20 3:03 AM PDT We continue to observe recovery across most of the affected AWS Services. We can confirm global services and features that rely on US-EAST-1 have also recovered. We continue to work towards full resolution and will provide updates as we have more information to share. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth is continuing to investigate real time impact on our valued customers.

4. 2025年10月20日 UTC 10:43investigating

   UPDATE FROM AWS: Oct 20 3:35 AM PDT The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution. Additionally, some services are continuing to work through a backlog of events such as Cloudtrail and Lambda. While most operations are recovered, requests to launch new EC2 instances (or services that launch EC2 instances such as ECS) in the US-EAST-1 Region are still experiencing increased error rates. We continue to work toward full resolution. If you are still experiencing an issue resolving the DynamoDB service endpoints in US-EAST-1, we recommend flushing your DNS caches. We will provide an update by 4:15 AM, or sooner if we have additional information to share. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth is continuing to investigate real time impact on our valued customers.

5. 2025年10月20日 UTC 11:11monitoring

   UPDATE FROM AWS: Oct 20 4:08 AM PDT We are continuing to work towards full recovery for EC2 launch errors, which may manifest as an Insufficient Capacity Error. Additionally, we continue to work toward mitigation for elevated polling delays for Lambda, specifically for Lambda Event Source Mappings for SQS. We will provide an update by 5:00 AM PDT. More information will be provided when this becomes available, in the meantime, please visit: https://health.aws.amazon.com/health/status Fourth will continue to monitor and mitigate any impact on our valued customers.

6. 2025年10月21日 UTC 08:04resolved

   This incident has been resolved.

1. 2025年10月9日 UTC 09:27investigating

   Good Morning, We are currently aware that some customers are experiencing intermittent issues when attempting to access their mobile solutions through Single Sign On We are currently working to resolve this issue. The next update will be provided in 30 minutes.

2. 2025年10月9日 UTC 09:50investigating

   We are aware an investigating intermitent issues with accessing Fourth Services via SSO in EMEA. Our Technical team are working with our Cloud Infrastructure partner to determine the root cause and fix. We apologies for the disruption to your service.

3. 2025年10月9日 UTC 10:02investigating

   We are aware of intermitent issues with accessing Fourth Services via SSO in EMEA. Our Cloud Infrastructure partner has confirmed they are experiencing issues with their Content Delivery Network (CDN), which is affecting Fourth and the wider user base. Further updates will be provided, when we get more information. We apologies for the disruption to your service.

4. 2025年10月9日 UTC 10:08investigating

   UPDATE: We can confirm that the issue being experienced lies with Microsoft services as show here: https://azure.status.microsoft/en-gb/status We are continuously monitoring affected services for signs of recovery. Further updates will be provided, when we get more information. We apologies for the disruption to your service.

5. 2025年10月9日 UTC 10:34investigating

   We can confirm that the issue being experienced lies with Microsoft services as show here: https://azure.status.microsoft/en-gb/status We are continuously monitoring affected services for signs of recovery. Further updates will be provided, when we get more information. We apologies for the disruption to your service.

6. 2025年10月9日 UTC 11:35identified

   UPDATE: Microsoft are reporting an improved situation, which should go some way to resolving the issues withing 90 minutes. Fourth are continuing to monitor our services and solutions and will advise when we see an improvement. For Microsoft real-time updates, please see; https://azure.status.microsoft/en-gb/status An update will be provided in the next 30 minutes. We sincerely apologise for the disruption this has caused.

7. 2025年10月9日 UTC 12:03monitoring

   Our testing shows we are able to gain access through Single Sign On and therefore we believe this issue has been resolved. We will continue to monitor https://azure.status.microsoft/en-gb/status And provide further updates if required.

8. 2025年10月10日 UTC 09:04resolved

   Good Morning, After reviewing the below, we are confident the issues experienced by Microsoft have been resolved and all services provided by Fourth are no longer impacted. https://azure.status.microsoft/en-gb/status We apologise for the disruption this has caused.

1. 2025年9月11日 UTC 12:59monitoring

   We are aware of connectivity issues affecting customers in the Middle East region. This is related to a major subsea cable cut in the Red Sea, which is impacting internet traffic across several providers in the area. Some customers may experience slow response times or intermittent access to Fourth solutions. Our infrastructure and services are fully operational — the disruption is due to external internet routing issues outside of our control.

2. 2025年9月11日 UTC 15:50monitoring

   We are aware of connectivity issues affecting customers in the Middle East region. This is related to a major subsea cable cut in the Red Sea, which is impacting internet traffic across several providers in the area. For further information relating to this incident, please see the below article; https://gulfnews.com/technology/red-sea-cable-chaos-why-the-internet-didnt-go-dark-1.500263896 Some customers may experience slow response times or intermittent access to Fourth solutions. Our infrastructure and services are fully operational — the disruption is due to external internet routing issues outside of our control. We will continue to monitor and provide an update when this situation improves.

3. 2025年9月30日 UTC 08:00resolved

   This incident has been resolved.

1. 2025年5月21日 UTC 09:04investigating

   We are aware of a situation where some customers are experiencing delays and timeouts when accessing our mobile apps. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 60 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2025年5月21日 UTC 10:05identified

   We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 60 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

3. 2025年5月21日 UTC 11:22investigating

   We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 60 minutes until the incident has been resolved. We apologise for this disruption to your service.

4. 2025年5月21日 UTC 13:02monitoring

   We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

5. 2025年5月22日 UTC 08:56resolved

   We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage. We greatly apologise for this disruption.

1. 2025年5月11日 UTC 17:53investigating

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2025年5月11日 UTC 18:45investigating

   We are aware of a critical incident that may be affecting some of our customers. We are continuing to investigate to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

3. 2025年5月11日 UTC 19:20monitoring

   We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

4. 2025年5月12日 UTC 06:30identified

   We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

5. 2025年5月12日 UTC 10:01identified

   We have identified the cause of this incident and are working towards an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again, we deeply apologise for this disruption.

6. 2025年5月12日 UTC 10:38monitoring

   We have implemented a fix for this incident, and services are now fully restored. Our teams are continuing to monitor closely to ensure stability. Thank you for your patience and understanding throughout this disruption.

7. 2025年5月12日 UTC 16:06resolved

   We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage however we will aim to post a formal Incident Report here within the next 5 business days. We greatly apologise for this disruption.

1. 2025年1月2日 UTC 17:27investigating

   We are aware that some customers are currently experiencing latency when logging in to Single Sign On and using connected applications. Our teams have been actively working throughout the day to address this issue, and investigations are progressing. Testing confirms that all applications remain operational, though performance may be slower than usual. We apologise for the inconvenience caused and assure you that we are prioritising a swift resolution. Further updates will be provided as soon as we have additional information.

2. 2025年1月3日 UTC 09:38monitoring

   This morning our development team have implemented a fix and the result of this is is an immediate improvement in log in and response times. We are confident that this issue has now been resolved but if you continue to see issues, please let us know. We sincerely apologise for the inconvenience this has caused.

3. 2025年1月7日 UTC 09:20resolved

   We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage however a formal Incident Report will be posted here with the next 5 business days. We greatly apologise for this disruption.

1. 2024年11月15日 UTC 10:16investigating

   Dear Customer, We have been made aware of a critical incident affecting some customers. Salesforce is currently investigating the root cause of the issue. You can find updates at the following link: https://status.salesforce.com/incidents/13457 We apologise for this disruption to your service. The next update will be shared once we have more significant information.

2. 2024年11月15日 UTC 10:53identified

   Salesforce has been able to identify the cause of this incident and is currently working towards finding an appropriate resolution. You can find updates at the following link: https://status.salesforce.com/incidents/13457 We apologise for this disruption to your service. The next update will be shared once we have more significant information.

3. 2024年11月15日 UTC 12:28monitoring

   Salesforce has now implemented a solution and is currently monitoring for completeness. The team is seeing positive results after completing the rollback. Due to the scale of the issue, the rollback is being implemented in stages. Affected customers should notice improved performance as each rollback is completed. We apologise for this disruption to your service.

4. 2024年11月15日 UTC 17:42resolved

   We are confident that the fix applied by Salesforce, along with internal monitoring this afternoon, has resolved the incident. This will conclude the updates to the status page regarding this outage however a formal Incident Report will be posted here within the next 5 business days. We greatly apologise for this disruption.

1. 2024年11月13日 UTC 01:01investigating

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologize for this disruption to your service.

2. 2024年11月13日 UTC 01:17identified

   We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologize for this disruption.

3. 2024年11月13日 UTC 01:19identified

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

4. 2024年11月13日 UTC 01:30monitoring

   We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologize for this disruption to your service.

5. 2024年11月13日 UTC 01:45resolved

   We are confident that our solution has resolved this incident. This will conclude the updates to the status page regarding this outage however a formal Incident Report will be posted here with the next 5 business days. We greatly apologize for this disruption.

1. 2024年10月28日 UTC 10:46investigating

   We are aware of a critical incident that may be affecting some of our customers. This is incident is currently being investigated to determine the root cause of the issue. Status and updates will continue here every 30 minutes until the incident has been resolved. We apologise for this disruption to your service.

2. 2024年10月28日 UTC 11:49identified

   We have been able to identify the cause of this incident and are currently working towards finding an appropriate resolution. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

3. 2024年10月28日 UTC 12:14identified

   UPDATE: Should you continue to experience difficulties accessing through a browser, we can confirm that customers accessing Single Sign On through mobile devices can do so successfully. We will continue to provide updates here every 30 minutes or less until full service has been restored. Again we deeply apologise for this disruption.

4. 2024年10月28日 UTC 12:35monitoring

   We have now implemented a solution and are currently monitoring for completeness. The next update will be provided upon confirmation of resolution. We apologise for this disruption to your service.

5. 2024年10月30日 UTC 11:17resolved

   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.