惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
E
Exploit-DB.com RSS Feed
Google DeepMind News
Google DeepMind News
F
Full Disclosure
D
Darknet – Hacking Tools, Hacker News & Cyber Security
T
ThreatConnect
Stack Overflow Blog
Stack Overflow Blog
Last Week in AI
Last Week in AI
Martin Fowler
Martin Fowler
G
GRAHAM CLULEY
C
Check Point Blog
T
Threatpost
I
Intezer
Spread Privacy
Spread Privacy
The Register - Security
The Register - Security
Project Zero
Project Zero
月光博客
月光博客
人人都是产品经理
人人都是产品经理
阮一峰的网络日志
阮一峰的网络日志
D
DataBreaches.Net
IT之家
IT之家
Malwarebytes
Malwarebytes
T
The Blog of Author Tim Ferriss
P
Privacy International News Feed
P
Palo Alto Networks Blog
T
The Exploit Database - CXSecurity.com
量子位
李成银的技术随笔
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Cisco Talos Blog
Cisco Talos Blog
Know Your Adversary
Know Your Adversary
美团技术团队
The GitHub Blog
The GitHub Blog
T
Tor Project blog
M
MIT News - Artificial intelligence
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Google Online Security Blog
Google Online Security Blog
P
Proofpoint News Feed
有赞技术团队
有赞技术团队
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
C
Comments on: Blog
T
Threat Research - Cisco Blogs
aimingoo的专栏
aimingoo的专栏
Security Latest
Security Latest
NISL@THU
NISL@THU
The Cloudflare Blog
H
Help Net Security
Recent Commits to openclaw:main
Recent Commits to openclaw:main

The Cloudflare Blog

