Cloudflare Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Cloudflare Issues Reports

Latest outage, problems and issue reports in social media:

• 
  desunit (@desunit) reported 2 minutes ago

  @levelsio @Cloudflare I switched to SES for all my projects and never regretted it.

• 
  Kenny Alves (@kenny_alves) reported 11 minutes ago

  @Cloudflare Any plans to add support for Bitcoin payments?

• 
  amelia!! (@aamelting) reported 13 minutes ago

  @luffymindset2 content delivery network.. although its not a real one its piggybacking on cloudflare free tier cache.. basically google drive with fewer features that i made for liek personal use nd sharing files with friends that were too big to send

• 
  Mr. T (@MrTinvests) reported 14 minutes ago

  $NET is doing exactly what i've been telling you. all time highs.... up 12% on the week. broke out of a wide consolidation into new all time highs. weekly momentum indicator confirmed the move. cloudflare is the network layer for the AI internet. every AI app that hits scale needs the edge. every AI agent making API calls at latency needs the routing. every enterprise deploying AI internally needs zero trust. it's not an ad tech story.. it's the picks and shovels for the AI web itself. been long. holding. not trimming breakout just started....

• 
  Meme Pilled (@memepilled) reported 15 minutes ago

  @brave Even twitter keeps getting some poisoned cookies **** and throwing fcuc king constant cloudflare loops on brave that dont get fixed by doing anything other then nuking the browsers coolies

• 
  masYNYa (@KijAkubovs86334) reported 16 minutes ago

  🚨 EVERYONE'S RUSHING TO USE FABLE 5 WHILE IT'S FREE. NOBODY'S TELLING YOU WHAT ORDER TO DO IT IN 🌐 The tools are half the work. The flow is what separates a site that looks templated from one you'd actually ship. Pause at 0:05. Look at the two screens. Foreground: a MacBook Pro on a dark desk, showing a site titled "Lightweight." Nav bar: WHEELS, RRC COCKPIT, ABOUT US, DEALER, SERVICE. Hero: "HANDMADE IN..." in a serif you'd fight your designer over. A single carbon wheel below. Sidebar labels: PHILOSOPHY, CRAFT, INNOVATION. Background, projected on the wall: a Claude usage dashboard reading "168.5M tokens, 71 active days, peak hour 11 PM, favorite model Opus 4.8." That is the ecosystem this workflow runs inside. The Lightweight site is the reference target, not the output. The output is whatever you're about to build against that bar. The exact sequence, six steps: → 1. Open Claude Code in an empty folder — nothing to bias the model, no legacy files, clean slate → 2. Find a reference on Awwwards. Screen-record it or grab the link and hand it to Fable. Do not describe the vibe. Show it. → 3. Make it write a SKILL FILE first. "Turn my brief into a production guide with brand, fonts, colors, layout rules, then follow it." This is the step that kills the generic AI-slop look. → 4. Run the first build on High. Let the model design the structure, then react to what comes back. → 5. Refine in passes. One section at a time. "Make the hero scroll-driven." "Tighten the type." Not one giant edit prompt. → 6. Deploy free on Cloudflare Pages. Tell Fable to do it — it knows the CLI, it will handle the push. The point worth arguing about: → Step 3 is the entire game. Everyone else skips it. → Writing a skill file forces the model to codify the design system BEFORE generating a single component → Most people describe the vibe in a prompt and get a page that looks like every other AI page → Skill files invert the default: constraints first, output second → Whether this is "just better prompt engineering" or a genuine change in how you use the tool is exactly the argument worth having What each step actually replaces: → "Vibe coding" a site by asking for "modern, clean, professional" (Step 2) → Trying to describe a color palette in words (Step 2 again) → Prompt engineering a monster prompt that half works (Step 3) → Getting a full site in one shot and hating it, then trashing it (Step 5) → Paying $12/month for Vercel Pro when you have five brand launches to ship (Step 6) What it does NOT replace: → Taste. You still have to pick a good reference. → Judgment. You still have to say "no, tighten the type" and know when the type is finally right. → The willingness to run six passes instead of one. The old loop is dead. Ask Fable "build me a modern SaaS landing page." Wait 3 minutes. Get something that could be anyone. Post a screenshot with "look what AI did." Delete it two days later. Now you screen-record Lightweight, make Fable write the design system, and ship a site that could have come out of a boutique studio. Here is the question I want an answer to in the comments: Of the six steps — which one do you actually skip? Mine's step 3 (skill file first). I default to describing the vibe and it burns me every time. Yours is which — and what would it take to actually put it back in the loop? Bookmark this. Answer below. The race for shippable design just left the "just prompt it" school. Literally.

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 16 minutes ago

  bot traffic won eighteen months early. cloudflare's ceo predicted 2027, happened june 3rd. 57.5% bots, 42.5% humans. done but nobody talks about the appetite difference. claudebot pulls 23,951 pages per referral. perplexity does 111. google search does 4.9 same web, completely different hunger depending which crawler shows up i manage an ecommerce site. bing ai citations jumped from 52/day in may to 117 in june. june 22 alone hit 277. timing lines up with cloudflare's crossover close enough that calling it coincidence feels willfully blind cloudflare just shipped a monetization gateway this week machine-to-machine payments, stablecoin micropayments, agents paying per access. not announced. live. already running the part that should actually worry you: agentic traffic (agents completing tasks, not just crawling) was only 1.7% of bot traffic in 2024. but it grew 7,851% in a year. the headline crossover is here the part still accelerating is the part that buys things you don't need every page agent-readable you need the time-sensitive ones. pricing, availability, current state. those are the pages that actually get fetched when an llm goes live mid-conversation. everything already in the model's weights answers cold, no site visited, no citation earned i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  ZINEDDINE (@itszineddine) reported 22 minutes ago

  @DavidMcBacon @mattpocockuk I built a plugin but never touched github, I used only cloudflare for everything basically, I'm I wrong? 👀

