Evidence — NoFlare.org

April 3, 2026 · Live Incident

The incident on record

⚠

This is a documented, timestamped event — not a complaint. Every item below is evidenced by email headers, support ticket numbers, and browser screenshots with UTC timestamps. The record is open.

April 3, 2026 · 05:02 UTC

Warning email received

Cloudflare sends automated notification: account at 90% of daily Workers request limit (100,000 req/day). Limit resets April 4 at 00:00 UTC. Standard warning; no action required.

April 3, 2026 · Morning

Payment attempted — 10+ times across 4 methods

Three credit cards and PayPal, more than ten separate payment attempts. Each rejected with "An unexpected error occurred while processing your payment." No explanation, no error code, no path to resolution.

April 3, 2026 · 10:05 UTC

Support ticket filed — Case #02055919

Ticket opened: "I have tried 4 payment methods. I am unable to submit payment for Workers due to this ongoing issue despite more than 10 attempts." Cloudflare sends auto-acknowledgment. No human response follows.

April 3, 2026 · 17:45–17:53 UTC

All 164 domains taken offline — no notification

Error 1027 begins appearing across all domains simultaneously. "This website has been temporarily rate limited." Zero email notification sent. Zero update to Case #02055919. The company that emails at 90% goes silent at 100% — while a billing support ticket sits open.

April 3, 2026 · 11:45 PT (ongoing)

Sites remain down · No response · Payment still blocked

Three facts remain true simultaneously: every site is offline, payment cannot be submitted, and Cloudflare has not responded to the support ticket they confirmed receiving.

Cloudflare billing error — April 3, 2026

EXHIBIT A — Cloudflare billing portal · April 3, 2026 · PayPal rejected alongside 3 credit cards · Case #02055919

The payment paradox

Cloudflare blocked their own payment gateway across four separate payment methods while simultaneously enforcing limits that require payment to resolve. The customer is trapped in a loop with no exit path.

Selective notification

Cloudflare sent an automated email at 90% of limit. They sent nothing when they crossed 100% and terminated all traffic. A company that emails at 90% and goes silent at 100% is making a deliberate choice.

No due process

164 domains — representing a civic infrastructure network for greater Seattle — taken offline in a single automated action. No warning. No grace period. No appeal path. No human on record.

"A website is speech. It is not a bomb." — Matthew Prince, Cloudflare CEO, 2012 (on not taking down websites)

The Operator

Matthew Prince — the documented affiliations

Origin: Built on a government intelligence sale

Project Honey Pot — Prince's pre-Cloudflare surveillance network tracking malicious IP addresses — was sold to the U.S. Department of Homeland Security in 2008. The DHS asked: "Do you have any idea how valuable the data you have is?" That transaction became the founding thesis of Cloudflare.

The company was not born of market demand. It was born of intelligence validation.

The affiliation stack

◈

Council on Foreign Relations

Member — Prince personally. Also: Chief Legal Officer Doug Kramer (lifetime member, former Obama White House Staff Secretary and Deputy Assistant to the President).

◈

World Economic Forum

Technology Pioneer designation. Regular Davos participant and speaker.

◈

CISA / U.S. Government

$7.2M contract to control authoritative DNS for the entire .gov top-level domain. 40+ federal agencies served. Protective DNS resolver for all Federal Civilian Executive Branch agencies.

◈

Institutional Holders

Vanguard, BlackRock, Fidelity, T. Rowe Price, State Street — the standard constellation of permanent capital. Prince retains operational control through super-voting Class B shares regardless.

The gate, documented

Cloudflare now intermediates between the open internet and 21% of all websites globally. It controls the DNS that routes every .gov domain. It holds intelligence-sharing agreements with the federal government that make it the conduit through which state threat intelligence flows into the private sector.

Prince's own words on the government partnership: "threat intelligence that was previously exclusively the government's" now flows through Cloudflare to the private sector. He is the intermediary.

          # The founding sequence

          2004 → Build surveillance network (Project HoneyPot)

          2008 → Sell intelligence to DHS

          2009 → Found Cloudflare on that validation

          2010 → Launch publicly at TechCrunch Disrupt

          2019 → IPO at $15/share; dual-class voting locked

          2021 → CISA contract: protective DNS for all FCEB

          2023 → Win .gov TLD registry contract ($7.2M)

          2026 → Controls 21% of internet · 40+ fed agencies

          # April 3: 164 civic domains offline, no notice

◈

Note: This pattern was publicly identified and documented in 2019 — seven years before today's event. The analysis is not reactive. It is confirmed.