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 (41%)
• Cloud Services (29%)
• Hosting (16%)
• Web Tools (10%)
• E-mail (4%)

Live Outage Map

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

City	Problem Type	Report Time
Noida	Hosting	3 days ago
Jewar	E-mail	3 days ago
Braga	Web Tools	3 days ago
Noida	Cloud Services	4 days ago
Paris	Cloud Services	4 days ago
Prievidza	Domains	5 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:

• 
  Mike (@ibuildcoolshit) reported 9 minutes ago

  @kapilansh_twt Namecheap customer for 20+ years just left them for cloudflare

• 
  Luma (@lumaBuilds) reported 10 minutes ago

  We migrated @ZeikoAI from Vercel to Cloudflare. Not because Vercel was bad, but because our infrastructure bill became a growth tax. The real lesson: Don’t migrate platforms. Migrate risk. Here’s what broke, what we learned, and why margin won 👇

• 
  rvivek (@rvivek) reported 11 minutes ago

  AWS is reportedly planning 11,000 early-career SDE hires. Cloudflare wants to hire 1,111 interns. Shopify scaled from ~100 to over 1,000. Companies aren't expanding intern programs because interns are cheap. AI turned good interns into high-leverage contributors. Here's what these companies are actually hiring for: > Interns who create clarity from ambiguity and turn it into automated workflows. > Interns who use AI without outsourcing judgment. They can tell you: "This is what AI generated. This is what I changed. This is where it was wrong. This is how I tested it." > Interns with real fundamentals. To debug, trace APIs and data flow, test outputs, and catch security risks before shipping. > Interns who stay close to the customer problem and make product tradeoffs to ship something useful, not just impressive. > Interns who ship useful code from day one. Cloudflare fast-tracks applicants who build an AI-powered app on Cloudflare as part of the application itself. A junior engineer with strong fundamentals and genuine AI fluency is more valuable to a company today than they have ever been. The companies that figured this out are expanding their intern programs by 10x.

• 
  Padhie (@PuddyPadhie) reported 12 minutes ago

  Congratulations @googlechrome I never seen web browser devs they fix 127 security issues in one version. And it's really amazing that you define @Cloudflare as a "security issue". And of course it's very safe to block all Javascript. Noone need that these days anyway...

• 
  Sid (@SidJain_80) reported 13 minutes ago

  @Umesh__digital Don’t push large payloads through your service-to-service calls that’s the bottleneck Better design: Use object storage (e.g., Amazon S3, Google Cloud Storage) Upload file once, pass signed URL/reference between services instead of raw data Chunking / multipart upload Break large files into smaller parts for parallel upload/download Async processing Use queues (Apache Kafka, RabbitMQ) to avoid blocking calls Streaming instead of buffering Process data as a stream (gRPC/HTTP streaming) to reduce memory spikes CDN for distribution Cache heavy content closer to users (e.g., Cloudflare) Compression + binary formats Reduce payload size (gzip, protobuf) Rule pass references, not files

• 
  h 🇺🇦🇵🇸 (@PrototypePWND) reported 16 minutes ago

  @RixThereal99054 I think I was I thought you heard it. Probably the cloudflare warp connection issues

• 
  adah (@adahstwt) reported 19 minutes ago

  @devbelowstairs never used cloudflare I should try it

• 
  🇮🇳 Sai Bharadwaj (@saibharadwaj) reported 19 minutes ago

  @Cloudflare @CloudflareHelp Hey Team, Do you have an ETA for Next.js 16 support in `@cloudflare/next-on-pages`?

• 
  Extynct Studios (@ExtynctStudios) reported 22 minutes ago

  Stopping the bad guys with Cloudflare: 129 malicious requests blocked or challenged in the last month #cloudflare

• 
  Colin Regan 🚀 (@engalicorn) reported 24 minutes ago

  @dhh @stefansdev @Cloudflare No telemetry!? Can you insert a dummy "Share data to help improve your experience?" So I can deny it?

• 
  Brandon Carl (@brandonjcarl) reported 24 minutes ago

  @miyagiyang @Cloudflare Thank you! You’re mostly right. They do support WASM-compilation and containerization, but that’s not a primary path, Not to over-evangelize, but the reason is rooted in how quickly they can spin up and down isolated JavaScript threads. It’s a reason why I was saying it requires thinking things about architecture. Before: I had to think, in terms of Kafka, Kubernetes, logging services, etc. Now those things are “free” - but requires revisiting application and other logic.