The day my ping took countermeasures Announcing Claude Compliance API support with Cloudflare CASB Announcing Claude Managed Agents on Cloudflare Project Glasswing: what Mythos showed us Our billing pipeline was suddenly slow. The culprit was a hidden bottleneck in ClickHouse Browser Run: now running on Cloudflare Containers, it’s faster and more scalable When "idle" isn't idle: how a Linux kernel optimization became a QUIC bug Building For The Future How Cloudflare responded to the “Copy Fail” Linux vulnerability When DNSSEC goes wrong: how we responded to the .de TLD outage Code Orange: Fail Small is complete. The result is a stronger Cloudflare network Introducing Dynamic Workflows: durable execution that follows the tenant Post-quantum encryption for Cloudflare IPsec is generally available Agents can now create Cloudflare accounts, buy domains, and deploy Shutdowns, power outages, and conflict: a review of Q1 2026 Internet disruptions Making Rust Workers reliable: panic and abort recovery in wasm‑bindgen Moving past bots vs. humans Building the agentic cloud: everything we launched during Agents Week 2026 The AI engineering stack we built internally — on the platform we ship Orchestrating AI Code Review at scale Introducing the Agent Readiness score. Check to see if your site is agent-ready Shared Dictionaries: compression that keeps up with the agentic web Redirects for AI Training enforces canonical content Unweight: how we compressed an LLM 22% without sacrificing quality Agents that remember: introducing Agent Memory Agents Week: network performance update Introducing Flagship: feature flags built for the age of AI Cloudflare’s AI Platform: an inference layer designed for agents Building the foundation for running extra-large language models AI Search: the search primitive for your agents Deploy Postgres and MySQL databases with PlanetScale + Workers Artifacts: versioned storage that speaks Git Email for agents - Cloudflare Email Service now in public beta Project Think: building the next generation of AI agents on Cloudflare Introducing Agent Lee - a new interface to the Cloudflare stack Register domains wherever you build: Cloudflare Registrar API now in beta Browser Run: give your agents a browser Rearchitecting the Workflows control plane for the agentic era Add voice to your agent Managed OAuth for Access: make internal apps agent-ready in one click Securing non-human identities: automated revocation, OAuth, and scoped permissions Scaling MCP adoption: Our reference architecture for simpler, safer and cheaper enterprise deployments of MCP Secure private networking for everyone: users, nodes, agents, Workers — introducing Cloudflare Mesh Building a CLI for all of Cloudflare Durable Objects in Dynamic Workers: Give each AI-generated app its own database Agents have their own computers with Sandboxes GA Dynamic, identity-aware, and secure Sandbox auth Welcome to Agents Week 500 Tbps of capacity: 16 years of scaling our global network From bytecode to bytes- automated magic packet generation Cloudflare targets 2029 for full post-quantum security How we built Organizations to help enterprises manage Cloudflare at scale Why we're rethinking cache for the AI era Our ongoing commitment to privacy for the 1.1.1.1 public DNS resolver Introducing EmDash — the spiritual successor to WordPress that solves plugin security Introducing Programmable Flow Protection: custom DDoS mitigation logic for Magic Transit customers Cloudflare Client-Side Security: smarter detection, now open to everyone How we use Abstract Syntax Trees (ASTs) to turn Workflows code into visual diagrams A one-line Kubernetes fix that saved 600 hours a year Sandboxing AI agents, 100x faster Inside Gen 13- how we built our most powerful server yet Launching Cloudflare’s Gen 13 servers- trading cache for cores for 2x edge compute performance Powering the agents: Workers AI now runs large models, starting with Kimi K2.5 Introducing Custom Regions for precision data control Standing up for the open Internet- why we appealed Italy’s Piracy Shield fine From legacy architecture to Cloudflare One Announcing Cloudflare Account Abuse Protection: prevent fraudulent attacks from bots and humans Slashing agent token costs by 98% with RFC 9457-compliant error responses AI Security for Apps is now generally available Building a security overview dashboard for actionable insights Investigating multi-vector attacks in Log Explorer Translating risk insights into actionable protection: leveling up security posture with Cloudflare and Mastercard Fixing request smuggling vulnerabilities in Pingora OSS deployments Active defense: introducing a stateful vulnerability scanner for APIs Complexity is a choice. SASE migrations shouldn’t take years. From the endpoint to the prompt: a unified data security vision in Cloudflare One Ending the "silent drop": how Dynamic Path MTU Discovery makes the Cloudflare One Client more resilient A QUICker SASE client: re-building Proxy Mode How Automatic Return Routing solves IP overlap Always-on detections: eliminating the WAF “log versus block” trade-off Mind the gap: new tools for continuous enforcement from boot to login Stop reacting to breaches and start preventing them with User Risk Scoring Defeating the deepfake: stopping laptop farms and insider threats Moving from license plates to badges: the Gateway Authorization Proxy Evolving Cloudflare’s Threat Intelligence Platform: actionable, scalable, and ETL-less Introducing the 2026 Cloudflare Threat Report See risk, fix risk: introducing Remediation in Cloudflare CASB How Cloudy translates complex security into human action From reactive to proactive: closing the phishing gap with LLMs Modernizing with agile SASE: a Cloudflare One blog takeover Beyond the blank slate: how Cloudflare accelerates your Zero Trust journey The truly programmable SASE platform Toxic combinations: when small signals add up to a security incident We deserve a better streams API for JavaScript The most-seen UI on the Internet? Redesigning Turnstile and Challenge Pages ASPA: making Internet routing more secure Bringing more transparency to post-quantum usage, encrypted messaging, and routing security How we rebuilt Next.js with AI in one week Cloudflare One is the first SASE offering modern post-quantum encryption across the full platform Cloudflare outage on February 20, 2026
Thoughts on Network Neutrality, the FCC, and the Future of Internet Governance
Cloudflare Team · 2015-02-27 · via The Cloudflare Blog

2015-02-27

7 min read

Today the United States Federal Communications Commission (FCC) voted to extend the rules that previously regulated the telephone industry to now regulate Internet Service Providers (ISPs). The Commission did this in order to preserve the principle of network neutrality. Broadly stated, this principle is that networks should not discriminate against content that passes through them.

At CloudFlare, we are strong proponents of network neutrality. My co-founder, Michelle Zatlyn, sat on the FCC's Open Internet Advisory Committee. The work of that committee played a role in guiding today's vote. So there is a large part of us that is celebrating today.

At the same time, I have deep concerns that proponents of a free and open Internet may look back on today not as a great victory, but as the first step in what may turn out to be a devastating loss. The Internet has largely been governed from the bottom up by technologists seeking rough consensus and running code. Today's action by the FCC may mark the beginning of a new era where the Internet is regulated by lawyers from the top down. As a technologist and recovering lawyer, that worries me.

