50 Simply Hosting undefined Servers incidents · 2017年5月 — official updates, affected components, duration and resolution details.
10月20日,宣布了两个关键的PHP脆弱性:CVE-2026-109618和CVE-2026-109619. 这些弱点的CVSS分数为9.2分,可能被用来在服务器上远程执行代码而无需认证. 脆弱性可能影响从PHP 5开始的所有PHP版本. 如果您在您的裸金属, 专用服务器, VPS 上使用 PHP, 我们强烈建议用可用的补丁更新 PHP 。 如果您正在运行 cPanel/ Plesk, 也可以使用补丁, 您应该应用它们 。 如果您有网站运行在这些产品上,我们建议您审查您的PHP用法以及您或您的客户正在使用的版本,并采取相关行动. 如果你和我们一起管理过服务器/Vps, 那么这些已经被我们的团队补齐了.
自动翻译自官方事件更新。
10月20日,宣布了两个关键的PHP脆弱性:CVE-2026-109618和CVE-2026-109619. 这些弱点的CVSS分数为9.2分,可能被用来在服务器上远程执行代码而无需认证. 脆弱性可能影响从PHP 5开始的所有PHP版本. 如果您在您的裸金属, 专用服务器, VPS 上使用 PHP, 我们强烈建议用可用的补丁更新 PHP 。 如果您正在运行 cPanel/ Plesk, 也可以使用补丁, 您应该应用它们 。 如果您有网站运行在这些产品上,我们建议您审查您的PHP用法以及您或您的客户正在使用的版本,并采取相关行动. 如果你和我们一起管理过服务器/Vps, 那么这些已经被我们的团队补齐了.
2026年10月20日,全球PHP安全团队宣布了两个关键的安全弱点. 官方安全更新于次日发布. 由于全球数百万网站都依赖PHP, 正确的是:您网站的安全极为重要。 好消息吗? 我们立即采取行动。 各小组一直在努力解决这一问题,在等待正式软件补丁的同时,尽可能采取缓解措施,并在这些补丁到位后立即推出。 所有可能影响到我们托管和公司平台的系统现已被补齐。 并不是每个网站都在最新的PHP版本上运行. 有的仍然使用更古老的版本,例如因为某些插件或应用程序与较新的PHP发布不相容. 我们的团队走了多一英里, 并调整了安全 修复一些旧的PHP版本。 这个过程叫做回放:改造一个安全补丁,因此它也与更古老的软件版本相配合. 这不仅仅是一个复制文件的问题。 我们的工程师必须手动执行,编译和测试必要的修改. PHP项目目前正式支持8.2至8.5版本. 旧版本不再定期收到安全更新. 不过不用说,如果你在旧版本的PHP上,请更新这个.
自动翻译自官方事件更新。
我们联合王国与爱尔兰的一条联系目前已经中断。 冗余路径正在按预期运行,因此预计不会产生影响,但目前应考虑网络面临风险。 我们有一个案子正在等待更新.
我们联合王国与爱尔兰的一条联系目前已经中断。 冗余路径正在按预期运行,因此预计不会产生影响,但目前应考虑网络面临风险。 我们有一个案子正在等待更新 承运人已经确认这个问题已经解决,我们已经监测并乐于结束危险期.
自动翻译自官方事件更新。
We are currently dealing with a issue on one of our fibre connections. Any services using it have failed over to redundant resources but the network should be considered "At Risk" while this fault is ongoing.
We are currently dealing with a issue on one of our fibre connections. Any services using it have failed over to redundant resources but the network should be considered "At Risk" while this fault is ongoing. The carrier has now identified the issue and is working to carry out the necessary repairs.
The carrier has repaired the service and the normal levels of resilience of the network have resumed. We consider the event cleared, but will continue a period of monitoring.
The carrier has repaired the service and the normal levels of resilience of the network have resumed. We consider the event cleared and are no longer in an at risk state.
Our monitoring has identified a failed network switch in our Reading datacentre rack L20 affecting a small number of dedicated server customers in that rack. The switch is currently under investigation and we expect servers to return online soon. We will post a further update once complete.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our monitoring has identified a failed network switch in our Reading datacentre rack N17 affecting a small number of dedicated server customers in that rack. The switch is currently under replacement and we expect servers to return online soon. We will post a further update once complete.
The switch has now been replaced, and the rack is back online
We will continue to monitor over the next couple of hours
This incident has been resolved.
We are investigating an issue on one link between our Reading Datacentre and London, this link is currently down and therefore the network should be considered at-risk. We are engaging with our upstream supplier to determine a root cause and implement a fix.
Our supplier has identified the root cause and is undertaking remedial work to address the underlying issue. The network remains at risk at this time.
Our supplier has completed the remedial work and confirmed the fix is in place. The network is no longer at risk. We will continue to monitor the link overnight as a precaution.
This incident has been resolved.
We currently have an issue with one of our switches causing some servers to be offline, we are working on getting the issue resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Our monitoring has detected 2 independent issues on circuits to our other European locations. Whilst we still have upstream connectivtiy from that location and resilient connectivity to another core pop datacenter we as such rely on this site at the current time and would consider this an at-risk situation for Network. We are progressing fault tickets with both carriers with the highest priority to restore normal resilience levels.
Both suppliers of different international circuits are mobilising engineers and replacement equipment to their affected locations in the EU with priority.
Both suppliers of different international circuits have repaired their services overnight in the EU. The Network is now operating with normally expected levels of resilience.
Our network teams have identified multiple independent fibre cuts across multiple suppliers that are impacting usual resilience to our IP transit network that feeds our UK hosting services. The network is still available and at full capacity, however we consider this an at-risk situation until these links are recovered by the suppliers and are closely tracking their progress.
All fibres and links are now available as normal and full network resilience has been restored. We will keep under monitoring overnight but are not anticipating any further unplanned works.
All fibres and links are now available as normal and full network resilience has been restored. We will keep under monitoring overnight but are not anticipating any further unplanned works.
At around 1:23am BST we were alerted to an instance of network instability. This was found to be due to a flapping link caused by a hardware failure. We isolated the link in question at approximately 1:57am BST and removed it from service while we arrange hardware replacement. This has reduced the capacity along one of our backbone links however overall resiliency has not been affected. We believe the impact to customers to be minimal however we will continue to monitor the situation and provide updates once we initiate the replacement process.
Faulty hardware has been identified and replaced, and the affected link will be returned to service between 2300 and 0100 tonight.
Faulty hardware has been identified and replaced, and the affected link will be returned to service between 2300 and 0100 tonight.
We have reports from a small numbers of customers with intermittent traffic issues communicating from some Amazon AWS instances to our network. This does not affect all source or destination IP addresses but a small subset of traffic that is not predictable. We are currently investigating and communicating with the supply chain to resolve the problem as quickly as possible.
Update: A solution has been found and we now believe that this has been resolved. We will monitor feedback and the network before fully closing this status. We have reports from a small numbers of customers with intermittent traffic issues communicating from some Amazon AWS instances to our network. This does not affect all source or destination IP addresses but a small subset of traffic that is not predictable. We are currently investigating and communicating with the supply chain to resolve the problem as quickly as possible.
Update: A solution has been found and we now believe that this has been resolved. We will monitor feedback and the network before fully closing this status. We have reports from a small numbers of customers with intermittent traffic issues communicating from some Amazon AWS instances to our network. This does not affect all source or destination IP addresses but a small subset of traffic that is not predictable. We are currently investigating and communicating with the supply chain to resolve the problem as quickly as possible.
We are currently investigating reports of Network packet loss or slow network access to some Simply Hosting services.
An issue was identified with a network device which has now been resolved and normal levels of network service has resumed.
This incident has been resolved.
We are investigating a network issue on a core device that may be affecting traffic from some destinations to some Simply Dedicated Servers.
Mitigating actions have been implemented and appear to have resolved the fault conditions in the affected hardware. We will now closely monitor before marking this issue as resolved.
This incident has been resolved.
We are currently investigating an issue with a linecard in one of our PoP routers. We do not expect this to cause any outages however this should be considered an at risk period as due to the nature of this issue we will need to run at reduced resiliency at times during fault finding and resolution.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of a service issue affecting one of our backbone links between two of our PoP sites. We do not expect any service interruption however this should be considered an at-risk period due to reduced resiliency.
This issue was observed as fixed at around 2:30am, after monitoring for a while and checking for errors, we believe this incident to be resolved.
We are aware of a service issue affecting one of our backbone links that connects our Reading DC to one of our PoP sites. We do not expect any service interruption however this should be considered an at-risk period due to reduced resiliency.
This incident has been resolved.
We are aware of a service issue affecting one of our backbone links that connects our Reading DC to one of our PoP sites. We do not expect any service interruption however this should be considered an at-risk period due to reduced resiliency.
This incident has been resolved.
We are currently experiencing an issue with our phone lines, for any support issues, please raise a ticket on your customer portal or email [email protected]
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to a software error causing forwarding issues, we will be rebooting one of our aggregation routers imminently. The reboot is expected to cause two blips as the secondary router as part of the resilient pair takes over, and then the primary router comes back online and takes back control.
The router in question is now back online and we can confirm the issue is resolved.