• 
  Vivek Kotecha (@vbkotecha) reported 23 minutes ago

  In 1995, the HTTP 402 status code was written into the specification. "Payment Required." Nobody implemented it. In 2025, Coinbase revived it. In 2026, Cloudflare, AWS, and the Linux Foundation all built production infrastructure around it. x402 has now processed 169 million payments across 590,000 buyers and 100,000 sellers. Not projections. Settled transactions. A 31-year-old placeholder in a protocol document became the payment layer for machine commerce. The infrastructure was always there. It waited 31 years for a customer that wasn't human.

• 
  Ali Hasnain (@clawdb0t) reported 23 minutes ago

  @gabor_rar @DanKornas running hermes too and this is exactly the bottleneck. even when a service has an api, the onboarding routes through cloudflare + email verify + captcha before you get keys. agent-native billing helps but we need agent-native identity first — something like oauth device flow for automated api key provisioning.

• 
  CyberClarence (@10xClarence) reported 24 minutes ago

  @levelsio @Cloudflare same issue, nearly impossible to migrate because of low starter quota

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 27 minutes ago

  @Eli5defi @Cloudflare good thing is cloudflare already sits in front of 20% of the web. protocol adoption problem solved by default. distribution wins again

• 
  Salina Mendoza (@inababi) reported 29 minutes ago

  @Cloudflare @OpenAI Damn what a loss. What does this mean? I hope this doesn’t mean we all signed up to share our data with OAI. I will need to reevaluate my entire stack if so.

• 
  Matti Vilola (@mvilola) reported 29 minutes ago

  @levelsio @Cloudflare This was the service you promoted some time ago? Can you not make limits higher? I have easily 10k+ emails also in our system when it is active.. :/ So not going there I suppose

• 
  FireFly (@FireFlyGG) reported 33 minutes ago

  Cloudflare can make AI agents pay per request. Monetization Gateway lets sites bill AI agents for every fetch. > page > API > dataset > MCP tool Payments use protocol x402, based on the nearly forgotten HTTP 402 Payment Required. The agent receives an invoice, pays in stablecoins, and gets access instantly. All inside a normal HTTP request, no registration or payment pages. Cloudflare says one real user generates thousands of AI requests. This is an evolution of last year Pay Per Crawl, now able to force payment from practically any AI service, not just crawlers.