WordPress 7.1.4 security release: all WPCloud sites protected
Monitoring - WordPress released version 7.1.4 on 28 October 2026 to fix several security vulnerabilities. All WordPress sites hosted on WPCloud are protected, and you don't need to do anything.

How we protect your site:
1. Firewall rules that block attempts to exploit these vulnerabilities are in place across our platform, protecting every site whether or not it has been updated yet.
2. WordPress's automatic security updates, which are on by default at WPCloud, apply the fix to most sites within a day.
3. Our team then checks every site and updates any that didn't update automatically.

Sites on older WordPress branches receive their own fixed version (for example 7.0.8, 6.9.11 or 6.8.12) and are protected even though they don't show 7.1.4.

Please check this page before opening a ticket: https://kb.wpcloud.wiki/knowledge-base/wordpress-7-1-4-security-release-28-october-2026-what-wpcloud-clients-need-to-know/
Oct 30, 2026 - 12:07 EDT
Brotli security flaw (CVE-2026-111497): WPCloud servers are patched
Monitoring - IMPORTANT: WPCLOUD SERVERS ARE PATCHED FOR THE GOOGLE BROTLI VULNERABILITY (CVE-2026-111497). YOU DO NOT NEED TO DO ANYTHING, AND YOU DO NOT NEED TO OPEN A TICKET TO CONFIRM IT.

Every component on our servers that uses Brotli has been updated to a fixed version: our web server (LiteSpeed), the operating system's Brotli library, and the library PHP uses for outbound requests. Node.js is not installed on our shared hosting servers.

Before opening a ticket about any widely reported security issue, please check our knowledge base first. We publish the status of each one there. Recent security events have brought in thousands of identical tickets, and answering each one individually adds support costs that ultimately have to be reflected in our pricing.

Full details: https://kb.wpcloud.wiki/knowledge-base/cve-2026-111497-google-brotli-decoder-wpcloud-status/
Oct 28, 2026 - 19:29 EDT
PHP security update complete: your PHP version number may not change
Update - Update, 29 October 2026: Some news coverage this week links the PHP2Shell vulnerabilities to a Linux kernel flaw, CVE-2026-46300 ("Fragnesia"), which attackers combined with them elsewhere. WPCloud is not affected: every server has been running a kernel that includes this fix since well before those attacks, and our security team re-checked every server on 28 October to confirm it. No action is required on your part. Details: https://kb.wpcloud.wiki/knowledge-base/cve-2026-46300-fragnesia-linux-kernel-flaw-wpcloud-status/
Oct 29, 2026 - 11:40 EDT
Update - Sites on PHP 8.2 and newer now show the PHP project's new version numbers in WordPress Site Health: 8.2.35, 8.3.36, 8.4.27 or 8.5.12. CloudLinux released builds carrying these numbers, and our regular updates installed them. A small number of sites may take up to another day to show the new number.

This changed only the number shown. The security fixes (CVE-2026-109618 and CVE-2026-109619) were installed and verified on every WPCloud server on 21 October, and your site has been patched since then.

Sites on PHP 8.1 and older (for example 8.1.34 or 7.4.33) keep their version number permanently, because the PHP project no longer releases new versions of them. CloudLinux adds the fix to the existing version, so those sites are patched too.

You don't need to do anything, and you don't need to open a ticket to check your PHP version. If your IT department, insurer or auditor needs written confirmation, open a ticket and let us know who it is for.

Full details and common questions: https://kb.wpcloud.wiki/knowledge-base/critical-php-security-release-21-october-2026-what-wpcloud-clients-need-to-know/
Oct 23, 2026 - 10:28 EDT
Monitoring - IMPORTANT: THE PHP VERSION NUMBER SHOWN FOR YOUR SITE DOES NOT TELL YOU WHETHER IT IS PATCHED. YOU MAY NOT SEE 8.5.12, 8.4.27, 8.3.36 OR 8.2.35, AND THAT IS EXPECTED.

The critical PHP security fixes released on 21 October 2026 (CVE-2026-109618 and CVE-2026-109619) were installed and verified on every WPCloud server on 21 October. You don’t need to do anything.

Why your version number looks unchanged: our PHP comes from CloudLinux, which adds security fixes to the version already installed instead of moving to a new version number. For example, a site on PHP 8.3 keeps showing 8.3.35 after the fix, even though PHP’s own fixed release is numbered 8.3.36, and a site on PHP 7.4 keeps showing 7.4.33. CloudLinux explains this in its advisory: https://cloudlinux.zendesk.com/hc/en-us/articles/31194180517916 and is planning a change to how patched versions are numbered to prevent this confusion in future.

Please don’t open a ticket to check your PHP version. Updating WordPress, plugins or themes won’t change anything either, since PHP is installed on our servers, not inside your website. If your IT department, insurer or auditor needs written confirmation, open a ticket and let us know who it is for.

Full details and common questions: https://kb.wpcloud.wiki/knowledge-base/critical-php-security-release-21-october-2026-what-wpcloud-clients-need-to-know/
Oct 22, 2026 - 11:46 EDT

