Is HTTP 206 a downtime signal?

Usually no. It is often expected for range-based delivery. Treat it as a normal availability signal unless users still fail to complete downloads or playback.

Why would some regions show 206 and others 200?

Different caches, range support, and client behavior can lead to mixed but healthy status patterns. Investigate only when user impact appears.

Not typically for normal web pages. It is more relevant to media and file transfer workflows than standard crawl/index paths.

HTTP Status Codes

What Does HTTP Status 206 Mean? (Partial Content)

Published March 12, 2026 · 10 min read · Author: WebsiteDown

What HTTP 206 (Partial Content) Means In Plain English

A 206 status (Partial Content) means the server delivered only part of the resource because the client asked for a specific byte range.

This is normal for video streaming, download resume, and large files. It is usually a healthy behavior when range requests are expected.

If you want the broader context across all status code families, use the full HTTP Status Codes Guide (2xx, 3xx, 4xx, 5xx).

Quick Navigation

What HTTP 206 (Partial Content) Means In Plain English
How to Read HTTP 206 in WebsiteDown Results
Most Common Root Causes
What to Do Next
What to Avoid During Triage
Real-World Examples
HTTP 206 FAQ

How to Read HTTP 206 in WebsiteDown Results

In WebsiteDown checks, 206 indicates the server is reachable and capable of responding. It should be interpreted as available service, not a hard outage.

However, repeated 206 with stalled playback or failed downloads can indicate CDN range handling issues or origin mismatch.

For triage, compare this with HTTP 200, HTTP 502, and the CDN regional diagnostics guide.

Most Common Root Causes

Video/audio players requesting chunks instead of full files.
Resume download behavior after interrupted network sessions.
CDN edge optimization for large static assets.
Proxy or cache layers rewriting range headers unexpectedly.

What to Do Next

Verify `Accept-Ranges` and `Content-Range` headers are correct for the requested object.
Test the same asset from multiple regions to detect edge-specific partial-content problems.
Confirm that backend and CDN agree on object length and byte ranges.
Check for intermittent 206 mixed with 503 or 504 during load spikes.

What to Avoid During Triage

Do not assume 206 means incomplete service by default; partial delivery is often intentional.
Do not ignore user complaints when 206 appears healthy on paper; media UX can still degrade badly.

Real-World Examples

Example: video seeks return 206 in every region and playback is smooth: healthy streaming pattern.
Example: one POP returns 206 but fails mid-stream due corrupted range handling, while others return 200/206 successfully.
Example: large software downloads bounce between 206 and 408 causing repeated resume loops.