• 
  Duchess Deborah 🇺🇸 🗽 ✝️👑 (@DuchessDeborah) reported 27 minutes ago

  @ann_omynous Cloudflare is not the issue moron

• 
  Dav (@davafons_dev) reported 29 minutes ago

  @varunkrish @Hetzner_Online I'm using Cloudflare for CDN which works great, but I needed a VPS for my backend. In any case if their customer support is like this I worry about their SLAs... so might have to just try other proviers even if they are more expensive.

• 
  Zack Riley 🇦🇺 (@ColdHeart_Prj) reported 33 minutes ago

  @BHolshouserUS Cloudflare went down earlier, probably had something to do with it.

• 
  0xA (@NeuralAA) reported 38 minutes ago

  Incredible people of the incredible cloudflare @dok2001 @dillon_mulroy @threepointone idk who else tbh The onboarding to the AI gateway is very bad tbh Why do I have to send a request from the terminal to be able to see the dashboard? You create the token and see nothing

• 
  Nikolaï Roycourt (@Nikokow) reported 38 minutes ago

  Writing thousands of files on Cloudflare R2 is so slow... script is wasting a lot of time because of that… Must find a way to optimize that

• 
  Pradeep Saran | Full Stack Developer (@pradeepsaran_29) reported 41 minutes ago

  @ardent__dev Cloudflare. No markup. No renewal surprises. At cost pricing — exactly what you see is what you pay. Never going back.

• 
  Oh, saw my bin, LADDER! (@OhSawMyBinLader) reported 45 minutes ago

  @patternrecoggni CLOUDFLARE YOU PIECE OF ****

• 
  ichi (@ichimikichiki) reported 45 minutes ago

  @notdan But to answer your question, I think Cloudflare is the cheapest registry from what I've seen. Not sure if they support .ru however.

• 
  Gergely Orosz (@GergelyOrosz) reported 47 minutes ago

  How is it that Cloudflare publishes RCAs within 24 hours of a massive outage, and no other company of similar size comes close? Waiting almost 3 weeks for the one Coinbase promised publicly (their global trading outage for ~8 hours I think), still crickets...

• 
  Jaideep Parashar (@jaideepparasha7) reported 52 minutes ago

  Another Layoff: Cloudflare lays off 1100 employees. They didn't cut the jobs because Cloudflare is struggling. This is true AI effect now, when companies are laying off without any issue.

• 
  Michael Ford (@Michael15028851) reported 54 minutes ago

  @CryptoCyberia 90% of it is legal fees (fighting against a NSL, big brother, and petty government wants this **** and telling them no) and the throughput webhosting (cloudflare etc), 10% of it is the servers and software.

• 
  Arosh (@AroshPererax) reported 56 minutes ago

  @_ashleypeacock @sudo_overflow The only thing is the latency. I think it’s probably because the workers are “region:earth” but my db is in one region. Even if i set worker to be in a particular region i am not sure if cloudflare treat it as a hint that will be respected when possible vs always.

• 
  timi2506 (@timi2506) reported 57 minutes ago

  @not_jpsenak @MyPayIndia It isn’t, it’s just Hauber who enabled cloudflare with PROXY mode 😭 (safari tries to upgrade to and cloudflare is like: “sure” just to display “server down” even tho it’s not)

• 
  Zunaira Ai (@ZunairaAi) reported 57 minutes ago

  The neighbor's final advice was the most actionable. He sat down and wrote out a list of 6 things every internet customer should do: 1. Turn off the public Xfinity hotspot (or your ISP's equivalent Spectrum, Optimum, and Cox all do this too) 2. Manually set your Wi-Fi channel instead of "Auto" 3. Disable QoS / Smart Network "optimization" features 4. Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) 5. Buy your own modem and router, stop renting from the ISP 6. Test your speed with fast. com or speedtest. net using a non-ISP server, never trust your ISP's own speed test Total cost: $150-300 in equipment, paid back within a year. Total time: One afternoon of setup. Total impact: Often 2-5x improvement in real-world speeds. The customer went from paying $90/month for "fast" internet that crawled to paying $60/month for the same internet that finally worked.

• 
  Brian Julkunen (@brianolavi) reported 60 minutes ago

  @RyanYorkSEO @chris_nectiv Good question, not sure specifically how the cloudflare service works (but I am going to deploy everywhere i can) it sounds like it looks for a user agent header for accepts markdown and then serves the markdown file