About This Site

All incidents on this page are posted manually by our team, not by automated monitoring. Before anything is published, an engineer confirms the issue is real and writes a short summary of what we know. This avoids false alarms, but it does mean there can be a short delay between the start of an issue and it appearing here. If you've received an alert from a third-party monitor, our team is very likely already investigating.

MONTREAL DATA CENTRE Operational
TORONTO DATA CENTRE Operational
VANCOUVER DATA CENTRE Operational
EMAIL SERVERS Operational
DEV/SANDBOX SERVERS Operational
BACKUP SYSTEMS Operational
STAGING SITE SYSTEM Operational
CDN Operational
MANAGED DNS Operational
WPCLOUD SUPPORT SYSTEM PORTAL Operational
WPCLOUD.CA WEBSITE Operational
3RD PARTY COURTESY NOTICES Operational
WPCloud Status Page Provider Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Nov 11, 2026

No incidents reported today.

Nov 10, 2026

No incidents reported.

Nov 9, 2026

Scheduled security maintenance: CANADA300 and SANDBANKS
Completed - This maintenance has been cancelled. The security update was applied without any restart or downtime across our entire fleet, so no further action is needed.
Nov 9, 20:52 EST
Scheduled - Scheduled: Tuesday, November 10, 2026, 5:00 a.m. to 6:00 a.m. ET

Affected servers: CANADA300, SANDBANKS

We will be applying an important security update to the operating system kernel on the servers listed above. Each server will be restarted once during the window.

Expected impact: websites, cPanel and related services on each server will be briefly unavailable while it restarts, typically for less than 10 minutes. CANADA300 will be updated first, followed by SANDBANKS. No action is required from you, and your site data is not affected.

We will update this notice when the maintenance is complete.
Nov 9, 19:02 EST

Nov 8, 2026

Scheduled maintenance: GRAVENHURST cluster
Completed - The scheduled maintenance on the GRAVENHURST cluster is complete. The cluster is now running on replacement hardware and operating normally.
Nov 8, 06:19 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 8, 06:00 EST
Scheduled - We will move the GRAVENHURST cluster to replacement hardware on Sunday 8 November, starting at 6:00 a.m. ET. This follows the hardware fault on the cluster's current host server described in our incident report.

Sites on the GRAVENHURST cluster may be unavailable for a few minutes during the move. The maintenance window runs to 7:00 a.m. ET to allow time for checks afterwards.

No action is needed from you. We will post an update here when the maintenance is complete.
Nov 7, 14:51 EST

Nov 7, 2026

KLUANE cluster
Resolved - This incident has been resolved.
Nov 7, 19:50 EST
Monitoring - Server is now responding. Monitoring.
Nov 7, 19:34 EST
Investigating - We are currently investigating an issue impacting the KLUANE cluster.
Nov 7, 19:31 EST
GRAVENHURST Incident
Postmortem - Read details
Nov 7, 14:35 EST
Resolved - Server remains stable at this time. Sysadmin team will continue to monitor & will post more details in port mortem if available.
Nov 7, 07:46 EST
Update - Server is now responding our sysadmin team continues to investigate.
Nov 7, 07:38 EST
Investigating - We are currently investigating an issue impacting the GRAVENHURST cluster.
Nov 7, 07:33 EST
Scheduled maintenance: STRATHCONA, RESTOULE, GROSMORNE and AULAVIK clusters
Completed - The scheduled maintenance on the STRATHCONA, RESTOULE, GROSMORNE and AULAVIK clusters is complete. All clusters are back online and operating normally.
Nov 7, 05:14 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 7, 05:00 EST
Scheduled - We will be applying a system update to the STRATHCONA, RESTOULE, GROSMORNE and AULAVIK clusters on Saturday, November 7, between 5:00 AM and 5:45 AM Eastern. Each cluster will restart once during this window, and sites on that cluster may be briefly unavailable for a few minutes. No action is needed from clients.

Affected components: STRATHCONA, RESTOULE, GROSMORNE and AULAVIK clusters
Nov 6, 19:13 EST

Nov 6, 2026

No incidents reported.

Nov 5, 2026

Scheduled maintenance: server updates (KLUANE & SUPERIOR)
Completed - The scheduled maintenance has been completed.
Nov 5, 05:30 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 5, 05:00 EST
Scheduled - We will be applying a system update to two of our hosting clusters (KLUANE & SUPERIOR) on Thursday, November 5, between 5:00 AM and 5:30 AM Eastern. Sites on those servers may be unavailable for a few minutes while each server restarts. No action is required on your part.
Nov 4, 18:43 EST
GRAVENHURST Cluster
Resolved - Cluster remains stable, our sysadmin team will investigate root cause & post more details in post mortem once available. Issue is now being marked as resolved.
Nov 5, 00:00 EST
Monitoring - Server is now responding. Monitoring.
Nov 4, 23:44 EST
Identified - This appears to be a hardware issue at the data centre, we're awaiting more details on the cause.
Nov 4, 23:41 EST
Investigating - We are currently investigating an issue impacting the GRAVENHURST cluster.
Nov 4, 23:32 EST

