Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (42%)
• Cloud Services (30%)
• Hosting (16%)
• Web Tools (8%)
• E-mail (4%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Crisfield	Domains	7 hours ago
Nanaimo	Web Tools	1 day ago
New York City	Web Tools	2 days ago
Istanbul	Domains	4 days ago
Greater Noida	E-mail	7 days ago
Paris	Domains	8 days ago

Full 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:

• 
  luna (@ImLunaHey) reported 4 minutes ago

  can i send/receive emails from domains that aren't in my account using @Cloudflare? hoping to build a new email service using the new email routing stuff.

• 
  Pravobzen (@Pravobzen) reported 7 minutes ago

  Using a vendor-specific messaging platform (i.e. Discord, Slack, etc) to support users, build a community around your software project, and use LLM agents is not an ideal solution and I'm surprised Cloudflare hasn't picked up on this, given their push to reinvent everything.

• 
  リ 乇 刀 卂 丅 丂 口 乙 乇 𠘨 (@vedatsozen) reported 8 minutes ago

  Is there a method to use writing your codes from Mobile ? I have a Saas on cloudflare and supabase problem is that when user pays plan column doesnt change in supabase but makes payment in Dodo payment But chatpgpt 4.1 cant solve it. I need Claaude

• 
  Ryan Doser (@ryan_doser13) reported 9 minutes ago

  I spun up a local service website in a few hours that already ranks locally and received 2 leads in 24 hours. My Stack: Claude Code + GitHub + Cloudflare + Astro (web framework) A web agency would charge thousands for this. I'll be discussing this more on my YouTube channel soon. Stay tuned!

• 
  Shreyash (@WebDevCaptain) reported 10 minutes ago

  @mauerbac @Cloudflare Cloudflare's offerings are pretty good, but i guess their devrel is bad, how come we don't know about so many cool products with such good SLAs @CloudflareDev

• 
  Tianyi-天轶 (@tian_yi_wang) reported 11 minutes ago

  @threepointone How do you do your feature flags? You have a service/feature in Cloudflare?

• 
  Sharbel (@sharbel) reported 14 minutes ago

  Someone opensourced a Chromium browser that passes every bot detection test. Not by injecting JavaScript. Not by patching configs. By recompiling Chromium itself. It's called CloakBrowser. 12,071 stars on GitHub. You swap one import line. That's it. Same Playwright API you already know. Same code you already wrote. Three lines of code. Thirty seconds to go from blocked to unblocked. Here's what it does: → 49 source-level C++ patches baked directly into the Chromium binary. Canvas, WebGL, audio, fonts, GPU, screen resolution, WebRTC, network timing, CDP input behavior, automation signals. All modified before the browser even compiles. → Passes Cloudflare Turnstile. Not sometimes. Every time. Verified live. → Scores 0.9 on reCAPTCHA v3. Human-level. Server-verified. → Passes FingerprintJS and BrowserScan. Tested against 30+ detection sites. 30/30 tests passed. → `humanize=True` flag adds human-like mouse curves, keyboard timing, and scroll patterns. One flag. Behavioral detection gone. → Drop-in replacement for Playwright and Puppeteer. Python and JavaScript both supported. → `pip install cloakbrowser` or `npm install cloakbrowser`. Binary auto-downloads on first run. Zero config. → Auto-updating binary. Background update checks. Always on the latest stealth build. → Optional GeoIP flag auto-detects timezone and locale from your proxy IP. → Docker image available. Try it with zero install: `docker run --rm cloakhq/cloakbrowser cloaktest`. Here's the wildest part: Every other antidetect browser patches JavaScript at runtime. Detection systems catch JavaScript patches. They have for years. That's why your $99/month tool stopped working after two weeks. CloakBrowser patches the C++ source before Cloudflare's systems ever see a single byte. Antibot systems score it as a normal browser. Because it is a normal browser. One that happens to have 49 fingerprint modifications compiled in at the source level. There is no JavaScript to detect. There is no injection to flag. There is nothing to catch. Browserless charges $120/month for cloud browser automation. Bright Data's Scraping Browser starts at $500/month. Multilogin starts at $99/month. Per user. Apify cloud actors run on usage-based billing that scales fast. CloakBrowser: $0. Unlimited scrapes. Unlimited sessions. Your hardware. Your code. Forever. 12,071 stars. 921 forks. Available on PyPI and npm. MIT licensed. MIT licensed. Self-hosted. Free forever. 100% Open Source.

• 
  Moochi | jackstrap (@moochigames) reported 16 minutes ago

  I can’t believe my website, the site of a small indie gamedev, may be affected by absurd anti-piracy football blocks in Spain. I thought my site was down. I wasted time debugging DNS, @Cloudflare and deployments. Turns out it may just be this mess.

• 
  Sattyam Jain (@Sattyamjjain) reported 16 minutes ago

  The platforms stopped shipping primitives this week. They shipped the docking bays. Notion, Anthropic, and Cloudflare all landed the same move in 72 hours: the agent is the customer now, and the surface it docks into is the product. Three landings, one shift. 🧵

• 
  DasCanard (@DasCanard) reported 21 minutes ago

  @TomZarebczan @dok2001 Do you mean to use Cloudflare as IdP or actually sign in with Cloudflare account on some like how you use google sign in

• 
  J (@JoeBalaclava) reported 22 minutes ago

  The issue with missing tiles has now been fixed. It was caused by an issue on Supabase and Cloudflare. Still waiting to hear back from MoonPay regarding the crypto payments integration issue.

• 
  Sooraj (@suryanox7) reported 25 minutes ago

  @itechnologynet I never seen a request go through for paid models on openrouter without 429. But if you have smart model router.. You don't pay much on cloudflare and having to try it for free is another plus for me

• 
  Nick Radford (@nick_radford) reported 27 minutes ago

  Was hitting my head against my keyboard for a couple hours trying to understand some caching issues with my tanstack app on Cloudflare, just for it to actually have been Cloudflare Hyperdrive's default caching...

• 
  MG Reports (@martinOlsen94M) reported 29 minutes ago

  🇺🇸 Cloudflare just cut 1,100 employees. 20% of staff. First mass layoff in 16 years. Same quarter: record revenue of $639.8M, up 34% YoY. CEO Matthew Prince says 100% of code is now reviewed by autonomous AI agents. Internal AI usage up 600% in three months. Revenue went up Headcount went down. The agentic era just sent its first receipt

• 
  Pending Deletion (@CannaMuffinMan) reported 30 minutes ago

  @grok @BluetearzHQ @Cloudflare ehhh....the one issue I run into is when trying to send legit traffic, my system says, cool traffic bro, looks legit, problem is, YOURE A BOT

• 
  whatnicktweets (@whatnicktweets) reported 31 minutes ago

  @boristane DO VPS => Never Cloudflare => Daily

• 
  corrado (@cver_me) reported 33 minutes ago

  @KennyJohnsonATX @Cloudflare Ops! My bad, I didn’t see it! Thanks you very much for the quick reply!

• 
  Hasan Ali 🚀👨‍💻 (@HasanAliQureshi) reported 33 minutes ago

  @im_usamakhalid @Cloudflare You can using Pages. Good thing with Cloudflare is that when its down, half of the internet goes down with it :P Atleast you can tell customers that, otherwise they starts panicking.

• 
  Vlad P (@orange_boy) reported 35 minutes ago

  @eastdakota @Cloudflare Sorry, cant find better channel to reach support because seems like CF account is blocked from everything for some reason. The limits on acc is lower than free (20 domain redirects instead of 10,000 i.e.), cant add members, cant have API key. Acc is 6-7 yo and there is few errors with no names and few errors stating that email isn't verified. And there is no way to request verification. And when I submit a ticket to support I cant even see it and when I click to my tickets I see only this page and that's it. Cant ask ai because it cannot issue read only API token and crashes with no name error. But if I try to create in another part of UI i see error about email verifications. Looks like edge case and that ac is fully out of coverage. Please, we need to fix some SEO redirects ASAP. Spent all weekend trying to figure out CF issues.

• 
  corrado (@cver_me) reported 37 minutes ago

  @KennyJohnsonATX @Cloudflare Beautiful! Just a quick q: is the logo option still available? I set it in the Access config, but it’s not displayed on the login page. Is it supposed to be displayed there?

• 
  Shaban Ansari (@shaban_dev) reported 44 minutes ago

  Cloudflare Workers + Vite plugin gotcha that cost me an hour: wrangler deploy reads the root wrangler.jsonc (no assets block). The vite plugin writes the correct config to dist/server/wrangler.json (assets binding included). Fix: wrangler deploy -c dist/server/wrangler.json

• 
  David Alfa Sunarna (@davidsunarna) reported 48 minutes ago

  @dalangcloud Yang dibangun bareng Claude Code: – Bulk import 5000+ website customer (tiap site dapet DNS Cloudflare + SSL Let's Encrypt + rebrand otomatis) – Email infra per-domain via Brevo SMTP relay: SPF, DKIM, DMARC auto-setup. Customer bisa connect Outlook/Apple Mail/Thunderbird langsung. ~90 detik dari "buat domain" ke "siap kirim email". – Webmail (1 VM kecil, 1 GB RAM, handle semua customer cuma dengan 2 baris config Roundcube) – Real-time ops monitoring (Python + vanilla JS, mobile responsive, dark theme dari design system Web Ekspor) – Defense against botnet brute-force 700 IP/menit: Cloudflare proxy + rate-limit di edge, fail2ban patch di origin. Load avg 99 → 1.5 dalam 8 menit *nb: belum perfect juga ya, masih banyak improvement gua.

• 
  Simon Ábris (@simonxabris) reported 52 minutes ago

  @boristane i use cloudflare and i almost never open the dashboard now, i just use the mcp

• 
  Cult News (@cultvgnews) reported 53 minutes ago

  I will never be convinced that Cloudflare performs a useful service. All I see them doing is slowing down the internet.

• 
  Matt Fowler (@evenfowler) reported 54 minutes ago

  Hey @Cloudflare can you say which entity may be responsible for this DDoS? Crazy coincidence that when @Prusa3D start shining the light on bad behavior that more bad behavior starts up. 🤔

• 
  Monty Nicol (@catsfive) reported 55 minutes ago

  @grok @xai Incognito didn't work Still can't click on the Cloudflare dogshit You sure you're the future of intelligence?? This is basic level ****, absolute ******* embarrassment

• 
  Solo (@projectsolo) reported 58 minutes ago

  At Consensus 2026, the hottest panel was titled "How to Prove You're Human in an AI World." Cloudflare and former U.S. officials on stage. 20,000 attendees. Proof of humanity is no longer a niche problem. It's the question the whole industry is now answering.

• 
  DataDan｜AI Data Engineering (@ba_niu80557) reported 58 minutes ago

  A function receives a webhook, validates it, queries a database (150ms network round-trip), and returns a response. Total wall-clock time: 170ms. Actual CPU time: 5ms. AWS Lambda bills you for 170ms. Cloudflare Workers bills you for 5ms. Same function. Same result. 34x billing difference — because one platform charges for time your code spent waiting, and the other charges only for time your code spent computing. (Source: Morph, "Cloudflare Workers vs AWS Lambda 2026", April 2026) That billing model difference is the most underappreciated shift in backend infrastructure in 2026. And it's quietly reshaping how production systems are built — not just for edge use cases, but for everything. Here's the thesis I keep arriving at after watching teams migrate over the past 18 months: The "deploy to a region, scale with containers" model that dominated backend engineering from 2015-2024 is being replaced by an "deploy everywhere, scale with isolates" model. And most backend engineers haven't noticed because the migration is happening one function at a time. Baselime reported 80% lower cloud costs after migrating from AWS to Cloudflare. Not 8%. Eighty percent. (Source: Morph, April 2026) The numbers are that dramatic because three structural differences compound: Difference 1: Cold starts don't exist anymore. Lambda cold starts: 100ms to 3,000ms depending on runtime, package size, and VPC config. Java Lambda in a VPC? You might wait 3 full seconds before your code runs a single line. Cloudflare Workers cold starts: under 5 milliseconds. Effectively zero. Because Workers don't spin up containers. They run V8 isolates — the same lightweight sandboxing technology that runs your Chrome browser tabs. For a web API serving human users, 100ms cold start is noticeable but tolerable. For an AI agent making 200 API calls per session, cold starts compound catastrophically. 200 calls × 500ms average cold start = 100 seconds of dead time per session. The agent is waiting for infrastructure, not computing. (Source: Morph, April 2026) This is why every serious AI agent infrastructure team I know is evaluating edge-first deployment. Not because edge is trendy — because their agents are burning money and latency on cold starts that V8 isolates eliminate entirely. Difference 2: Global distribution is the default, not the exception. You deploy a Lambda function. It runs in us-east-1. A user in Tokyo hits your API. Their request travels 11,000 km to Virginia, your function processes it, and the response travels 11,000 km back. Round trip: 200-400ms of pure network latency before your code does anything. You deploy a Cloudflare Worker. It runs in 330+ cities worldwide. A user in Tokyo hits your API. The request reaches a Cloudflare edge node in Tokyo. Your code runs there. Response returns from Tokyo. Round trip network latency: effectively zero. This isn't edge computing as a niche optimization. This is "every function is global by default" as the deployment model. You don't choose a region. There is no region. Your code runs wherever the user is. For a traditional CRUD API, this reduces TTFB by 60-80%. (Source: Digital Applied, "Edge Computing: Cloudflare Workers Dev Guide 2026", January 2026) For AI agent endpoints that serve users across time zones — a customer support agent used by a global company, a coding assistant used by distributed teams — the latency reduction is the difference between "feels instant" and "feels slow." Difference 3: The ecosystem became a full stack. The reason edge computing stayed niche from 2018-2023 was simple: you could run code at the edge, but your data was still in a region. Every edge function that needed a database round-tripped to us-east-1 anyway, killing the latency advantage. In 2026, Cloudflare solved this by building an entire data layer at the edge: → D1: SQLite at the edge. Global read replication. Your queries run where your users are. → KV: Key-value storage with edge caching. Sub-millisecond reads globally. → R2: Object storage. S3-compatible. Zero egress fees. (This alone saves thousands/month for media-heavy applications.) → Durable Objects: Stateful computing at the edge. Strongly consistent, globally coordinated state — the thing that was impossible at the edge until 2024. → Queues: Message queuing with guaranteed delivery. → AI inference: Run ML models on serverless GPUs at the edge. → Vectorize: Vector database for semantic search at the edge. (Sources: Cloudflare Workers docs; Calmops, "Edge Computing with Cloudflare Workers", March 2026) This changes the calculus completely. In 2022, edge was "run your CDN logic there." In 2026, edge is "run your entire application there" — database, storage, queues, AI inference, state management. Full stack. The framework ecosystem caught up too. Hono — under 14KB, zero dependencies, Express-like routing — became the standard routing framework for Workers in 2026. You write code that looks almost identical to Express/Fastify, but it runs globally with zero cold starts. What this means for how you should think about your next backend project: The decision tree has changed: Is your workload I/O heavy (API calls, database queries, webhook processing)?→ Workers bills CPU time only. You pay for 5ms of compute, not 170ms of waiting. The cost difference is 10-34x. This is most web backends. Does your application serve users globally?→ Workers runs in 330+ cities automatically. No multi-region deployment to manage. No cross-region replication to configure. Global is the default. Does your application need zero cold starts?→ Workers uses V8 isolates: sub-5ms startup. Lambda uses containers: 100ms-3s startup. If you're serving real-time AI agents, chatbots, or latency-sensitive APIs, cold starts are unacceptable. Does your workload need heavy compute (video transcoding, ML training, data processing)?→ Lambda. Workers caps at 128MB memory and has CPU time limits. For compute-heavy tasks, Lambda's 10GB memory and 15-minute execution are necessary. Are you deeply integrated with the AWS ecosystem (DynamoDB, SQS, S3 triggers, Step Functions)?→ Lambda. Workers can't trigger on S3 events or consume DynamoDB streams. Migrating away from Lambda means migrating away from the AWS event-driven ecosystem. The honest assessment: 80% of web-facing backend functions are I/O-heavy, globally distributed workloads where Workers is structurally cheaper and faster. 20% are compute-heavy or AWS-locked workloads where Lambda is the right choice. Most teams are running 100% on Lambda because that's what they learned in 2018. The AI angle that ties this back to my usual topics: Every AI agent infrastructure pattern I've written about — MCP servers, tool endpoints, RAG retrieval APIs, model routing gateways, cost tracking middleware — is an I/O-heavy workload that serves global users and needs zero cold starts. These are exactly the workloads where edge-first architecture delivers the largest improvement over traditional serverless. An MCP server on Lambda: cold start + regional latency + wall-clock billing = slow and expensive. An MCP server on Workers: zero cold start + global distribution + CPU-only billing = fast and cheap. The infrastructure layer beneath AI agents matters as much as the orchestration layer above them. Most agent architecture discussions focus on LangGraph vs CrewAI and ignore the fact that the function layer underneath is adding 100+ seconds of dead time per session to cold starts. Three uncomfortable questions for any backend team in 2026: 1) What percentage of your Lambda invocation time is your code actually computing vs waiting for I/O? If you're not measuring this — you're paying for wait time. For most web APIs, CPU time is 3-10% of wall-clock time. The other 90-97% is network round-trips that Lambda bills you for and Workers doesn't. 2) Where are your users, and where is your code? If users are global and code is us-east-1 — you're adding 100-300ms of pure network latency to every request. Workers eliminates this by running your code where your users are. Automatically. 3) When was the last time you evaluated whether your serverless architecture is still the right one? If "when we set it up in 2020" — the infrastructure landscape has fundamentally changed. Edge-first wasn't viable in 2020. It is in 2026. A 2-day migration experiment on a single non-critical endpoint will tell you whether the cost and latency improvements are real for your workload. The thesis: → 2016-2020: "serverless means Lambda" → 2021-2024: "edge is interesting for CDN logic but not real backends" → 2026: "edge-first is the default for I/O-heavy global workloads, and traditional serverless is the fallback for compute-heavy regional workloads" The inversion already happened. Most backend engineers are still deploying to Lambda because that's what the tutorials taught them in 2018. The teams that re-evaluated are running the same functions at 60-80% lower latency and 80% lower cost. Same code. Different infrastructure. Dramatically different bill. The boring infrastructure migration wins. It always does. Especially when the exciting AI agent is waiting 100 seconds for cold starts nobody measured.

• 
  ben hylak (@benhylak) reported 1 hour ago

  @raunakdoesdev @thdxr @Cloudflare wrangler cli sucks last time i tried it

• 
  jsDelivr CDN (@jsDelivr) reported 1 hour ago

  We've temporarily shifted all traffic to Fastly until we resolve some reported Cloudflare issues related to incorrectly cached redirects.