---
title: "The OSI Model Explained: 7 Layers With Real Examples"
description: Explore the OSI model, its 7 layers, and real-world examples to understand how networks communicate.
image: https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-03-2026-04-45-37-9940-AM.jpeg
---

[![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us)

[📘 Learn ▾](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us)

[CDN Fundamentals](https://blog.blazingcdn.com/cdn-fundamentals?hsLang=en-us) [By Content Type](https://blog.blazingcdn.com/by-content-type?hsLang=en-us) [Advanced Concepts](https://blog.blazingcdn.com/advanced-concepts?hsLang=en-us) [📖 Glossary](https://blog.blazingcdn.com/glossary?hsLang=en-us)

[🎬 Video & Streaming ▾](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us)

[🔴 Live Streaming](https://blog.blazingcdn.com/live-streaming?hsLang=en-us) [📺 VOD & OTT](https://blog.blazingcdn.com/vod-ott?hsLang=en-us) [🎞️ Encoding & Players](https://blog.blazingcdn.com/encoding-players?hsLang=en-us) [🎧 Audio & Podcasts](https://blog.blazingcdn.com/audio-podcasts?hsLang=en-us) [💰 Bandwidth & Costs](https://blog.blazingcdn.com/bandwidth-costs?hsLang=en-us)

[🏗️ Infrastructure ▾](https://blog.blazingcdn.com/cdn-infrastructure?hsLang=en-us)

[🗄️ Storage & Origin](https://blog.blazingcdn.com/storage-origin?hsLang=en-us) [📦 Large File Delivery](https://blog.blazingcdn.com/large-file-delivery?hsLang=en-us) [💸 Cloud Costs & Egress](https://blog.blazingcdn.com/cloud-costs-egress?hsLang=en-us) [🌐 Networking & ISP](https://blog.blazingcdn.com/networking-isp?hsLang=en-us) [⚙️ DevOps & Cloud Infra](https://blog.blazingcdn.com/devops-cloud-infra?hsLang=en-us) [⚡ Web Performance](https://blog.blazingcdn.com/web-performance?hsLang=en-us)

[🏭 Industries ▾](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us)

[📺 Media & Broadcasting](https://blog.blazingcdn.com/media-broadcasting?hsLang=en-us) [💾 Software & SaaS](https://blog.blazingcdn.com/software-saas?hsLang=en-us) [📣 AdTech & Advertising](https://blog.blazingcdn.com/adtech-advertising?hsLang=en-us) [🎮 Gaming & Esports](https://blog.blazingcdn.com/gaming-esports?hsLang=en-us) [📱 Mobile Apps & Developers](https://blog.blazingcdn.com/mobile-apps-developers?hsLang=en-us) [🤖 AI & Machine Learning](https://blog.blazingcdn.com/ai-machine-learning?hsLang=en-us) [🏛️ Enterprise & Corporate](https://blog.blazingcdn.com/enterprise-corporate?hsLang=en-us) [📚 E-Learning & EdTech](https://blog.blazingcdn.com/e-learning-edtech?hsLang=en-us) [🏟️ Sports & Live Events](https://blog.blazingcdn.com/sports-live-events?hsLang=en-us)

[💰 Pricing & Compare ▾](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us)

[Provider Pricing](https://blog.blazingcdn.com/provider-pricing?hsLang=en-us) [Cost Optimization](https://blog.blazingcdn.com/cost-optimization?hsLang=en-us) [Decision Support](https://blog.blazingcdn.com/decision-support?hsLang=en-us) [⚡ Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [Provider Comparisons](https://blog.blazingcdn.com/provider-comparisons?hsLang=en-us) [Strategy Comparisons](https://blog.blazingcdn.com/strategy-comparisons?hsLang=en-us) [📊 Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us)

[🔒 Security ▾](https://blog.blazingcdn.com/cdn-security?hsLang=en-us)

[Attack Protection](https://blog.blazingcdn.com/attack-protection?hsLang=en-us) [Encryption & Access](https://blog.blazingcdn.com/encryption-access?hsLang=en-us) [Video & DRM Security](https://blog.blazingcdn.com/video-drm-security?hsLang=en-us)

[🛠️ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us)

[Get Started](https://blazingcdn.com/sign-up-contact-form/)

[Infrastructure](https://blog.blazingcdn.com/en-us/tag/infrastructure) [Infrastructure - Networking & ISP](https://blog.blazingcdn.com/en-us/tag/infrastructure-networking-isp)

# The OSI Model Explained: 7 Layers With Real Examples

 Vadym Borovskyi  Nov 3, 2026, 5:48:24 AM

![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-03-2026-04-45-37-9940-AM.jpeg)

Every device and proxy in a request path can be classified by one question: what is the deepest header it reads before deciding where traffic goes? The OSI model gives that question its vocabulary, with seven layers running from electrical and optical signaling at layer 1 up to application protocols such as HTTP and DNS at layer 7.

The OSI reference model, standardized as ISO/IEC 7498-1 (first edition 1984, revised 1994), divides networking into seven layers: physical, data link, network, transport, session, presentation and application. In CDN and load-balancing design, three of them drive almost every decision: layer 3 (IP routing and Anycast), layer 4 (TCP and UDP flows identified by the 5-tuple) and layer 7 (HTTP requests, headers and cache keys).

A layer 4 load balancer forwards connections without parsing HTTP. A layer 7 proxy terminates TLS and the client's TCP connection, then opens its own toward the backend. That one difference decides what you can cache, log, rewrite and debug at each hop.

## **OSI model layers 1 to 7 with real protocols and devices**

The table maps each layer to the protocol data unit (PDU), the protocols you actually run, the hardware or software that operates there, and the failure you are most likely to debug at that layer in a delivery network.

| Layer | PDU | Real protocols | Devices and software | Typical failure at this layer |
| --- | --- | --- | --- | --- |
| 7 Application | Message | HTTP/1.1, HTTP/2, HTTP/3, DNS, gRPC, SMTP | CDN cache servers, reverse proxies (nginx, Varnish, Envoy), API gateways | Cache key fragmentation, wrong Vary, 5xx from origin |
| 6 Presentation | Data | TLS encryption, gzip, Brotli, zstd content encoding, character sets | TLS libraries, compression modules in the proxy | Double compression, cipher mismatch |
| 5 Session | Data | TLS session resumption, RPC sessions, SOCKS | Session ticket stores shared across a server fleet | Low resumption rate after a load balancer rehash |
| 4 Transport | Segment or datagram | TCP, UDP, QUIC (over UDP) | Linux IPVS, HAProxy in TCP mode, nginx stream module, XDP-based balancers | Retransmits, SYN backlog overflow, conntrack table exhaustion |
| 3 Network | Packet | IPv4, IPv6, ICMP, plus BGP as the control plane that programs it | Routers, ECMP fabrics, Anycast announcements | Path MTU black holes, route flaps, asymmetric routing |
| 2 Data link | Frame | Ethernet (IEEE 802.3), 802.1Q VLANs, LACP, ARP and IPv6 neighbor discovery | Switches, bonded NICs | MTU mismatch, uneven LACP hashing |
| 1 Physical | Bits and symbols | 100GBASE-SR4, 400G optics, DWDM, copper twinax | Transceivers, fiber, NIC PHYs | Low optical receive power, rising CRC errors |

Most delivery incidents land at layers 3, 4 and 7, which is why the rest of this article concentrates on them.

### Why layers 5 and 6 stop matching real stacks

The TCP/IP stack that every production system implements (described in RFC 1122) has four layers, not seven. Session and presentation functions were folded into TLS and application libraries decades ago, so no device you can buy is a "layer 5 switch".

TLS is the clearest misfit: it encrypts (a layer 6 job), resumes sessions (a layer 5 job) and runs between TCP and HTTP. Treat it as part of layer 7 for design purposes, because the box that terminates TLS is the only one that can read HTTP.

## **What each layer costs: header overhead on a 1500-byte MTU**

Every layer adds bytes, and the arithmetic explains why a 10 Gb/s port never delivers 10 Gb/s of file data. Take a full-size Ethernet frame carrying TCP over IPv4 with timestamps enabled:

- Layer 1 and 2 on the wire: 8 bytes preamble, 14 bytes Ethernet header, 4 bytes frame check sequence, 12 bytes interframe gap, so 38 bytes per frame.
- Layer 3: 20 bytes IPv4 header (40 bytes for IPv6).
- Layer 4: 20 bytes TCP header plus 12 bytes of timestamp option, so 32 bytes.
- Payload per frame: 1500 minus 20 minus 32 equals 1448 bytes, carried in 1538 bytes of wire time.

Efficiency is 1448 divided by 1538, or 94.1%, so a 10 Gb/s link tops out near 9.41 Gb/s of TCP payload on IPv4. On IPv6 the payload drops to 1428 bytes and the ceiling to about 9.28 Gb/s. With 9000-byte jumbo frames inside a data center, payload efficiency rises to 99.0%.

Layers above transport are cheaper than people assume. A full TLS 1.3 record adds 22 bytes (5 header, 1 content type, 16 authentication tag) to 16,384 bytes of data, about 0.13%. Tunnels are the expensive surprise: GRE over IPv4 costs 24 bytes and VXLAN 50 bytes, which is enough to push 1500-byte packets past the path MTU and trigger the black holes covered below.

For capacity planning, our rule of thumb from this arithmetic: provision roughly 6.2% more layer 1 capacity than the payload throughput you sell on IPv4, and about 7.7% more on IPv6.

## **How CDNs, proxies and load balancers map to layers 3, 4 and 7**

The useful classification is the deepest header read for the forwarding decision, combined with whether the device terminates the connection. Those two properties predict state, cost and visibility better than any marketing label.

### Layer 3: Anycast and ECMP

Anycast announces the same IP prefix over BGP from many sites, so the internet's routing table picks the site. Failover happens when a site withdraws its route, typically converging in seconds rather than waiting out a DNS TTL. ECMP routers then spread packets across equal-cost next hops.

The OSI labels blur here. ECMP hashes on source and destination ports, which are layer 4 fields, yet the router keeps no per-flow state. That statelessness is the point: a layer 3 tier scales with line rate, not with connection count. BlazingCDN, for example, steers clients with [**Anycast routing with built-in failover**](https://blazingcdn.com/anycast-cdn/) in front of NVMe SSD cache servers, which is the layer 3 plus layer 7 split described in this section.

### Layer 4: connection-aware balancing

A layer 4 balancer tracks flows by 5-tuple and forwards packets to a backend without reading the payload. It can run in direct server return (DSR) mode, where responses bypass the balancer entirely. For egress-heavy workloads such as video segments and installers, DSR matters because response bytes outnumber request bytes by orders of magnitude.

Two common variants sit between layers 4 and 7. SNI routing reads the hostname from the TLS ClientHello without decrypting anything, and the PROXY protocol prepends the original client address so backends still see it.

### Layer 7: CDN edges and reverse proxies

A CDN cache is unavoidably layer 7: the cache key is built from host, path, query string and Vary headers, all of which require terminating TLS and parsing HTTP. The proxy holds two TCP connections per request path, buffers responses and can coalesce concurrent misses into one origin fetch.

A real CDN request crosses all three tiers in order: an Anycast route picks the site, an ECMP or layer 4 tier picks a cache server (often by consistent hashing so the same object lands on the same disk), and the layer 7 process serves or fetches the object.

## **Layer 4 vs layer 7 load balancing: which one a workload needs**

Pick the lowest layer that satisfies the requirement. Every layer you go up adds per-connection state, CPU for TLS and parsing, and a new place for latency to hide.

| Requirement | Lowest layer that works | What you give up by going higher |
| --- | --- | --- |
| Survive a site outage without DNS TTL delay | Layer 3 (Anycast route withdrawal) | Nothing; higher layers cannot replace it |
| Keep TLS end to end, keys only on backends | Layer 4 (passthrough or SNI routing) | Key custody moves to the proxy |
| Responses bypass the balancer (DSR) | Layer 4 | All egress flows through the proxy |
| Route by path, host header or cookie | Layer 7 | Not applicable |
| Cache, compress or rewrite responses | Layer 7 | Not applicable |
| Per-request status codes and latency in logs | Layer 7 | Not applicable |

Failover and raw egress belong at layers 3 and 4, while anything that depends on understanding a request, including caching, belongs at layer 7.

## **Failure modes and observability gaps by layer**

**Anycast and long TCP flows.** When a BGP path changes mid-transfer, packets for an existing connection can arrive at a different site that holds no state for it, which answers with a reset. Short HTTP requests rarely notice; a multi-gigabyte download that runs for minutes is far more exposed. Range requests and client retry logic are the practical mitigation.

**Path MTU black holes.** Path MTU discovery depends on ICMP "packet too big" messages reaching the sender. When a firewall drops them and a tunnel shrinks the path below 1500 bytes, small requests succeed and large responses stall. Clamping TCP MSS at the tunnel edge (1436 bytes on IPv4 for GRE: 1500 minus 24 minus 40) removes the dependency.

**Lost client identity.** A layer 4 balancer in NAT mode hides the client address unless you add the PROXY protocol. A layer 7 proxy adds X-Forwarded-For, which clients can forge, so trust only the entry appended by your own outermost proxy.

**Split visibility.** Layer 4 tiers see bytes, connections and resets but never an HTTP status. Layer 7 tiers see status codes and cache results but not retransmits on the client leg. An incident that lives between the two (for example, a 200 response delivered at 300 kb/s because of 4% packet loss) is invisible unless you correlate both data sets on the same connection.

**QUIC breaks layer 4 assumptions.** QUIC carries reliability, congestion control and the TLS 1.3 handshake inside UDP. A layer 4 balancer sees only UDP on port 443, and because QUIC allows connection migration when the client address changes, 5-tuple hashing can send a live connection to the wrong server unless the balancer routes on the QUIC connection ID.

## **How to verify layer behavior on your own stack**

- Layer 1 and 2: interface CRC and input error counters plus transceiver receive power in dBm; any steady increase in CRC errors means optics or cabling, not software.
- Layer 3 and 4: the MSS value in captured SYN packets (expect 1460 on clean IPv4 paths, lower behind tunnels) and the kernel's TCP retransmitted segments counter as a ratio of segments sent.
- Layer 7: the Age header and your CDN's cache status header on repeated requests for the same object; Age that never increases points to a cache key that varies per request.

## **Where the OSI model helps and where it misleads**

The model earns its place in two situations: incident triage, where "which layer is failing" narrows the search in minutes, and vendor conversations, where "layer 4 or layer 7" instantly tells you what a product can and cannot see. It is also the shared language on every network architecture diagram, so new engineers need it.

It misleads when taken as an implementation guide. Real stacks have four layers, TLS and QUIC deliberately cut across the boundaries, and ECMP routers read layer 4 fields. Classify devices by the deepest header they read and whether they terminate connections; the layer number is a shorthand for that, not a substitute.

## **FAQ: OSI model layers in CDN and load balancer design**

### What are the 7 layers of the OSI model in order?

From bottom to top, the 7 layers of the OSI model are physical, data link, network, transport, session, presentation and application. Real protocols sit at most of them: Ethernet at layer 2, IPv4 and IPv6 at layer 3, TCP and UDP at layer 4, HTTP and DNS at layer 7. Layers 5 and 6 are largely absorbed into TLS and application libraries.

### Is a CDN layer 4 or layer 7 in the OSI model?

A CDN edge is a layer 7 system, because caching requires parsing HTTP: the cache key comes from host, path, query string and Vary headers. Most CDNs also work at layer 3, using Anycast or DNS steering to pick a site, and at layer 4 inside each site, where balancers spread connections across cache servers.

### Which OSI layer does TLS belong to?

TLS does not fit a single OSI layer. It provides encryption, a presentation-layer function, and session resumption, a session-layer function, yet it runs on top of TCP and below HTTP. Engineers usually call it layer 4.5 or group it with layer 7, because the device terminating TLS is the only one able to read HTTP.

### Where do QUIC and HTTP/3 fit in the OSI model?

QUIC performs layer 4 transport functions inside UDP datagrams and embeds the TLS 1.3 handshake, while HTTP/3 is the layer 7 protocol running on top. A layer 4 balancer sees QUIC only as UDP on port 443, so stable routing requires reading the QUIC connection ID, since client addresses can change during a connection.

### What is the difference between layer 3 and layer 4 load balancing in the OSI model?

Layer 3 balancing steers traffic by destination IP, through Anycast routes or ECMP next hops, while layer 4 balancing tracks individual TCP or UDP flows by their 5-tuple. The boundary blurs in practice: ECMP routers hash on ports, which are layer 4 fields, even though they are layer 3 devices that keep no per-flow state.

## **Map your request path to OSI layers this week**

Draw every hop between a client and your origin: DNS or Anycast steering, any layer 4 balancer, each TLS termination point, each cache and the origin itself. Next to each hop write the deepest header it reads, whether it terminates the connection, and the one metric it exports (retransmits, resets, status codes, cache results). The gaps in that last column are where your next unexplained slowdown will hide, and filling them costs far less than finding them during an incident.

If your workload is heavy static delivery such as video, installers or game patches, the [**BlazingCDN features page**](https://blazingcdn.com/features/) lists what is included on every plan, from origin shield and request coalescing to Prometheus metrics for the layer 7 tier.

Share: [f](https://www.facebook.com/sharer/sharer.php?u=https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples) [in](https://www.linkedin.com/sharing/share-offsite/?url=https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples) [𝕏](https://twitter.com/intent/tweet?url=https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples&text=) [✉](mailto:?subject=%3Cspan%20id="hs_cos_wrapper_name"%20class="hs_cos_wrapper%20hs_cos_wrapper_meta_field%20hs_cos_wrapper_type_text"%20style=""%20data-hs-cos-general-type="meta_field"%20data-hs-cos-type="text"%20%3EThe%20OSI%20Model%20Explained:%207%20Layers%20With%20Real%20Examples%3C/span%3E&body=https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples)

![BlazingCDN](https://blog.blazingcdn.com/hs-fs/hubfs/Logo/blog-logo-w.png?height=24&name=blog-logo-w.png)

*Heavy traffic.*  
Light bill.

The CDN for video and large traffic

Their monthly bill vs ours

- 20 TBFastly $2,087**$92.50**
- 50 TBCDN77 $990**$215**
- 200 TBCloudFront $11,965**$765**

Published list prices, Aug 2026

[Calculate your cost](https://blazingcdn.com/cdn-cost-calculator/?utm_source=blog&utm_medium=sidebar&utm_campaign=blog_sidebar&utm_content=compare_calc)

## Related posts

[![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-07-50-38-8948-AM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-ipv6-ipv6-vs-ipv4-and-why-it-matters?hsLang=en-us)

Infrastructure

### [What Is IPv6? IPv6 vs IPv4 and Why It Matters](https://blog.blazingcdn.com/en-us/what-is-ipv6-ipv6-vs-ipv4-and-why-it-matters?hsLang=en-us)

The short answer to what is IPv6: Internet Protocol version 6 is the network-layer protocol that replaces IPv4's 32-bit ...

Nov 4, 2026, 8:52:25 AM [Read more](https://blog.blazingcdn.com/en-us/what-is-ipv6-ipv6-vs-ipv4-and-why-it-matters?hsLang=en-us)

[![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-05-45-38-9119-AM.jpeg)](https://blog.blazingcdn.com/en-us/what-is-a-network-port-ports-80-and-443-explained?hsLang=en-us)

Infrastructure

### [What Is a Network Port? Ports 80 and 443 Explained](https://blog.blazingcdn.com/en-us/what-is-a-network-port-ports-80-and-443-explained?hsLang=en-us)

The short answer to what is a port: a network port is a 16-bit number, from 0 to 65535, carried in every TCP and UDP ...

Nov 4, 2026, 6:47:39 AM [Read more](https://blog.blazingcdn.com/en-us/what-is-a-network-port-ports-80-and-443-explained?hsLang=en-us)

[![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-03-40-38-3827-AM.jpeg)](https://blog.blazingcdn.com/en-us/dns-propagation-why-dns-changes-take-time?hsLang=en-us)

Infrastructure

### [DNS Propagation: Why DNS Changes Take Time](https://blog.blazingcdn.com/en-us/dns-propagation-why-dns-changes-take-time?hsLang=en-us)

DNS propagation is the window after a record change during which recursive resolvers, operating system caches and ...

Nov 4, 2026, 4:42:52 AM [Read more](https://blog.blazingcdn.com/en-us/dns-propagation-why-dns-changes-take-time?hsLang=en-us)

[![](https://blog.blazingcdn.com/hubfs/Gemini-Blog/image-Nov-04-2026-01-35-38-5774-AM.jpeg)](https://blog.blazingcdn.com/en-us/dns-records-explained-a-aaaa-cname-txt-and-more?hsLang=en-us)

Infrastructure

### [DNS Records Explained: A, AAAA, CNAME, TXT and More](https://blog.blazingcdn.com/en-us/dns-records-explained-a-aaaa-cname-txt-and-more?hsLang=en-us)

DNS records are typed entries in an authoritative zone that map a name to data. An A record returns a 32-bit IPv4 ...

Nov 4, 2026, 2:37:32 AM [Read more](https://blog.blazingcdn.com/en-us/dns-records-explained-a-aaaa-cname-txt-and-more?hsLang=en-us)

[![BlazingCDN](https://blog.blazingcdn.com/hubfs/Logo/blog-logo-w.png)](https://blog.blazingcdn.com?hsLang=en-us)

[📘 Learn](https://blog.blazingcdn.com/cdn-learn?hsLang=en-us) [📊 Benchmarks](https://blog.blazingcdn.com/cdn-ratings-and-benchmarks?hsLang=en-us) [🎬 Video & Streaming](https://blog.blazingcdn.com/video-streaming-cdn?hsLang=en-us) [🏭 Industries](https://blog.blazingcdn.com/cdn-industry-insights?hsLang=en-us) [💰 Pricing & Costs](https://blog.blazingcdn.com/cdn-pricing-and-cdn-costs?hsLang=en-us) [⚡ Compare](https://blog.blazingcdn.com/cdn-comparison?hsLang=en-us) [🔒 Security](https://blog.blazingcdn.com/cdn-security?hsLang=en-us) [🛠️ Tools](https://blog.blazingcdn.com/cdn-tools?hsLang=en-us) [✍️ Publish with us](https://blog.blazingcdn.com/publish-with-us?hsLang=en-us)

in f 𝕏 ✉

 Copyright © BlazingCDN |. All rights reserved.

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blazingcdn.com/#organization",
  "@type" : "Organization",
  "description" : "High-volume CDN for video, live streaming, OTT/IPTV, software, games, SaaS and large-file delivery.",
  "logo" : {
    "@id" : "https://blazingcdn.com/#logo",
    "@type" : "ImageObject",
    "height" : 560,
    "url" : "https://blazingcdn.com/wp-content/uploads/2024/08/logo-560-560.png",
    "width" : 560
  },
  "name" : "BlazingCDN",
  "sameAs" : [ "https://www.linkedin.com/company/blazingcdn", "https://x.com/BlazingCdn", "https://www.reddit.com/r/BlazingCDN/", "https://www.wikidata.org/wiki/Q141711074" ],
  "url" : "https://blazingcdn.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/#website",
  "@type" : "WebSite",
  "inLanguage" : "en-US",
  "name" : "BlazingCDN Blog",
  "publisher" : {
    "@id" : "https://blazingcdn.com/#organization"
  },
  "url" : "https://blog.blazingcdn.com/"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples#article",
  "@type" : "BlogPosting",
  "author" : {
    "@id" : "https://blog.blazingcdn.com/en-us/author/blazingcdn#person",
    "@type" : "Person",
    "description" : "Vadym Borovskyi is Chief Product and Marketing Officer at BlazingCDN, where he has led product strategy and growth since 2021. He has more than 11 years of experience in IT product management and B2B marketing. On this blog he writes about CDN pricing and egress costs, video and software delivery, cache configuration, and how teams evaluate and switch CDN providers. He is based in Warsaw, Poland.",
    "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/vadym-borovskyi.jpg",
    "jobTitle" : "Chief Product and Marketing Officer",
    "knowsAbout" : [ "Content Delivery Networks (CDN)", "CDN pricing", "Video streaming delivery", "Software and game distribution", "Cache optimization", "Product Management", "B2B Marketing", "Digital Marketing", "Pay Per Click Marketing (PPC)", "Google Ads", "Search Engine Marketing (SEM)", "Marketing Strategy", "Artificial Intelligence (AI)", "Cloud Management", "SaaS Development", "IT Consulting", "Computer Networking", "Project Management", "Startups" ],
    "name" : "Vadym Borovskyi",
    "sameAs" : [ "https://www.linkedin.com/in/axelt/" ],
    "url" : "https://blog.blazingcdn.com/en-us/author/blazingcdn",
    "worksFor" : {
      "@id" : "https://blazingcdn.com/#organization"
    }
  },
  "dateModified" : "2026-11-09T14:45:11Z",
  "datePublished" : "2026-11-03T04:48:24Z",
  "description" : "Explore the OSI model, its 7 layers, and real-world examples to understand how networks communicate.",
  "headline" : "The OSI Model Explained: 7 Layers With Real Examples",
  "image" : "https://143144902.fs1.hubspotusercontent-eu1.net/hubfs/143144902/Gemini-Blog/image-Nov-03-2026-04-45-37-9940-AM.jpeg",
  "inLanguage" : "en-us",
  "isPartOf" : {
    "@id" : "https://blog.blazingcdn.com/#website"
  },
  "mainEntityOfPage" : {
    "@id" : "https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@id" : "https://blazingcdn.com/#organization"
  },
  "wordCount" : 2347
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples#breadcrumb",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://blog.blazingcdn.com/en-us",
    "name" : "Blog",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples",
    "name" : "The OSI Model Explained: 7 Layers With Real Examples",
    "position" : 2
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://blog.blazingcdn.com/en-us/osi-model-explained-7-layers-with-real-examples#faq",
  "@type" : "FAQPage",
  "mainEntity" : [ {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "From bottom to top, the 7 layers of the OSI model are physical, data link, network, transport, session, presentation and application. Real protocols sit at most of them: Ethernet at layer 2, IPv4 and IPv6 at layer 3, TCP and UDP at layer 4, HTTP and DNS at layer 7. Layers 5 and 6 are largely absorbed into TLS and application libraries."
    },
    "name" : "What are the 7 layers of the OSI model in order?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "A CDN edge is a layer 7 system, because caching requires parsing HTTP: the cache key comes from host, path, query string and Vary headers. Most CDNs also work at layer 3, using Anycast or DNS steering to pick a site, and at layer 4 inside each site, where balancers spread connections across cache servers."
    },
    "name" : "Is a CDN layer 4 or layer 7 in the OSI model?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "TLS does not fit a single OSI layer. It provides encryption, a presentation-layer function, and session resumption, a session-layer function, yet it runs on top of TCP and below HTTP. Engineers usually call it layer 4.5 or group it with layer 7, because the device terminating TLS is the only one able to read HTTP."
    },
    "name" : "Which OSI layer does TLS belong to?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "QUIC performs layer 4 transport functions inside UDP datagrams and embeds the TLS 1.3 handshake, while HTTP/3 is the layer 7 protocol running on top. A layer 4 balancer sees QUIC only as UDP on port 443, so stable routing requires reading the QUIC connection ID, since client addresses can change during a connection."
    },
    "name" : "Where do QUIC and HTTP/3 fit in the OSI model?"
  }, {
    "@type" : "Question",
    "acceptedAnswer" : {
      "@type" : "Answer",
      "text" : "Layer 3 balancing steers traffic by destination IP, through Anycast routes or ECMP next hops, while layer 4 balancing tracks individual TCP or UDP flows by their 5-tuple. The boundary blurs in practice: ECMP routers hash on ports, which are layer 4 fields, even though they are layer 3 devices that keep no per-flow state."
    },
    "name" : "What is the difference between layer 3 and layer 4 load balancing in the OSI model?"
  } ]
}
```