The Threat to the Network

If you think about it, it's a miracle that the Internet has been as neutral as it has for as long as it has. Throughout history, owners of networks — be they shipping channels, country clubs, Ivy League colleges, banks, roads, or actual telecommunications networks — have profited by charging tolls to access those networks. The Internet has, for the most part, resisted this. There is no "long distance" charge on the Internet. You don't pay more to access one website or use one mobile app than another. Bytes, for the most part, are bytes regardless of where they come from or go to.

That is not to say there is no risk. Networks tend to be natural monopolies. Consolidation of what are known as "terminating access providers" — companies like Comcast that act as ISPs for customers — creates a choke point for the Internet. These companies are in a position to start charging not only their users but also content providers. But, to date, the number of instances of actual abuse by ISPs in the United States has been remarkably low.

Netflix

When proponents of government regulation of the Internet want to point to abuse their poster child is often Netflix. The company's fights with Comcast and other ISPs are well documented. There's little doubt that Netflix's performance suffered on some ISPs where the infrastructure serving the company's movie-streaming bytes became overloaded.

Lawyers have a saying: hard cases make bad law. Netflix is a hard case. According to the company, during primetime viewing they are responsible for more than 30% of all U.S. Internet bandwidth use. Remember that the company only launched streaming video seven years ago, and it only really took off about four years ago. In other words, the company has increased U.S. Internet use by a third — on its own — in an extremely short amount of time.

Qwikster

As a consumer, it's easy to think of the Internet as an infinite resource, but real atoms carry all those bytes and they have finite capacities. Who pays the cost of delivering that additional 30% of traffic is not straight forward. While it's tempting to say that an ISP like Comcast should pay, is it fair, then, for them to spread that cost over all Comcast subscribers regardless of whether they are Netflix subscribers?

Again, because of their remarkable scale and the rate of growth, Netflix makes for an extremely hard case and therefore a tricky poster child. In the end, assuming the whisper numbers are correct on the terms, the commercial arrangement worked out between ISPs and Netflix seems from my perspective to have been a pretty reasonable outcome. The market worked here when giants battled. However, I worry about the non-giants who so far haven't been poster children.

The Internet Miracle

The good news is that beyond the exceptional case of Netflix, other abuses of the principle of network neutrality have proven more difficult to find. By in large, today on the Internet, bytes are bytes. CloudFlare delivers a large number of bytes and, so far, we have never been "shaken down" by an ISP in order reach their customers. Quite the opposite, as we've grown our cost of delivering a byte has rapidly decreased. In the last 12 months, our global blended average per byte cost has fallen by half, even as we've expanded in expensive markets like Australia, Latin America, and Africa.

That's not to say I don't worry. I worry a lot. Comcast, or other large ISPs, could likely extract tolls from a company like ours if they threatened to rate limit or outright block their customers from reaching our network. Legally, before today's FCC vote, there was likely no rule that stopped them. And yet, to date, in spite of their market power, the bottoms-up, normative approach to Internet governance has largely kept ISPs in check and kept the network neutral. This arrangement feels fragile and likely won't last forever, but up until now, I think this is rightly described as the Internet miracle.

The Challenge of Regulating Technology

There is always tension between law and technology. Technology moves fast. Law moves slow. Technology is nimble. Law is a lumbering beast. I like to joke that my job as a lawyer and a programmer were the same: in both cases I was writing code, just as a lawyer it took 10 years and an expensive legal trial for the compiler to let me know if I had a bug.

Bad things happen when lawyers and politicians step in too early to regulate technology markets that are still developing. In this case, the FCC not only may be stepping in too early — before we know what the actual, not just theoretical, problems they aim to regulate will be — but they were forced by previous court decisions and political realities to apply the rules written for traditional telephone networks rather than craft a new regulation specific to the unique nature of the Internet.

The exact rules the FCC just voted for are not yet public, and we don't know exactly what they will contain. What we do know, however, is that they will stem from Title II of the Federal Telecommunications Act. The problem is that Telecommunications Act comes with 80 years of baggage. The Act, which was originally passed in 1934 under the Franklin D. Roosevelt administration, has been interpreted by courts and rewritten by Congress a multitude of times. For the programmers reading this, what the FCC is doing is like trying to compile Node.js on MS-DOS. Even if they get it to work, inevitably there will be unintended consequences.

