GitHub 行为影响
Pending
- identified
GitHub 今早通过状态页面报告退化的绩效: https://www.githubstatus.com/ 互联网档案馆的存檔,存档日期2013-12-21. 就页面而言,这个问题可能影响到拉出请求、问题、副驾驶、动作、Webhooks和API请求等服务。 客户应当使用 GitHub 状态页面获取最新信息.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
64 Liquid Web incidents · 2025年11月 — official updates, affected components, duration and resolution details.
GitHub 今早通过状态页面报告退化的绩效: https://www.githubstatus.com/ 互联网档案馆的存檔,存档日期2013-12-21. 就页面而言,这个问题可能影响到拉出请求、问题、副驾驶、动作、Webhooks和API请求等服务。 客户应当使用 GitHub 状态页面获取最新信息.
这一事件已经得到解决.
自动翻译自官方事件更新。
We are currently investigating network issues affecting servers in our Phoenix Data Center. During this time, you may experience connectivity disruptions or degraded performance. Our engineers are actively working to identify the root cause and restore service stability as quickly as possible. If you have any questions or require assistance, please contact us via chat or open a support case through portal.liquidweb.com We appreciate your patience and understanding while we work to resolve this issue. Thank you.
Dear Valued Customer, We are currently responding to a critical facilities issue affecting our Phoenix, Arizona data center. A major chiller equipment failure at the facility has significantly reduced cooling capacity, resulting in elevated temperatures and an increased risk of service disruption and potential hardware impact. The data center provider is actively working to restore normal cooling operations. Replacement work is underway, with current estimates indicating repairs may take 10–16 hours or longer. Additional information regarding the facility incident is available on the data center provider's status page: https://status.phoenixnap.com/incidents/dnjp5pfv2mmh Our teams are closely monitoring conditions and working directly with the data center provider to minimize customer impact. To protect customer infrastructure and reduce the risk of hardware damage or data loss, we may need to perform controlled shutdowns of affected systems if facility temperatures reach unsafe levels. Where necessary, we will prioritize orderly shutdown procedures to protect the underlying infrastructure. Customers with services hosted within the affected Phoenix facility should prepare for potential service interruptions while remediation efforts continue. We understand the seriousness of this situation and the impact an extended disruption may have on your business. We will continue to provide updates as conditions change and additional information becomes available. We sincerely apologize for the disruption and appreciate your patience as we work to protect your infrastructure and restore normal operations. Sincerely, Nexcess Support Team
Dear Valued Customer, Update: Our teams are continuing to work closely with our data center provider at the Phoenix location. Our data center teams and on-site vendors continue working to restore adequate cooling. As part of our ongoing mitigation efforts, we are gracefully shutting down impacted systems where necessary to help protect customer data and reduce the risk of data corruption or hardware-related issues while temperatures remain elevated. We apologize for the disruption and appreciate your patience as we work to protect your infrastructure and restore normal operations. We will continue to provide updates as the situation progresses. Sincerely, Nexcess Support Team
Dear Valued Customer, We are continuing to work closely with our provider as they address the elevated temperatures at the Phoenix facility. Progress is being made, and temperatures are continuing to come down as cooling systems are restored and additional mitigation efforts are put in place. We apologize for the disruption and appreciate your patience as we work to protect your infrastructure and restore normal operations. We will continue to provide updates as the situation progresses. For the latest status and updates from the facility, please visit: https://status.phoenixnap.com/incidents/dnjp5pfv2mmh Sincerely, Nexcess Support Team
Internal ambient temperatures in our Phoenix, Arizona data center have continued to moderate and onsite Nexcess Engineers have begun to restore service to networking equipment and other services. Our Senior Engineering and Leadership teams are actively monitoring the situation and will continue to protect customer infrastructure and reduce the risk of hardware damage or data loss where necessary, however at this time customers should begin to see network service restoring to their environments.
Our Nexcess Engineering teams continue working to restore all remaining systems and services in our Phoenix, Arizona data center. While significant progress has been made and many systems have returned to service, our teams are continuing to bring remaining infrastructure back online in a controlled and careful manner. As systems and network services are restored, our Engineering and Operations teams are monitoring them very closely to confirm they remain stable and continue operating as expected. We are also actively watching environmental conditions and infrastructure health throughout the facility to reduce the risk of additional service disruption, hardware damage, or data loss. Work will continue until all affected systems and services have been fully restored. Our Engineering and Leadership teams remain actively engaged, and we will continue to provide updates as restoration efforts progress and overall service stability is confirmed.
Our Nexcess Engineering teams have successfully brought the majority of systems and services in our Phoenix, Arizona data center back online, and work continues actively to restore the remaining pending services. For all restored systems, our teams are conducting thorough checks across the infrastructure to confirm complete stability and ensure there is no ongoing operational impact. Out of an abundance of caution, we continue to closely monitor facility environmental conditions and overall infrastructure health. We will provide further updates in this space as restoration and verification efforts progress.
Our Nexcess Engineering teams have brought the majority of systems and services in our Phoenix, Arizona data center back online, and work remains actively underway to restore the remaining pending services. Over the past several hours, we have observed continued stability across all restored systems with no red flags identified. Out of an abundance of caution, our teams are continuing to perform ongoing checks and closely monitor facility environmental conditions alongside overall infrastructure health. We will provide further updates in this space as restore and verification efforts progress.
The vast majority of impacted servers have been brought online and are functional at this time. We continue to monitor the stability of the network to ensure normal operations. Our engineers are still working on restoring functionality to the Cloud Sites Platform but are making progress. The root cause has been identified and progress is being made. Updates and more information regarding those efforts can be found on our Cloud Sites Status Page here: https://status.websitesettings.com/incidents/0l8hyyhr6v93
We have restored all services and observed continued stability. We will keep a close eye on the platform and continue to update this page with any new developments.
All post-outage cleanup activities have been completed, and everything is working as expected. We will continue to monitor the environment, and this incident is now resolved.
A security vulnerability, CVE-2026-65640, has been identified in WordPress that could allow an authenticated Author-level or higher user to achieve remote code execution through a malicious file upload on sites using Imagick and Ghostscript. The vulnerability has been addressed through updates across supported WordPress branches. Patched Versions: Customers should update to the following patched version for their respective WordPress branch: 7.0.4 6.9.7 6.8.8 6.7.7 6.6.7 6.5.10 6.4.10 6.3.10 6.2.11 6.1.12 6.0.14 5.9.16 5.8.15 5.7.17 5.6.19 5.5.20 5.4.21 5.3.23 5.2.26 5.1.24 5.0.27 4.9.31 4.8.30 4.7.35 Recommended Action: Customers are strongly encouraged to update WordPress core to the latest available patched version and ensure automatic updates are enabled where appropriate. Customers with automatic updates enabled should receive the applicable update automatically. However, we recommend verifying the currently running WordPress version to ensure the security update has been successfully applied. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please reach us via live chat or via a case. Additional information: https://wordpress.org/news/2026/08/wordpress-7-0-4-release/ https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-8vr3-7mxf-gx8w
A high-severity reflected XSS vulnerability, CVE-2026-64638, has been identified in the WordPress login interface. Exploitation requires a victim to visit a specially crafted URL and, under specific conditions, could potentially lead to PHP code execution. Impacted versions Impacted versions: WordPress 4.7 – 7.0.2 (every release on every branch) WordPress 4.6 and earlier — end of life, no patch available Fixed versions: WordPress 7.0.3 WordPress 6.9.6 WordPress 6.8.7 Equivalent minor releases on every remaining supported branch back to 4.7 Recommended Action Customers are strongly encouraged to update WordPress core and ensure automatic security updates are enabled where appropriate. Since exploitation requires user interaction, customers should also remain vigilant against phishing attempts and avoid clicking suspicious or unsolicited links. Customers with automatic security updates enabled should receive the applicable update automatically; however, we recommend verifying the currently running WordPress version. There is currently no reported evidence of widespread exploitation in the wild. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please contact our Support team.
我们正在调查断断续续的连通性,以及影响在VMware MT环境中托管的一些服务的长期性。 我们的工程师们正在积极努力,找出原因,尽快恢复正常服务. 我们赞赏你在努力解决这一问题时的耐心和理解。 如果您有任何问题或问题,请打开支持票或通过聊天联系我们.
目前服务已恢复,受影响的VMware MT托管服务正常运行. 在我们的团队努力解决这一问题期间,感谢你的耐心和理解.
自动翻译自官方事件更新。
7月17日Wordpress.org宣布了两个被通称为WP2Shell的关键远程代码执行(RCE)漏洞. 这些弱点存在于Wordpress Core中,并允许未经认证的请求在目标网站上执行任意代码. 下面运行Wordpress版本的客户强烈建议尽快升级到最新版本: Wordpress 6.8.x;固定于 6.8.6 WordPress 6.9.x; 固定于 6.9.5 WordPress 7.0.x; 固定于 7. 0.2 WordPress 7.1 β,固定于 7.1 β2 资料来源:https://wordpress.org/news/2026/07/wordpress-7-0-2-release/。 2分钟前寄出. 7月17日, 2026 - 21:44 EDT
我们的小组继续勤奋工作,评估最近披露的WordPress核心脆弱性的影响,并核实适当的缓解措施已经到位。 我们仍然积极参与调查,并正在监测局势,以了解任何新的事态发展。 我们将继续密切监测局势,并采取任何必要的额外步骤来维护系统安全与稳定。 如果您需要援助或有任何担心,请联系我们的支援小组.
服务已恢复,网站目前正在按预期加载。 我们的网络小组正在继续调查根本原因并积极监测环境,以确保稳定。 目前,所有服务似乎都正常运行。 如果您遇到任何问题或需要援助,请联系我们的支援小组.
这一问题已经确定,一个解决办法正在实施之中.
我们正在继续努力解决这个问题。
鉴于这种脆弱性的严重性,液化网络系统工程师一直在积极更新我们整个车队受影响的Wordpress应用程序。 仍大力鼓励客户审查其Wordpress网站,如果受到影响,则尽快更新补丁版.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们凤凰城的一组服务器 AZ数据中心失去电源 我们的现场调查组正在调查.
主要权力已经恢复,我们正在监测局势.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个影响我们服务器上的 Apache 服务的问题。 受影响服务器上的客户可能遇到网站无法使用、HTTP出错或连接超时的情况。 我们的工程组目前正在努力恢复服务。 需要帮忙吗? 与我们聊天或通过我的. liquidweb. 在我们努力恢复正常服务时,我们赞赏你的耐心和理解.
我们的工程小组正在监测受影响的服务器,以确认Apache服务保持稳定.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们的团队目前正在评估Januscape脆弱性(CVE-2026-53359)的影响和范围,及其对我们机队服务器的影响,以及对我们的托管基础设施应用补丁的最佳方式。 在我们努力实施必要的缓解措施时,我们将向任何受影响的客户发送信函。 下一步: 各小组目前正在审查脆弱性;随后将更新有关情况.
我们的小组正在继续在整个受影响的系统中部署必要的安保更新,以应对Januscape的脆弱性(CVE-2026-53359)。 作为这种补救的一部分,有些系统需要有控制的重启来完成补丁过程. 每次重启后,我们正在验证系统的可用性、服务健康和网络连接。 我们的行动小组正在积极调查和恢复没有按预期恢复服务的系统。 我们理解保持可用性的重要性,并正在认真努力完成这一补救工作,同时尽量减少客户的影响。 随着补丁和验证工作的继续进行,将提供更多的更新.
安全更新已在Liquid Web车队中应用.
自动翻译自官方事件更新。
已经提请我们注意,我们小组的一大部分客户在试图登录WHM时看到一个错误信息。 "无效许可证文件。 颁发执照的权力不当". WebPros(小组)意识到这一问题,他们目前正在进行调查。 我们赞赏你耐心地努力解决这一问题.
c 小组一直在努力改进其许可证服务器的性能并进行修改。 我们看到,在没有得到支持的情况下,WHM和CPANEL的准入正在恢复。 如果你仍然有问题,请伸出援手,我们很乐意提供协助.
WebPros表示,这个问题已经解决,服务器应该开始适当续签许可证. 如果你还在经历一些问题.
我们看到局势持续稳定,小组许可证更新工作迄今进展顺利。 如果您需要进一步援助,请毫不犹豫地通过聊天或电子邮件联系我们的支援团队.
自动翻译自官方事件更新。
我们正在调查影响凤凰城数据中心服务器的问题。 你可能会遇到连接问题。 我们的工程师们目前正在调查这个问题,以孤立事业和恢复稳定。 需要帮忙吗? 与我们聊天或创建一个案件 通过我的. liquidweb.com。 在我们努力恢复这项服务时,我们赞赏你的耐心和理解。 谢谢.
我们正在调查一个影响凤凰城数据中心和内部服务之间连通性的问题。 我们确认,这个问题涉及在预定的维护窗口期间与上游供应商的网络连接。 目前,预计客户服务仍可从公共网络获得,我们尚未发现对外部可获取服务的广泛影响。 我们的工程师们正积极与上游供应商合作,尽快恢复全面连接。 需要帮忙吗? 与我们聊天或创建一个案件 通过我的. liquidweb.com。 在我们努力恢复这项服务时,我们赞赏你的耐心和理解。 谢谢.
随着受影响环节开始恢复,我们看到网络连通性不断改善。 所有客户网站和服务器仍可在线访问。 预定的维护工作仍在进行中,我国工程组正在积极监测环境,以确保全面恢复连接。 我们将继续提供补充资料。 需要帮忙吗? 与我们聊天或创建一个案件 通过我的. liquidweb.com。 在我们努力恢复这项服务时,我们赞赏你的耐心和理解。 谢谢.
我们一直在监测局势,一切都保持稳定。 这一事件现已解决.
自动翻译自官方事件更新。
我们建议所有使用WordPress的客户验证以下插件更新到最新版本. 最近披露的弱点影响到这些插件的旧版本: CVE-2026-6279 – Avada Builder (Fusion Builder) – 未认证远程代码执行 受影响版本:3.15.2和较早 CVE-2026-10795 – UpdraftPlus 备份插件 – 认证旁通 受影响版本:1.26.4和较早 这些弱点可能让未经认证的攻击者获得对易受攻击的WordPress站点的控制,如果插件没有被更新到最新的可用版本,则会妥协WordPress用户账户. 如果您的网站使用其中任一插件,我们强烈建议您: 立即将受影响的插件更新为最新的可用版本 。 为任何意外的管理员账户、插件或修改后的文件审查您的 WordPress 安装 。 如果您认为您的网站受到影响, 或者您需要援助来审查您的安装, 请联系我们的支援团队 .
这一咨询现已关闭。 我们鼓励我们的客户确保将任何受影响的WordPress插件更新到最新版本,并继续遵循WordPress安全最佳做法. 如果您认为您的网站可能受到影响或需要援助,请联系我们的支援小组.
自动翻译自官方事件更新。
我们知道,在密歇根州兰辛的DC3数据中心,一个网络服务事件影响到一些客户。 液力网络工程师目前正在参与并努力尽快恢复服务。 我们今天上午将尽快提供更多资料.
液力网络网络工程师查明了原因并实施了固定,网络流量此时已恢复到数据中心的灾区. 我们正在积极监测环境。 我们今天上午将尽快提供更多资料.
这一事件已经得到解决.
自动翻译自官方事件更新。
We are currently experiencing a partial degradation in our monitoring and alerting system. Some monitoring components are intermittently unable to generate or relay alerts as expected. Our engineering teams are actively investigating the issue to identify the cause and restore full monitoring functionality. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or concerns, please open a support ticket or contact us via chat.
We are currently experiencing a service degradation affecting our monitoring infrastructure and monitoring ticket integration. As a result, some monitoring alerts may be delayed in being generated, delivered, or escalated to our teams. Customer services themselves are not impacted by this issue; however, the delay in alert processing may result in slower detection and response to service-related incidents. Our engineers are actively investigating and working to restore normal monitoring performance as quickly as possible. We appreciate your patience and understanding while we work to resolve this issue. If you have any questions or concerns, please open a support ticket or contact us via chat.
Our teams have implemented a fix for the issue affecting the monitoring system and are continuing to monitor the service to ensure stability. We will provide additional updates if any further issues are identified. Thank you for your patience.
This incident has been resolved.
We are investigating an issue preventing customers from reaching support via Phone. Please use Live Chat or open a Support Case at my.liquidweb.com for immediate assistance while we restore the phone service. We appreciate your patience and understanding as we work to restore this service. Thank you.
Our phone system is now back online, and agents should be able to connect and accept calls. We will continue to monitor the system to ensure stability. Thank you for your continued patience.
This incident has been resolved.
A recently disclosed vulnerability (CVE-2026-48172) in the LiteSpeed user-end cPanel plugin allows an unprivileged user to escalate to root privileges in plugin versions between v2.3 and v2.4.4. This issue has been classified as high severity. Public reports suggest the vulnerability was being exploited in the wild in May 2026, and indicators of compromise have been published. On May 19th cPanel issued a separate update which disabled and removed the plugin. This vulnerability is patched in v2.4.7 of the user-end plugin and v5.3.1.0 of the WHM plugin (which bundles the user-end plugin). Reference: https://nvd.nist.gov/vuln/detail/CVE-2026-48172 https://blog.litespeedtech.com/2026/05/21/security-update-for-litespeed-cpanel-plugin/ https://support.cpanel.net/hc/en-us/articles/40599423437079-Security-LiteSpeed-plugin-automatically-removed-during-nightly-update-May-19-2026 Status Our security and operations teams are completing an assessment of our infrastructure and will force a upcp update today for all systems we are able to reach. We plan to review for Indicators of Compromise following the updates. Customer Guidance Customers managing their own systems or using unmanaged services should ensure they have applied the latest security updates or have removed the plugin. Customers should also review their systems for indicators of compromise using the information provided in the LiteSpeed blog article. Should you need any assistance or have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: [email protected] We will continue monitoring this vulnerability and will provide updates if new information becomes available.
Status Update Our security and operations teams completed the assessment of our infrastructure, which forcd a upcp update today for all systems we were able to reach. We also reviewed environments for the indicators of compromise noted in the LiteSpeed article below. We will address any findings via a support ticket. We are resolving this incident at this time. Customer Guidance Customers are strongly encouraged to ensure they are running the updated version of the LiteSpeed plugin and to review their systems for the indicators of compromise. If our team does not have access to your system because it is unmanaged, self-managed, or access has been updated but not shared with Liquid Web, then we would not have been able to reach your system in order to apply updates or check for indicators of compromise. If you have any questions or concerns, you can reach us through the following channels: Live Chat via the Customer Portal: https://my.liquidweb.com Email: [email protected]
We are investigating an issue preventing customers from accessing the portal through login.liquidweb.com. Updates are forthcoming as more information becomes available. Need help? Chat with us or contact Support for assistance. We appreciate your patience and understanding as we work to restore portal access. Thank you.
We are continuing to investigate the issue impacting access to the portal through login.liquidweb.com. While the site may be loading for some users, our teams are still reviewing the issue and working to confirm full service stability. Updates will be provided as more information becomes available. Thank you for your patience while we continue working toward a resolution.
Access to the portal through login.liquidweb.com has been restored, and the site is now loading successfully. Our teams have implemented a fix and are continuing to monitor the service to ensure stability. We will provide additional updates if any further issues are identified. Thank you for your patience while we worked to restore access.
This incident has been resolved.
A recently disclosed Linux vulnerability (CVE-2026-31431), sometimes referred to as “Copy Fail,” affects certain Linux distributions and may allow a local, unprivileged user to escalate privileges under specific conditions. This issue has been classified as high severity. Status Our security and operations teams have completed an assessment of our infrastructure and have applied all relevant vendor patches and mitigations to affected systems. Impact No evidence of exploitation has been identified within our environment Systems under our management have been patched or otherwise mitigated Customer Guidance Customers managing their own systems or using unmanaged services should ensure they have applied the latest security updates provided by their Linux distribution and review any related vendor advisories. We will continue monitoring this vulnerability and will provide updates if new information becomes available.
This incident has been resolved.
We have been made aware of an incident that is affecting Let's Encrypt. The third party SSL provider is currently not issuing SSL certificates as they investigate the issue further. More information is available at at Let's Encrypts status page here: https://letsencrypt.status.io/ If you have any additional questions please reach out to our support team and we will be happy to assist
Let's Encrypt has updated their status post indicating that they are resuming their typical issuance of certificates. We will continue to monitor to see if there are any changes in their status going forward
This incident has been resolved.