51 Simply Hosting undefined Servers incidents · 2017年5月 — official updates, affected components, duration and resolution details.
英国からアイルランドのリンクまで、現在ダウンしています。 冗長パスは、影響が期待されていないため、期待どおりに機能していますが、この時点でネットワークはリスクで考慮すべきです。 弊社では、配送業者様とお取引をお待ちしています.
当社のキャリアは、問題を確認し、解決するために働いています.
公式のインシデント更新を自動翻訳しています。
10月20日、CVE-2026-109618とCVE-2026-109619の2つの重要なPHP脆弱性が発表されました。 これらの脆弱性は 9.2 の CVSS スコアを持ち、認証を要求することなく、サーバー上でコードをリモートで実行する可能性がある。 脆弱性は、PHP 5 から始まるすべての PHP バージョンに影響を与える可能性があります。 ベアメタル、専用サーバー、VPS で PHP を使用する場合は、利用可能なパッチで PHP を更新することを強くお勧めします。 cPanel/Plesk を実行している場合は、パッチも使用可能で、それらを適用する必要があります。 弊社からこれらの製品を実行しているサイト/s をお持ちの場合は、お使いの PHP の使用状況と、お客様やお客様のご利用者様が使用しているバージョンを調べて、関連する操作を取ることをお勧めします。 サーバ/ vps を管理している場合は、これらは、当社のチームにパッチを当てたものです.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
10月20日、CVE-2026-109618とCVE-2026-109619の2つの重要なPHP脆弱性が発表されました。 これらの脆弱性は 9.2 の CVSS スコアを持ち、認証を要求することなく、サーバー上でコードをリモートで実行する可能性がある。 脆弱性は、PHP 5 から始まるすべての PHP バージョンに影響を与える可能性があります。 ベアメタル、専用サーバー、VPS で PHP を使用する場合は、利用可能なパッチで PHP を更新することを強くお勧めします。 cPanel/Plesk を実行している場合は、パッチも使用可能で、それらを適用する必要があります。 弊社からこれらの製品を実行しているサイト/s をお持ちの場合は、お使いの PHP の使用状況と、お客様やお客様のご利用者様が使用しているバージョンを調べて、関連する操作を取ることをお勧めします。 サーバ/ vps を管理している場合は、これらは、当社のチームにパッチを当てたものです.
2026年10月20日、グローバルPHPセキュリティチームは2つの重要なセキュリティ脆弱性を発表しました。 正式なセキュリティアップデートが翌日リリースされました。 世界中の何百万人ものウェブサイトが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.