Rules Versus Standards

Montana Speed Limit: Reasonable & Prudent

There is a philosophical debate in the law about the role of "rules" versus "standards." For quite some time, in the United States, most roads have had a defined speed limit: say 55 miles per hour. That's a rule. Some stretches of road in Montana were different. There the speed limit was listed as "reasonable and prudent" speed. In some cases, say during a sunny day on a straight, clear road, what is "reasonable and prudent" may be a lot faster than 55 mph. On the other hand, if it's snowing, 55 mph may be far faster than "reasonable and prudent." Montana, in other words, set a standard, not a rule, for their speed limit.

Generally, when conditions are well defined, and the optimal outcome is known, then rules are appropriate. When the conditions are more uncertain and the optimal outcome is unknown, then standards are appropriate. I worry that the FCC is about to set down a series of rules for network neutrality before the real threat and the optimal outcome is known.

The other problem with rules is that they are brittle. Teams of lawyers will comb through whatever the FCC finally publishes and find any loopholes. There will be defined bright lines going forward and, make no mistake, ISPs will now get as close to those lines as they can. Whatever the Internet's rough consensus of "acceptable" was before, it's about to be thrown out in favor of a set of rules written by lawyers. Ironically, that may end up resulting in a regulated network that is less neutral than what we have today.

What I Wish the FCC Had Done

Setting aside political realities, I wish the FCC had done something quite different today. In my ideal alternate universe the FCC chairman would have given something like the following speech:

The Internet is one of the greatest inventions in human history. What has made the Internet great is that anyone, anywhere can publish an idea and reach a global audience. Incumbent on us preserving that Internet ideal is that the providers that make up the Internet not discriminate against one idea or another; not favor one byte flowing across their network or disfavor another. This principle of network neutrality is core to the continued success of the Internet.

_

We, as the FCC, are stewards of the communications systems in the United States. The policies of the United States also serve as a precedent for network regulators throughout the rest world. As such, when we act, we must do so with extreme care. To date, the Internet has been governed by a consensus-drive, bottom-up approach. That approach has succeeded in creating the most open, accessible network in human history. Our actions should serve to strengthen, not replace, that approach.

That said, there are real concerns about the increasing market power of Internet Service Providers. These providers hold a 100% monopoly on delivering content to each of their customers. Abusing that monopoly position is unacceptable and we, as the FCC, will not tolerate it. We hold, under Title II of the Federal Communications Act, broad powers to crack down on providers that are abusing their trusted position on the network. If we find abuses, ISPs be warned: we will not hesitate to use the full extent of our power.

Today, we are articulating a simple standards on network neutrality to which all ISPs will be held:

  • Providers should not discriminate against or for any byte flowing across their network

  • Providers should continue to invest in their networks to provide higher quality of service across the entire Internet

  • Providers should not offer so-called "fast lanes" that content providers may purchase in order to favor their own content

_

To monitor compliance with this standard, I have hired a team of 100 investigators who will be fielding complaints around the clock from consumers and businesses about ISPs that fail to live up to these standards. We will take allegations of ISPs that do not follow these standards seriously and investigate them to the fullest extent. Non-neutral networks will be put through the equivalent of a legal root canal. And if we find that our current legal framework does not offer the tools to remedy abuses, make no mistake that we can and will act quickly under our full powers of Title II. To ISPs: you're on notice. To Internet users: we will be vigilant.

Oliver Wheeler Dingo

Now, of course, that would satisfy no one. John Oliver would take to his HBO show to yet again call Chairman Wheeler a do-nothing "dingo." But, I have a hunch, ISPs would actually act more cautiously and self-police out of fear they incur the full wrath of an FCC armed with specific consumer complaints. The risk of setting bad rules with their unintended consequences would be diminished. And, for at least a bit longer, we may preserve the Internet miracle: where technologists make decisions from the bottom up by rough consensus and running code, guided by the principle that any idea from anyone should be able to reach a global audience.

FCCNet NeutralityPolicy & LegalPolitics