• 
  Devanshu (@DevanshuXi) reported 1 hour ago

  People usually learn tries in the context of autocomplete and dictionary problems, but once you start working on real infra systems, you realize tries are everywhere underneath modern high-performance networking and search stacks. I was recently reading the @Cloudflare blog about the performance bottlenecks of Linux BPF LPM tries used in packet routing and firewall systems, and learned something important. At scale, “search” stops being an algorithms problem and becomes a memory systems problem. The interesting part about tries is that they trade comparison-heavy searching for deterministic state transitions over bits/symbols. Instead of repeatedly comparing full keys like balanced BSTs or hash collision chains, a trie incrementally consumes the key itself during traversal. That sounds theoretical until you realize this is exactly why networking stacks use longest-prefix-match tries for CIDR routing. Routers are effectively doing millions of searches/sec over prefixes where latency matters more than throughput averages, branch mispredictions hurt badly, deterministic lookup depth matters, and memory locality dominates everything One thing that becomes super obvious from the BPF trie implementation is how “Big-O” alone becomes almost useless for understanding performance. The Linux BPF LPM trie uses only 2 child pointers per node, which means densely populated prefixes effectively degenerate into many sequential binary branch decisions. In theory the asymptotics still look acceptable. In practice, the trie height explodes, pointer chasing increases, and lookup throughput collapses as the structure outgrows cache and starts hammering dTLBs. That’s the part most people miss about high-performance systems: a cache miss is often more expensive than the actual computation. Modern CPUs are absurdly fast at arithmetic. They’re slow at waiting for memory. Also I was solving a suffix-query problem recently where the straightforward Trie solution itself wasn’t enough. The interesting part became optimizing the traversal and memory layout rather than just “using a Trie.” The strategy was to build a highly optimized reversed Trie where every node stores the “best” candidate index for that suffix path. Instead of doing expensive comparisons during query time, I pushed almost all decision-making into insertion time. While inserting container strings in reverse order, every node keeps track of shortest matching string and if tied, earliest index. So during query traversal, the search becomes almost embarrassingly simple: walk backwards through the query, follow pointers until traversal breaks, and the current node already contains the precomputed optimal answer. No heap allocations during queries. No suffix comparisons during queries. No backtracking. No secondary scans. Just incremental state transitions through memory. The funny thing is the actual algorithmic idea is pretty small. Most of the engineering challenge became memory optimization. A naive pointer-heavy Trie immediately started hitting MLE because every node carried 26 pointers. So the optimization was moving toward index-based contiguous storage: replacing raw pointers with integer child indices storing nodes in a flat vector, reducing pointer chasing improving locality, cutting memory almost in half And honestly this is exactly the same class of problem that appears in production systems. In CP, tries feel like string DS problems. In real systems, tries are actually cache-behavior problems disguised as data structures. That’s why production systems rarely use textbook tries. Instead you start seeing: Patricia tries, radix tries, crit-bit trees, compressed tries, LC-tries, succinct tries finite state transducers, double-array tries. All basically solving the same underlying issue: “How do we preserve fast prefix search while minimizing memory movement?” Even path compression itself is basically a cache optimization disguised as a data structure trick. So, This is why systems engineering feels so different from competitive programming sometimes. In CP, we optimize operations. In real infra, we optimize movement through memory.

• 
  Hekmon | Agent Workflows (@hhkkmon) reported 1 hour ago

  I tried to save $20/month. So I moved part of my data from Supabase to Cloudflare D1. A few days later, D1 cost me $100+. The real lesson was not “D1 is bad”. The lesson was, I trusted AI-generated code because it looked correct. 😑😑😑

• 
  Gerrit van Vuuren (@gerrit_jvv) reported 1 hour ago

  @Cloudflare @Cloudflare your pages uploads are still down. chunk-YO254JJB.js net::ERR_ABORTED 500 (Internal Server Error). Since: May 28, 2026 - 20:45 UTC :( Time to migrate away, sorry you can't be trusted anymore.

• 
  Uche | Tech Solution Expert (@Nueltek) reported 1 hour ago

  @jayhemz Cloudflare to the rescue for a single point of failure? How exactly is Cloudflare supposed to handle that? I thought Cloudflare mainly helps with bandwidth, caching, and DDoS protection. How does it handle a VPS crash, server hardware failure, PostgreSQL corruption, or even a misconfigured firewall? Also, the problem usually isn't bandwidth. The real bottlenecks are CPU, RAM, disk I/O, database connections, etc. A VPS can run out of RAM long before it comes close to using 10TB of bandwidth. Anyways, for small brochure websites, I agree the tradeoff is usually worth it. But for SaaS products and other critical systems, I'd still want more isolation and redundancy, to be honest.