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.

• Cloud Services (43%)
• Domains (21%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	17 days ago
Los Angeles	Cloud Services	19 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	2 months ago
Angers	Cloud Services	2 months 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:

• 
  assertchris (@assertchris) reported 7 minutes ago

  I thought the 10 custom domain limit (on the Laravel Cloud plan I'm on) would be an issue. It just pushed me to handle more things directly in CloudFlare. A much better solution of those things that need mail DNS and a simple redirect.

• 
  Ravi Ojha (@raviojhax) reported 7 minutes ago

  @Voxyz_ai browsing the web on a cloud computer was clunky experience, at one point it was just stuck at cloudflare captcha and didn't even ask me to help there lol it just kept trying

• 
  Attick (@Attickk) reported 9 minutes ago

  @imagesaicouldnt blame her for cloudflare being down

• 
  Jared Smith (@woodchipdaddy) reported 10 minutes ago

  i freakin LOVE combining all of these into a single CLI interaction - checking domains - buying a domain name - setting up nameservers on cloudflare - setting up hosting on vercel - setting up email Installing site + basic framework This would have taken me hours if not a whole day before. Now it's minutes. God damn it's good to have bots

• 
  Jiten Bansal (@bansal_io) reported 12 minutes ago

  I’m building a SaaS where customers will use their own custom domains. Can anyone familiar with Cloudflare for SaaS clarify this for me? The pricing page says $0.10 per additional hostname. Is that $0.10 per hostname per month, or a one-time charge? Any confirmation from someone who has actually used Cloudflare for SaaS billing would be really helpful. It’ll help me choose the right stack for my SaaS. @CloudflareDev @threepointone

• 
  addison (@uwunetes) reported 15 minutes ago

  @BraydenWilmoth im conflicted cause well, first I own an iPhone so I need an android app.... otherwise, I don't think I would use it ever for anything other than statistics, fixing small config issues on the go, maybe managing some cloudflare settings... stuff I don't particularly trust ai for

• 
  KZZY (@kzzy47) reported 17 minutes ago

  @scheemunai The GA vs Cloudflare gap is the more interesting number here. Everyone's dashboard is quietly lying to them by 4x and most people never bother to check a second source.

• 
  Erik Langille (@eriklangille) reported 18 minutes ago

  @BraydenWilmoth can you fix the two terrible iOS apps cloudflare already has? (1.1.1.1 and Cloudflare One) Tried using Warp for CF Zero Trust and it kept erroring. Turns out I needed this other CF One app. Took like 2 hours of debugging Tailscale is way smoother

• 
  Divin Prince (@divinprnc) reported 20 minutes ago

  @zakizakkzakk Yeah Just Pushed support for running it Entirely on Cloudflare

• 
  BITx (@getbitx) reported 23 minutes ago

  @xrpcafe @XRPXolo It’s possible your ISP is using CGNAT which can cause Cloudflare to block your shared public IP address. Asking your ISP to allocate you a fixed IP might resolve your issue.

• 
  WhiskyBone🌻🍅 (@Whisky_Bone) reported 23 minutes ago

  @DocStrangelove2 And yet Reddit is still up and backed by @Cloudflare but Kiwifarms isn’t despite not having anything close to as bad, just because a group of wealthy rapists told them not to.

• 
  Mahesh (@MaheshPawaar) reported 24 minutes ago

  @AnupamHaldkar Exactly. When I transferred my domain from Vercel to Cloudflare, I faced this exact issue. It wasn't working on Wi-Fi, but worked on mobile data.

• 
  Maciej Nowak (@mnowak_eth) reported 24 minutes ago

  Cloudflare does not cache your HTML by default. You can be paying for Cloudflare and still have none of your HTML cached there. Would you be able to tell this is your case? By default Cloudflare caches by file extension, not by content type. CSS, JS, images: yes. The HTML document, the thing PHP and the database assemble: not by default. Without an explicit rule, every page view still goes to the origin. I have seen more than one setup where "we have a CDN" meant the logo loads from the edge of the network and everything else works exactly as before. Check the cf-cache-status header. If an HTML document comes back as DYNAMIC, the edge is not caching it at all. What I also hear on calls sometimes are two words traded as if they were two products: CDN and edge. They are not two products. It is the same few hundred machines Cloudflare keeps around the world, and the two names come from different decades. CDN says what the thing does, deliver content. Edge says where it is located, at the far end of the network. For twenty years those were words for the same servers, and then the industry started using edge for the code you can run on them. Nobody planned that, so it is not on you if the two names blur together. What is different is not the name but the job you give those machines. Handing out copies of files, your images, CSS and JS, comes with the account. No decisions, it's just simple distribution, working from the moment you point your domain at them. The other job is running your logic up there: assembling and caching whole HTML pages, telling a logged-in visitor from an anonymous one, holding the product page while letting the basket through untouched. It's not on by default because it needs rules: what may be stored, for whom, for how long, and what wipes it. And you are the one who knows those rules. And the principle that ties this whole series together: cache layers are a cascade, not a set of independent switches. The lower layers have to hit before anything propagates up and reaches the edge. Getting that order right is messy work, and it is the reason a site feels smooth when someone has done it. So before you add another layer, you should be able to say three things about it in plain words. What it stores: files, whole pages, or answers from the database. Who is allowed to get the same copy: everyone, or does a logged-in visitor need their own. And what removes that copy when the content changes, plus who is able to trigger it. If any of the three is a shrug, you probably have something messed up and don't know it yet. We created a great guide to understanding caching specifically for WordPress. Link in comment

• 
  Splamei Ch.【 SplameiPlay 】 (@splamei) reported 25 minutes ago

  Yes I am reading the full Terms of Service and Privacy Policy to Cloudflare. Why do you ask? I'm not weird

• 
  Md. Abu Taher (@entrptaher) reported 26 minutes ago

  @divinprnc Mind sharing why resend for sending and receiving? Doesnt cloudflare offer native email support right now?

• 
  Sheik Althaf (@SheikAlthafDev) reported 27 minutes ago

  Shipped an LLM feature. Invoice arrived. Still couldn't tell you which customer spent what. This is the common case in 2026, not the exception. Most teams I talk to don't have a clean answer. The fix isn't a dashboard. It's six fields tagged at the call site: user_id, customer_id, feature, deployment, prompt_version, agent_run_id. Provider logs strip context. Post-hoc parsing breaks. Three failure modes from real incidents: → Runaway agent loops — retry-on-malformed-output billing tokens until a guard fires → Retry storms — SDK retries on transient 503s that the app never sees but the bill catches → Context bloat — a longer system prompt moves cost-per-request before total spend looks wrong Pricing is the second problem and it's worse than people think: • Reasoning tokens → 30–40% undercount if you only count visible output • 128K context crossing → silently 2x's per-token price, no signal in the response • Same model, different prices per host (Kimi K2.5: $0.5/$2.8 Together, $0.6/$3 Fireworks) Tooling is catching up. Cloudflare AI Gateway shipped dollar-budget limits in June 2026, scoped per model/provider/attribute. Portkey open-sourced their 3,500-model pricing DB. Langfuse v4 exposes cost_details per observation, queryable by tag. FinOps Foundation 2025: AI spend management jumped from 31% to 63% of practitioners YoY — the largest one-year swing in the report. Tag at request time. Enforce at the gateway. Then you can answer the question. How is your team attributing token spend today?

• 
  RED BARN NEWS 🇺🇸 (@JasperRoads) reported 32 minutes ago

  1/2 Quick tip that can save your parents/grandparents a ton of headaches: Grandma and Grandad keep getting hit with phishing texts and links. Every few months the phone gets completely wrecked and needs a factory reset. Changing the DNS to Cloudflare Family (1.1.1.3 + 1.0.0.3) blocks known phishing, malware, and scam sites at the DNS level. When they click a bad link, the page just doesn’t load instead of infecting the phone. It’s free, doesn’t slow anything down, and works quietly in the background. Not 100% perfect, but it stops a huge chunk of the common phishing junk older people get targeted with.

• 
  Uben (@Ubendev) reported 40 minutes ago

  @aiwithadb just shipped the version 4 of my CRM extension. mostly Cloudflare worker issues fixes.

• 
  Paul 🇷🇴🇨🇴 (@hasieratik) reported 41 minutes ago

  @TeeDevh good will gestures matter, a lot; obviously not your scale, but Cloudflare covered a $100 bill that I made because I was stupid and I went on X and Reddit and praised them and their support team :)

• 
  Sindhu Biswal (@sindhubiswal) reported 43 minutes ago

  @frantzfries cloudflare didn't build a new moat, they repositioned an existing one (network layer control) for a buyer that didn't have budget for it yet. that kind of positioning velocity only works because the capability was already sitting there waiting for demand to catch up.

• 
  SK64 (@stonkeykong64) reported 43 minutes ago

  Is Cloudflare main site down or what?

• 
  Divin Prince (@divinprnc) reported 45 minutes ago

  @dragos_dydy It support cloudflare as well

• 
  dad chords (@dadchords) reported 47 minutes ago

  claude code isolated code environments excels at making mobile three js game mockups with its screenshotting. bad publishing and repo connection ux - default should be create new private repo on github, not pick a repo. it's amazing seeing it work from a iphone app instance. also publishing html fragments to github pages or cloudflare dev pages is bullshit, they need actual artifact hosting without share banner sign in wrappers

• 
  dad chords (@dadchords) reported 49 minutes ago

  grok is poised to pick up claude code customers long time multi claude pro max subscriber here, trimmed back to one claude sub, one grok, one agy and one codex Too early to tell but my current low confidence read is Grok is better overall, cleaner cli, smoother multi agent spawns, more stable and faster and same intelligence. (claude code isolated code environments excels at making mobile three js game mockups with its screenshotting. bad publishing and repo connection ux - default should be create new private repo on github, not pick a repo. it's amazing seeing it work from a iphone app instance. also publishing html fragments to github pages or cloudflare dev pages is bullshit, they need actual artifact hosting without share banner sign in wrappers)

• 
  🐗 Giacomo Balli (@BigBalli) reported 49 minutes ago

  Woke up to a saturated PHP-FPM pool. Overnight someone pulled 16,420 requests off one of my sites in seven hours, from 9,509 different IPs. All of it China Mobile CMNET. 36.128.0.0/10 and 36.212.0.0/14, spread across 18 /16 blocks. The detail that took me longest to see: 15,628 distinct URLs. That's 1.05 requests per URL. It walked the entire URL space, one fetch each. Every request was a cold miss at the edge by construction. Cloudflare cached all of it correctly and absorbed none of it. Seven rotating Chrome user agents, every one a real browser string, so all my UA-based rules sailed right past it. No reverse DNS. No self-identification. It never asked for robots.txt. It averaged 1.7 requests per IP, which is below every per-IP threshold I had. Zero requests hit the rate limiter. Blocked it by netblock in the end. Fifteen days of logs show 43 requests total from those ranges to my 40-odd other sites, so the collateral is nothing. Anyone else getting hammered out of CMNET lately? Trying to work out whether this is pointed at me or spraying everyone.

• 
  Manuel Suarez (@srmanuelangel) reported 59 minutes ago

  I think infra might be one of the areas where coding agents feel the most unfair. So much of the job used to be babysitting slow feedback loops: change something → deploy → wait 15 min → find out it broke → fix → wait again. Now you can give an agent the Terraform, let it understand how the whole thing is wired together, read the errors, and keep iterating. Obviously this doesn't make infra trivial. Security, WAFs, rate limits, CloudFront, Cloudflare, permissions, etc. still need actual thought. But for relatively simple products, the amount of annoying work that just disappeared is kind of insane. It also makes some infra SaaS feel a lot less essential when you have an agent + a pile of AWS/GCP/Azure startup credits. Much respect to the people who were doing all this **** manually 5 years ago.

• 
  Alexander Zuev (@zlxndr) reported 59 minutes ago

  @vicentesandev + retries, timeouts, DI, error taxonomy is trivial and not an issue even without effect - the only core reason for me to consider the transition is to make the logic more maintainable and more reliable And the most confusing bit of this is handling errors / translating them at the boundaries: - tanstack server fn handle them one way - server api routes expect a response - cloudflare workflow have specific control flow requirements with nonRetryableError - cf durable objects have their own nuances with alarms - cf queues need to ack/retry - cron just logs at the boundary That’s where probably most of integration effort lies

• 
  Fern (@Ferrrrrnnnnnn) reported 1 hour ago

  Hey @AMCTheatres @Cloudflare, might be smart to fix your dogshit rate limiting before you drop tickets for the biggest movie of the decade

• 
  yenkel (@yenkel) reported 1 hour ago

  @positiveblue2 @vercel @Cloudflare any issues with reliability?

• 
  XXI (@XXIfomo) reported 1 hour ago

  A 21-YEAR-OLD IN COPENHAGEN BUILT A HEX-GRID LIGHT PUZZLE IN ELEVEN DAYS AND HIT $4,200 A MONTH BY WEEK EIGHT. HE SPENT $205 TO SHIP IT. MOST PEOPLE STILL HAVEN'T SHIPPED ANYTHING. He is 21. Solo. No studio. He works from a shared desk in Nørrebro. Claude Code writes the puzzle generator, the reflection math, and the leaderboard. He hand-tunes the visual polish and refuses to let the model touch the lighting effects. The whole game runs on Cloudflare Workers for five dollars a month. The player never asks who built it. She screenshots her solution and asks the internet how she pulled it off in seven moves. Everyone else spends three months vibe-coding an original masterpiece that nobody plays. He picked a shape people already knew how to solve, added a limited-moves counter, and dropped the link in three subreddits on a Tuesday. By Friday it had 340 daily players. By week seven it had 47,000. Build time = 11 days Total cost to ship = $205 Claude Code Max subscription = $200 per month Hosting = $5 per month Daily active users at week eight = 47,000 Monthly recurring revenue = $4,200 Marketing spend = $0 For nine days nothing worked. The generator produced puzzles with no valid solutions. He almost killed the project on day ten. On day eleven he switched the generator to reverse-solve from a target state and every level shipped playable. The first hundred players arrived before breakfast. Monument Valley shipped in three years with a team of ten. The kid in Copenhagen shipped a shape people already knew how to solve in eleven days. bookmark this and read the article below