Internet outages and Cloudflare errors: does downtime hurt your Google rankings?
"Internet" broke out on Google Trends on 24 October 2026 after a week of mass site outages. Here is how Googlebot treats 5xx errors, how long downtime can last before rankings suffer, and what to check in Search Console once you're back up.
If this week's internet outages took your site offline, your rankings are probably fine. Googlebot slows crawling during 5xx errors but keeps pages that are already indexed. Google says the risk starts when errors last longer than a day or two. After that, URLs can drop out of the index. Serve a 503, fix the cause, then check Search Console's Crawl stats.
Big news sites are listing which sites went down. This post covers what that downtime does to your Google traffic, and the five checks to run once you're back up.
Why "internet" is trending on 24 October 2026
WriteOut's Trend Monitor flagged "internet" as a breakout in the US: 1,000+ searches, +100%, starting 24 Oct 06:20 UTC and still trending when fetched at 18:53 site time. The related search is "cloudflare". No single report explains the spike. The most likely cause is a week of mass site outages:
- 23 Oct: CISA updated its PHP alert with a detection rule.
- 21 Oct: PHP's GitHub security advisories went live at 13:34 UTC and patched builds followed at about 14:00 UTC, fixing PHP2Shell: two critical flaws (CVE-2026-109618 and CVE-2026-109619) that affect PHP 5.4 to 8.5, according to the PHP security advisory. Owners took servers offline to patch. Wikimedia tools went down, and so did the Edinburgh and Oxford council sites and the Metropolitan Police site (Insurance Business UK).
- 20 Oct: Details of the flaws leaked ahead of the disclosure planned for 22 Oct. On the same day, Google Cloud's London region (europe-west2) went down because of a power problem (ThousandEyes).
There is one gap. As of 24 October 2026, I found no confirmed outage across Cloudflare's whole network. In the sources, Cloudflare appears as one of several providers offering firewall protection while sites patch. If your visitors saw a Cloudflare 521 or 522 error page, your origin server was usually the thing that was down.
Does internet downtime hurt your Google rankings?
Not if it's short. Google's documentation on HTTP and network errors says 5xx and 429 responses make Googlebot slow its crawling for a while. Pages that are already indexed stay indexed. URLs that keep returning server errors are eventually dropped.
| What Googlebot sees | What Google does | Ranking risk |
|---|---|---|
| 5xx errors for a few hours | Slows crawling and retries later | Low. Indexed pages stay put. |
| 5xx errors for 1–2 days | Google's crawl-rate guidance says not to serve deliberate errors for longer than this | Rising. Crawling should recover once the site is back. |
| Errors that persist | Drops URLs from the index | High. You lose traffic until pages are crawled again. |
| robots.txt returns 5xx | Treats the whole site as off-limits for crawling | High while it lasts. Crawling stops. |
What should you do while your site is down?
The problem: your maintenance page returns 200 OK. Google can then index "Down for maintenance" as if it were your article.
The fix: return 503 Service Unavailable with a Retry-After header. Keep robots.txt reachable.
The problem: your server runs PHP that hasn't been patched.
The fix: update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 from php.net/downloads.php, then restart every PHP process and rebuild container images. PHP 7.4, 8.0 and 8.1 are end-of-life and got only source patches, so rely on your distro or LTS vendor; PHP 7.3 and older won't get a fix. PHP says no configuration change fully mitigates the flaws. cPanel, CloudLinux and SiteGround have released fixes, so check with your host.
A few hours of 503 while you patch costs far less than a server someone else controls.
What to check in Search Console after an outage
- Settings › Crawl stats › Host status: look for failed server connectivity or robots.txt fetches between 20 and 24 Oct.
- Crawl stats, By response: check how big the server error (5xx) share got. It should fall back once you're up.
- Pages report: find "Server error (5xx)" under the reasons pages aren't indexed. Click Validate fix once the cause is resolved.
- URL Inspection: run a live test on your top 10 URLs and request indexing for any that dropped.
- Performance: compare the outage days with the week before. A dip only on the days you were down is normal. If the dip is still there a week later, start digging.
Running these checks across a client roster? Learn more → WriteOut for SEO agencies
From the desk: [ANMOL: add a first-hand example of a site outage and how long it took GSC impressions to recover, if you have one. Otherwise remove this block.]
How WriteOut fixes it
The problem: searches driven by an outage peak within hours. When they do, the top results for "internet" are still dictionary definitions and Wikipedia pages that say nothing about this week.
The fix: WriteOut's Trend Monitor spotted "internet", with "cloudflare" as a related search, on the day the search took off. It drafts the explainer in your desk's voice and publishes once you approve. You get a page up while the list of competing pages is still short. Learn more → or see WriteOut for news portals.
The short version
- Downtime of a few hours rarely hurts Google rankings. Googlebot slows down and comes back later.
- Google treats 1–2 days of 5xx errors as the ceiling. Errors that persist get URLs dropped.
- Serve a 503 with Retry-After during maintenance, never a 200 or 404.
- If robots.txt returns 5xx, Google stops crawling the whole site.
- After you recover, check Crawl stats, the Pages report and Performance for 20–24 Oct.
Frequently asked questions
Does internet downtime hurt Google rankings?
Short internet downtime rarely hurts Google rankings. When a site returns 5xx errors, Googlebot slows its crawl rate and retries later, and pages already in the index stay there. The risk grows when errors last beyond one or two days, because Google eventually drops URLs that keep returning server errors. Pages that drop out lose their traffic until Google crawls them again.
How long can a website be down before Google drops pages?
Google's crawl-rate documentation says not to serve deliberate 5xx or 429 errors for longer than one to two days, because doing so can harm how a site appears in Google. Google gives no exact cut-off, but persistent server errors lead to URLs being removed from the index. Treat a day or two as the limit and fix the cause before that.
Should a maintenance page return 503 or 200?
A maintenance page should return 503 Service Unavailable, ideally with a Retry-After header. A 503 tells Googlebot the outage is temporary, so Google keeps your indexed pages and comes back later. A maintenance page that returns 200 OK can get indexed in place of your real content. A 404 tells Google the page is gone.
Why are so many websites down in October 2026?
Many websites went offline in October 2026 because their owners were patching PHP2Shell, two critical PHP flaws (CVE-2026-109618 and CVE-2026-109619) that PHP fixed on 21 October 2026. CISA, the NSA and the UK NCSC told server owners to patch at once, or to take the server offline if they couldn't. A site being down does not mean it was hacked.
Does a Cloudflare 521 or 522 error hurt SEO?
A Cloudflare 521 or 522 error reaches Googlebot as a 5xx server error, so Google handles it like any other outage. It slows crawling and keeps indexed pages for short outages. These Cloudflare errors usually mean the origin server behind Cloudflare is down or not responding. Fix the origin quickly, then check Search Console's Crawl stats for failed requests.
Sources
- PHP 2026 news archive: security releases · PHP
- PHP security advisory GHSA-w8hw-w9fx-j79w · PHP (GitHub)
- HTTP status codes, network and DNS errors, and Google Search · Google Search Central
- Critical security issue affecting PHP · UK NCSC
- Critical PHP Security Release CVE-2026-109618 and CVE-2026-109619 · cPanel
- PHP CVE-2026-109618 and CVE-2026-109619 · CloudLinux
- Google Cloud outage analysis: October 20, 2026 · ThousandEyes
- Google on PHP2Shell downtime · Search Engine Roundtable