Nov 4, 2026

SUPERIOR server: temporary bot protection in place (4 November 2026)
Resolved - Update, 4 November 2026, 5:15 p.m. Eastern

This incident is resolved. Websites on the SUPERIOR server have been performing normally since approximately 2:30 p.m. Eastern.

Summary: from late morning until early afternoon, a large bot network crawled several websites on the server, rotating through thousands of residential IP addresses and requesting endless combinations of calendar dates, product filters and similar pages that cannot be served from cache. The resulting load slowed websites across the server.

We identified the pattern and put targeted protection in place on the affected websites, and blocked the individual sources that were causing the most load. These protections remain in place and do not affect normal visitors.

A temporary browser check was enabled on the server between approximately 1:30 and 2:15 p.m. Eastern. During that window, some visitors were asked to complete a verification before the site loaded, and uptime monitoring services may have reported websites as down. Those monitoring alerts were caused by the verification check and were not real outages.

We continue to monitor the server closely and are strengthening protection against this type of traffic across our platform.

WPCloud SOC Team
Nov 4, 17:12 EST
Monitoring - Update, 4 November 2026, 2:20 p.m. Eastern

Websites on the SUPERIOR server were slow or intermittently unavailable from late morning until approximately 1:35 p.m. Eastern. The cause was a large bot network crawling several websites on the server, rotating through thousands of residential IP addresses and requesting endless combinations of calendar dates, product filters and similar pages that cannot be served from cache.

We have put targeted protection in place on the affected websites. These rules block the bot's requests without affecting normal visitors, and server performance has returned to normal.

A temporary browser check was enabled on the server between approximately 1:30 and 2:15 p.m. Eastern. During that window, some visitors were asked to complete a verification before the site loaded, and uptime monitoring services may have reported websites as down. Those monitoring alerts were caused by the check and were not real outages. The check has been removed.

The bot network is still active and moving between websites. We are adding protection where needed and continuing to monitor the server closely.

WPCloud SOC Team
Nov 4, 14:19 EST
Investigating - Starting late this morning, the SUPERIOR server came under heavy automated crawling. A large bot network, rotating through thousands of residential IP addresses and posing as ordinary web browsers, requested endless combinations of calendar dates, product filters and similar pages. Because almost every one of those requests was unique, none could be served from cache, and the resulting load slowed or interrupted websites across the server.

What we have done:

1. Enabled a temporary browser check (Google reCAPTCHA) on the server. Some first-time visitors may be asked to tick an "I'm not a robot" checkbox once before the site loads. After passing it once, that visitor browses normally.

2. Search engines such as Google and Bing pass automatically.

3. Added targeted protection against the specific crawl patterns on the most affected sites. Normal visitors are not affected by these rules.

Server load returned to normal within minutes of these measures.

Uptime monitoring: while the browser check is in place, third-party uptime monitoring services may report your site as down or returning errors even though it is loading normally for visitors. These are false alerts caused by the browser check, not real outages, and they will stop once the check is removed.

This is a short-term measure. The reCAPTCHA check will be removed once the bot traffic subsides and the targeted protections are confirmed to be holding. We will post an update when it has been removed.

No action is required on your part.

Regards,
WPCloud SOC Team
Nov 4, 13:37 EST
Scheduled maintenance: BRANNEN cluster update
Completed - Maintenance is complete.
Nov 4, 03:56 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 4, 03:45 EST
Scheduled - We will be applying a system update to one of our clusters (BRANNEN) on Wednesday, November 4, between 3:45 AM and 4:15 AM Eastern. Sites on that server may be unavailable for a few minutes while it restarts. No action is required on your part.
Nov 3, 19:14 EST

Nov 3, 2026

Scheduled Maintenance: WADDINGTON Cluster Migration
Completed - Maintenance is complete. All websites on this server have been moved to new hardware and are running normally.
Nov 3, 04:28 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 04:00 EST
Scheduled - We will be migrating all sites on the WADDINGTON hosting cluster to new, upgraded hardware (GLACIER) as part of our ongoing infrastructure improvement program. The work has been scheduled during off-peak hours to minimise any impact.

The maintenance will take place in two phases:

1. Final data synchronization (approximately 15 minutes): the latest site files and databases are copied to the new hardware. No interruption is expected during this phase.
2. IP address transition (approximately 15 minutes): the existing IP addresses are moved to the new hardware. Sites on the WADDINGTON cluster will experience a brief interruption during this phase.

We have reserved a one-hour window to complete and verify all work.

No action is required on your part. Your sites keep their current IP addresses, so no DNS changes are needed.

We will update this notice once the migration is complete.
Nov 2, 14:10 EST

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

Oct 29, 2026

Oct 28, 2026

Incident History Powered by Atlassian Statuspage